It looks to me like the wbond Package Manager has problems marking ST3-compatible packages as such. Some of the issues may be due to the package makers themselves and their metadata, but not all of the problems.

First, a package listing. Note how all of them only claim to support ST2 - both via the occasional ST2 tag, and in the package description:

http://i.imgur.com/jRqW8bd.png

But, clicking into a package reveals an “ST2/ST3” tag which wasn’t shown on the index page. Plus, conflicting compatibility information in the metadata:

http://i.imgur.com/kapeRfW.png

This isn’t a Package Manager issue. The description is taken from the GitHub description line. https://github.com/jbrooksuk/InsertNums and “Sublime Text plugin for inserting sequences. Supporting alphanumerics and hex, with bitwise operations!” for example.

Basically, the author of the package needs to update their description lines. The package will still be compatible with ST2 and ST3, but would’ve originally been written for ST2.

In the list view, where there is not a lot of space to persent data, I only show things that are “exceptions”. Since most packages (sublime.wbond.net/stats) are ST2/3 compatible, I don’t show the badge since there is not a whole ton of space to use.

As jbrooksuk pointed out, this is really an issue with the package’s description. Many of these packages were written before ST3 was announced, and people were trying to show that it worked with ST 2 (cross-platform) as opposed to ST1. Obviously things have changed since then, but the description is easy to forget.

So, say I use ST3. I guess there’s just no good way to see ST3-compatible packages in the search results - whether or not the package manager has marked it as such? Or, are you saying that the default - no tag means ST3-compatibility?

In the first screenshot right under the search field it says “filters:”. Enter these to filter the results. E.g., to find packages with “script” that work in Sublime Text 3, enter “script :st3”.

Excellent - thanks!