🏃Running a Build
Building and running a Steam game
Like what your seeing?
Support us as a GitHub Sponsor and get instant access to all our assets, exclusive tools and assets, escalated support and issue tracking and our gratitude. These articles are made possible by our GitHub Sponsors ... become a sponsor today!
Introduction
A typical Steam game is made dependent on the Steam client. This means that you must have Steam installed and running and logged in as a user that has access to the App Id your attempting to initialize as.
Build Testing
For proper build testing you should deploy your game to the Steam client preferably using the Content feature of steamcmd.exe as found in the Steam SDK. You can set up test aka beta packages and add addition users for testing builds before the game its self is published live.
Dev Testing
While most dev testing is taken care of in Unity Editor you may also want to test a build without necessary bothering to upload it to Steam. To do this you **must** include the steam_appid.txt file in the root of the build.
Troubleshooting
The following sections are just to help people find this information when searching in the Knowledge Base ... they all just point you to steam_appid.txt.
Closes and relaunches from Steam
You ran your build without deploying it to Steam and have not used the steam_appid.txt as required.
Crash on Launch
You ran your build without deploying it to Steam and have not used the steam_appid.txt as required.
Tries to download Spacewar
You ran your build without deploying it to Steam and are using App ID 480 and have not used the steam_appid.txt as required.
Last updated