linc_steam_api

[Yanrishatum]

I've waited long enough for linc_steamworks to "complete", which never happened. So I decided to just make my own and publish it at the very early development stages. Creating bindings to Steam API is heck of a work and I always open to pull requests implementing missing features. Main rule: minimum overhead.

https://github.com/Yanrishatum/linc_steam_api

[ruby0x1]

(I'd appreciate if you could tone it down a little - it's unnecessary to start a conversation this way.)

Since this is the first time you're "asking" about it, I can give you information on the status of the library. Testing the library requires a lot of effort, since you need an actual game on steam and you have to implement things that the spacewar example code doesn't really implement - like cloud saves or workshop or whatever. There are things in the backend of the game that you can't create or modify in order to test things. This requires time and games.

I initially implemented it and it shipped with a first version in Westport for the basic user API's and cloud save. This version had some issues because it was created before hxcpp was ready for linc stuff, and transitioned to linc right before we used it, so it had some manual steps and extra (extra) setup which I didn't want.

Recently though I have been working with Benn on Operator Overload to flesh it out more and push it live, which includes more than just these 2 API's.

I have also since answered some of the important questions about the licensing of the files to make sure I'm not breaching any contracts with Valve, and I have been tidying and documenting it for use (even this last week).

The version I will push is fine on Mac, WIndows and Linux and includes a flow file for automatically pulling the correct files into the build, and gives you defines to configure some stuff. It will still need testing, and it's not a full coverage of the API (the api is huge) but it's definitely usable.

I'll make a note here when the repo goes up soon.

Thanks for the comments.

[Yanrishatum]

I'd appreciate if you could tone it down a little - it's unnecessary to start a conversation this way.

Sorry if it sound a bit up-toned. I just wanted to note that this lib marked as "nearly complete" and "soon" way too long (more than a year). Didn't meant anything bad.

[ruby0x1]

Yea sometimes things come up! :)
Feel free to just ask in future, I'm always happy to respond to questions.