We’ve never been that close (I can’t tell when it’s going to happen though)!

What has already been done:

• The API is JavaScript ready! No need to mess around with the folders if you want to use the API from your JavaScript scripts.

• Easier configuration. It now has a settings window inside the editor. You don’t need to call Init before using the API.

• The API part of it is fully functional (i.e. adding scores, trophies, etc but not helpers like login/leaderboard windows).

• It uses actions instead of delegates.

• Automatically connect WebPlayer users! Also, the Editor can simulate this behaviour. Hourray!

• A demo console to test endpoints (also serve as a tutorial as you can inspect how it’s done). In C# only at the moment. I’ll do a JavaScript version as well.

What still needs to be done (apart from “A lot!”):

• The UI: login/leaderboard/trophies windows and notifications.

• Automatically ping so you don’t have to worry about it.

• Automatically download the trophies definitions/pictures (with caching) so list/notifications can be shown much faster.

• Make the MD5 encryption WindowsPhone/WindowsStore compatible.

• Trim down the JSON library (for smaller build size).

• A written/video tutorial. A demo game.

• Documentation.

• (Optional) Remember me option for the login window.

• (Optional) Custom inspector for the settings (with help bubble to explain what each setting is about).

• (Optional) Guest name generator! When saving a score for a guest, it will show the name of the guest followed by “(guest)” on the website, but because the default name is “Guest”, it actually shows “Guest (guest)” which is pretty lame. Unless you specify a name yourself, it would be nice to add random names like Mario/Luigi/Sonic/etc (and possibly allow you to give a custom list to match your game universe).

• (Optional) The API is a lot less chatty than it uses to be but and option to enable/disable loging would be nice.

• And probably more…

Notes:

• It looks like JavaScript does not recognize optional parameters of C# functions so JavaScript users will have to specify all the parameters all the time (if you needed another reason to jump to C#), but as far as I am aware, there is nothing I can do about it.

• It will not be backward compatible (this is why it’s v2 not v1.3). That’s unfortunate but I’ve learned a lot in the meantime and some design choices of the past couldn’t simply live (like using uint instead of int).

• The API now has a github repo so you can watch my progress! Also, after the first release, I’ll be able to accept pull requests if anybody wants to help with the development. Or you can also just comment on the code.