Posted by: Father Tim
« on: May 01, 2020, 10:15:05 PM »I'm not sure it would be either of those things (or, at most, a tiny improvement per player at the cost of massive work to Steve).
It is assumed (perhaps that's our fault for not advertising it better) that you will only run one game of Aurora at a teim per database. If you want two games, make two spearate DBs and manually rename the one you're not using. If you want to 'share your save' then rename the database to "Bughunters_Awesome_Setup.db" before doing so, and the folks who want to try it can back up their own game (by renaming to "whatever.db") and then load yours.
Personally, I wouldn't ever want to run multiple games off the same DB. Not only as a legacy of old Aurora (where advancing time for any game advanced time for all games) but simply because bugs and crashes are common enough that I wouldn't want to risk all my games simultaneously.
Multiple games on one DB is like leaving a trailer attached to your car at all times. It may make some things more convenient, but it is still pointless extra risk.
It is assumed (perhaps that's our fault for not advertising it better) that you will only run one game of Aurora at a teim per database. If you want two games, make two spearate DBs and manually rename the one you're not using. If you want to 'share your save' then rename the database to "Bughunters_Awesome_Setup.db" before doing so, and the folks who want to try it can back up their own game (by renaming to "whatever.db") and then load yours.
Personally, I wouldn't ever want to run multiple games off the same DB. Not only as a legacy of old Aurora (where advancing time for any game advanced time for all games) but simply because bugs and crashes are common enough that I wouldn't want to risk all my games simultaneously.
Multiple games on one DB is like leaving a trailer attached to your car at all times. It may make some things more convenient, but it is still pointless extra risk.