#How to test Steamworks API in Debug build ?

1 messages · Page 1 of 1 (latest)

devout blaze
#

I'm using the Heathen Toolkit for Unity 2022. When I follow Bobsi's video on how to set it up, it works perfectly in the Unity Editor. The Console shows that Heathen Toolkit has picked up my username from Steam and the game launches without a hitch.

When I build the game, however, to a stand-alone executable and try testing that way, it doesn't work. My bootstrap scene shows up and as soon as Heathen initializes, it starts the Spacewar game through Steam.

I'm still very new to game dev. What do I need to do so I can keep testing the same way we test regular non-Heathen Toolkit-based Unity games (as stand-alone binaries) without launching Spacewar ?

Is there maybe a runtime flag we need to pass to the executable to let Steam know we're in debug mode ? Tried reading the official Steamworks docs to make sense of it, but I'm just not getting it.

wide spoke
#

Steam doesn't care if its a test build, if you run in editor, if your testing a under steam, out side of steam or if your just running a console app initalized as your App ID

#

Steamworks SDK works the same way no matter what

#

and that includes the REstart if Reqired check

#

A process that is not under steam will check if it was launched from Steam if not it will attempt to relaunch from Steam unless stem_appid.exe is present

#

do read the article and undestand when to and when not to use steam_appid.txt

devout blaze
#

Wonderful. I made a spelling mistake 😭

My steam_appid.txt was called my staem_appid.txt

If irony were made of strawberries, we'd all be drinking a lot of smoothies right now.