If you ship on multiple platforms you must have multiple build targets for each platforms. This is only recommended if your binary is not portable across platforms already.In Visual Studio open your project properties, change to the Build tab and define STEAMWORKS_WIN or STEAMWORKS_LIN_OSX globally via Conditional compilation symbols. Option B: Otherwise, copy Plugins/Steamworks.NET directly into your C# project.Start coding! Call SteamAPI.Init() before initializing your renderer.Reference the built assembly () in your project.(Optional if you downloaded a prebuilt version) Open the Visual Studio solution (.sln) file, build both targets one for Windows and one for OSX & Linux.Option A: The recommended route is to build the standalone assemblies with the project file located in Standalone/ or download the prebuilt binaries which are available on the Releases page.If you are not using Unity then you have two available paths that you can take. Steamworks.NET is a free project but if it helps you make money please consider donating so that I can continue to support it in the years to come!Īlso never ever required but greatly appreciated is a mention in your credits! It’s free, easy, and can help a lot! ( Examples) Head over to Getting Started to start using Steamworks.NET!.Close Unity and relaunch the project so that it loads the freshly updated steam_appid.txt.Open the steam_appid.txt which now resides in the root of your Unity project and replace 480 with your own AppId.The included editor scripts will copy steam_appid.txt into the root of your project. You may wish to grab the SteamManager MonoBehaviour.The Standalone/ folder does not need to be imported. Copy everything into your project’s Assets/ folder.Option B: Download the latest version from the Github master branch ( direct link).

Import everything into your project’s Assets/ folder.To use Steamworks.NET you must already be a Steamworks developer. The simple instructions to get you up and running with Steamworks.NET!

Steamworks api