ben-lear
commented
3 months ago As far as implementation would be concerned:
- Have the game save the session immediately on option select with the selected option
- If they try to reload or they disconnect for whatever reason, on reload when it loads the encounter, only the selected option is available to choose, the other options are disabled
This would not be terribly difficult to implement, and after discussion with some other devs, I don't believe it would have any impact on save requests being sent to the server. The save would just be cached on the browser until they hit the 10th wave for the biome, so no server impact.
We very briefly gathered some opinions on whether it's worth it the server overhead to add some sort of "saving" feature to Events, so as to avoid reloads bringing you back to the beginning of the Event, rather than after the option you picked.
On the one hand, not adding this would save some energy/memory (sorry I'm not being so technical) and the argument can be made that people can 'cheat' all they want in a single-player mode.
On the other hand, allowing save-scumming limits us in our design possibilities, and takes away merits ('bragging rights') to the 'completionists' players who manage to do it without save-scumming.
Something something some other considerations.