Automatically define DISABLESTEAMWORKS when running on non-Steam platforms

[fredsa]

Thanks for the DISABLESTEAMWORKS define in c303806.

I think it would be nice if DISABLESTEAMWORKS where automatically defined on non-Steam platforms, such as Android/iOS.

Could be as easy as:

#if !UNITY_STANDALONE
  #define DISABLESTEAMWORKS 
#endif

[rlabrecque]

So I was about to do this but... the reason why I didn't is that it would remove the symbols from usage elsewhere. I.E. You would need to wrap all steam calls with "#if UNITY_STANDALONE" as well instead of just an if(). Which while it is good practice it would inconvenience a lot of people currently.

Correct me if I'm wrong about that!

[fredsa]

I've been thinking about this some more, and realize it probably makes sense to to support both runtime and compile time conditionals.

Perhaps the answer here is to explicitly document how one would remove all Steamworks.NET APIs at compile time, i.e. wherever the docs cover DISABLESTEAMWORKS just include an example like:

#if !UNITY_STANDALONE
  #define DISABLESTEAMWORKS 
#endif

[Chaser324]

This is a nice idea, but if you're on a large project that spans many different platforms, you should probably already have some sort of build automation solution that can handle conditionally defining DISABLESTEAMWORKS through a call to PlayerSettings.SetScriptingDefineSymbolsForGroup() where it's necessary.

I also fear that trying to modify those defines outside of the context of someone's standard build workflow could cause issues or prove to be kinda pointless. Anyone already using the PlayerSettings.SetScriptingDefineSymbolsForGroup() in their build workflow could end up inadvertently undoing any additions you try to make to those defines.

[andrewspalato]

Adding DISABLESTEAMWORKS does not work when added to the scripting define symbols.