Open ChapelR opened 2 years ago
On the one hand, it's not an unreasonable request.
On the other, I don't want sessions to be optional for various reasons—not the least of which is mobile browsers.
On the gripping hand, it seems like a footgun for users who cargo cult, which is to say far too many of them.
Let me think about it some. 🤔
One (admittedly weird) suggestion could be to make this part of the State
API or another relevant API that is documented and not Config
, which is a part of the documentation I think non-power users who are likely to misuse this setting won't find as easily, and maybe slap a dire warning on it to boot. That doesn't solve the cargo cult issue per se, but it should keep the setting out of common circulation. That said, I feel that the available means of clearing session storage are not laborious, and I do appreciate that a setting like this will be misused no matter what.
Is your feature request related to a problem? In a "game" I've made, I don't need session storage. The player plays small scenes in any order they want, the only stateful thing is whether a scene has been completed, so after a browser refresh it makes sense to just send them back to the main menu where they select these scenes from, where save data is autoloaded anyway. This also allows me to make a lot of data for the individual scenes non-stateful.
Describe the solution you'd like. While I think the game session being preserved makes sense in the vast majority of cases and should continue to be the default going forward, I would like to see a config setting to disable session storage and allow a normal engine restart.
Describe alternatives you've considered. Right now I am clearing session storage with the unload event, which works totally fine. I think a config makes sense and would be preferrable, but there are certainly other valid options to achieve this effect.
Additional context. Add any other context or screenshots about the feature request here.