Closed jimkberry closed 3 years ago
As it turns out, by the time any BeamGameCode is running there already needs to be a UserSettings instance in place - it needs to get loaded/created during the platform/driver startup sequence. So this is actually a Beam.Cli and/or Beam.Unity issue.
This is part of Beam.Unity#7 or at least goes along with it.
If loading the settings file results in creation of default settings they should get written immediately. In other words: if a player starts a game and then exits without ever having done anything there should be a settings file written.