This makes it easier for modders to support their own settings, and is generally rather easier to write, particularly since we can rely on the GameSettings abstraction.
I've implemented one way directly in the gamesettings Attributes, & one way centralised in a single function. I don't have a _strong_ opinion on which is preferable, but it might be easier to have eberything in the one place if we assume the 'autostart' feature is kind of a secondary, debug thing. In that case, the best option might well be to do the argument -> InitAttributes conversion in JS, then parse that directly instead of what I've done here.
The diff contains both ways, but we should choose one.
- Where should the documentation go?
- Should I just make this an even more general JS path? C++ wise, the various autostart paths could be the same now, just with some clever argument handling.
- It's rather easy to extend autostart to other things, should we want to.