Support us on Patreon
PayPal
Good news for any Unity3D developers! Ludosity has open sourced their Steamworks wrapper and made it free.
Find the source code here.
Hopefully this can stop future games using Steamworks wrappers that have finicky Linux support, so they could just use this one instead and even help improve it if they wish.
A wrapper like this is apparently the cause of the delay for 7 Days To Die getting a Linux version for an example off the top of my head.
I cannot imagine why anyone would go with a different Steamworks wrapper now. Not only is it open source, but it is rammed full of features too.
About It
Ludosity's Steamworks Wrapper is a fully managed .Net wrapper of Valve's Steamworks SDK. It supports Windows, Mac and Linux!
This wrapper has been used to succesfully deploy several Steam-games.
Features:
* Achievements
* Apps
* Cloud
* Stats
* Friends
* Leaderboards
* Matchmaking
* MatchmakingServers
* GameServer
* GameServerStats
* Networking
* Screenshots
* Utils
* HTTP
* Big Picture Mode
* Steam Controller
* SteamVR
See their blog post on it here. Article taken from GamingOnLinux.com.
0 Likes
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
9 comments
Actually, it's exactly this wrapper that Fun Pimps used as excuse for not giving f..k about Linux users.
And related problem has been fixed circa since january.
And related problem has been fixed circa since january.
0 Likes
I'm either blind or they don't specify which license the code is under.
0 Likes
Yeah, I don't see a license either.
And the PDF in the documentation says something about $300 for access to the source code?
So unless I'm missing something, for now, this code drop is completely unusable.
And the PDF in the documentation says something about $300 for access to the source code?
So unless I'm missing something, for now, this code drop is completely unusable.
0 Likes
Chatted with them on twitter. They will slap a license on as soon as they can.
1 Likes, Who?
This is something you realise after a few weeks being an open developer that Licences are everything when it comes to open source. I really hope it will be unrestricted on others projects...
Also why did they use Sourceforge?
Also why did they use Sourceforge?
1 Likes, Who?
This is pretty much non news, this was prompted by another wrapper being released as a result of their closed source nature. https://github.com/rlabrecque/Steamworks.NET
They have abandoned their wrapper and do not provide support for it anymore and it's already starting to wither away. (2 Steamworks versions behind...) As someone else mentioned they frequently had platform specific issues which in some cases directly harmed linux gaming. We switched from this wrapper to Steamworks.NET as a result of this.
From their "documentation": "This library is built against Ubuntu 12.04 32-bit version. It has not been properly tested on other Linux distributions yet. Currently we only support 32-bit versions of Linux. 64-bit is being worked on, stay tuned for an announcement on an official relase."
The lack of license just shows how little they care, It's literally just a dump of whatever files they had the last time someone touched it.
They have abandoned their wrapper and do not provide support for it anymore and it's already starting to wither away. (2 Steamworks versions behind...) As someone else mentioned they frequently had platform specific issues which in some cases directly harmed linux gaming. We switched from this wrapper to Steamworks.NET as a result of this.
From their "documentation": "This library is built against Ubuntu 12.04 32-bit version. It has not been properly tested on other Linux distributions yet. Currently we only support 32-bit versions of Linux. 64-bit is being worked on, stay tuned for an announcement on an official relase."
The lack of license just shows how little they care, It's literally just a dump of whatever files they had the last time someone touched it.
0 Likes
Those Mercurial files (.hg directory and .hgignore file) inside the git repository also make it seem thoughtlessly thrown together.
1 Likes, Who?
I'm really curious why they didn't just set their Bitbucket repo to public. Surely that would have been even easier and generally superior. They specifically mention the Bitbucke repo in their readme (which was written before going free & open source): "Can I access the source code? Yes! We offer access to the source code for $300 (or $250 if you’ve already bought iton the Asset Store) which will grant you access to our Bitbucket repository. With source access, you can extend or modify the wrapper as you please, and use the results it in your commercial products."
With Sourceforge they are using git so yeah, those hg files are useless and they have already committed garbage with them and stuff that the .hgignore should have protected against and would have if they just renamed it .gitignore before committing this. (Some examples: The Visual studio cache files .suo, /bin/ and /obj/ output dirs, There's a few rar's that contains the exact same content as the folder that it's in.)
At the very least this is generally a good thing as I'm sure someone will add 64 bit linux support which will improve things for people already using their wrapper but it's also actively harmful to linux gaming if people start using it over Steamworks.NET in it's current state.
I should note that I am associated with the creator of Steamworks.NET so my view is obviously biased, but Steamworks.NET was created as a direct result of stuff like this.
With Sourceforge they are using git so yeah, those hg files are useless and they have already committed garbage with them and stuff that the .hgignore should have protected against and would have if they just renamed it .gitignore before committing this. (Some examples: The Visual studio cache files .suo, /bin/ and /obj/ output dirs, There's a few rar's that contains the exact same content as the folder that it's in.)
At the very least this is generally a good thing as I'm sure someone will add 64 bit linux support which will improve things for people already using their wrapper but it's also actively harmful to linux gaming if people start using it over Steamworks.NET in it's current state.
I should note that I am associated with the creator of Steamworks.NET so my view is obviously biased, but Steamworks.NET was created as a direct result of stuff like this.
0 Likes
See more from me