Spacewar Only works in Standalone mode, Game Build doesn't work

When I play the game through the editor in standalone mode, the game gets detected by steam as Spacewar, but when i build the game (whether it be Dev build or shipping) it doesnt detect the game, therefore multiplayer doesn’t work.

I’m using Online Steam Subsystem plugin. Modified the DefaultEngine.ini file accordingly.

What am I missing?

Im using UE 5.6.1

Hello @August831 ,
I’m sharing the official Unreal Engine documentation on how to set up your project for distribution on Valve’s Steam platform.

I’m also sharing this forum post, which discusses several possible solutions to the same issue you’re experiencing.

Hope it helps!

Standalone from the editor and a packaged build initialise Steam differently, and that difference is almost always the same one: the editor already knows your app id, and the packaged exe does not.

Before changing any config, find out whether Steam is initialising at all. Run the packaged build with -log and look for:

LogOnline: OSS: Creating online subsystem instance for: STEAM
LogSteamShared: Loaded Steamworks

If the STEAM line is missing, your config did not reach the build, so check the OnlineSubsystemSteam plugin is enabled for the packaged target and not only for Editor. If the line is there but SteamAPI_Init then fails, Steam is running but cannot work out which app you are. Two different problems, two different fixes, and guessing between them is what costs the evening.

On the app id itself, I will give you what actually worked for me rather than the usual advice. The usual advice is to drop a steam_appid.txt containing 480 next to the executable, and if you try it, note that a packaged Windows build has a small launcher exe at the root and the real binary at YourProject/Binaries/Win64/YourProject.exe, so it has to sit beside the real one.

That did not work for me in a packaged build. What did was using a real app id from a Steam developer account and installing the build through Steam, so the client sets the app context itself and nothing has to be inferred from a file. If you are only proving that a connection works, 480 is worth ten minutes. If you are going further than that, the developer account path is where you end up anyway, and it removes this whole class of problem rather than working around it.

Also confirm the Steam client is running and logged in when you start the packaged build. Running standalone from the editor you almost always have it open already, which makes it an easy difference to miss.