Recently, I was annoyed for accidentally closing OpenTTD on Android and delaying some really annoying processes, especially when placing signals. This is because the game will undergo autosave every game months by default, and this value is not based on real-life time. This leads to a problem that if I pause the game time and build a lot of things, the progress will be ruined if OpenTTD is accidentally closed, since there aren't any autosave files to recover.
Therefore, the autosave system needs an upgrade. I suggest 10 real-life minutes to be the default autosave interval, but the value needs to be configurable.
Autosave interval should be based on real life time spent in-game
Moderator: OpenTTD Developers
-
- Engineer
- Posts: 24
- Joined: 11 Aug 2021 16:29
Re: Autosave interval should be based on real life time spent in-game
An alternative solution to this problem might be to create an exit save when OpenTTD is terminated.
-
- Engineer
- Posts: 24
- Joined: 11 Aug 2021 16:29
Re: Autosave interval should be based on real life time spent in-game
Well in this case exit save need to be also performed when OpenTTD is terminated by the system, not just when the "exit game" button is pressed.
Re: Autosave interval should be based on real life time spent in-game
Yes, but at least on PC (both on Windows and on anything Unix-like) that is no problem - when a process is terminated by the OS, it generally first gets a request from the OS to orderly terminate itself, at which point an exit save can be created.kcl504sandboxgamer wrote: ↑14 Aug 2021 00:47 Well in this case exit save need to be also performed when OpenTTD is terminated by the system, not just when the "exit game" button is pressed.
I am not an expert on Android but would assume that holds true there as well, especially because I have seen games which do automatically persist their state when closed.
Who is online
Users browsing this forum: No registered users and 23 guests