I’d like to create build targets that allow me to “swap” between building with OnlineSubsystemSteam support, and building with the typical OnlineSubsystemNull. Basically, during development, I’d like to be testing network code directly within the editor (on one machine), and then switch to building the Steam-enabled target when I need to test it in Steam (on multiple machines).
IIRC, to properly test a Steam-enabled project, it needs to be packaged… so having a non-Steam build target seems like a decent way to avoid having to wait for building, packaging and deploying just to test changes to a single line of code.
Is this possible?
Here’s what I’ve tried:
-
File copied and changed to MyGameSteam.Target.cs
-
File copied and changed to MyGameSteamEditor.Target.cs
-
File copied and changed to MyGameSteamServer.Target.cs
-
File copied and changed to MyGameSteam.Build.cs
This gives me the following error when generating project files: