this post was submitted on 07 Feb 2025
549 points (98.6% liked)
Gaming
20574 readers
337 users here now
Sub for any gaming related content!
Rules:
- 1: No spam or advertising. This basically means no linking to your own content on blogs, YouTube, Twitch, etc.
- 2: No bigotry or gatekeeping. This should be obvious, but neither of those things will be tolerated. This goes for linked content too; if the site has some heavy "anti-woke" energy, you probably shouldn't be posting it here.
- 3: No untagged game spoilers. If the game was recently released or not released at all yet, use the Spoiler tag (the little ⚠️ button) in the body text, and avoid typing spoilers in the title. It should also be avoided to openly talk about major story spoilers, even in old games.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Waaay too much trouble to compare the time-of-last-save with minimum-time-to-ask-save. 🙄
Or even just "Has the menu been closed since it was saved?"
That's harder to implement. Suddenly you need to store that extra state somewhere and don't mess it up. The last save should already have a timestamp and is immutable. A lot less likely to get bugs that way.
Literally a single boolean lol
It's the "don't mess it up" part that is harder.
Do you not need to store that state to pause the game anyway? How else would you end the menu loop?
The state "the game is paused" is different from " the game is paused and saved". Sure that could be another key in some atate machine but like above: it's the "not mess it up" part that is harder.
I feel like I've seen a "Time since last save:" line on enough games to find it hard to believe that "paused and saved" is difficult to check for lol
These are variables that already exist in most games, it just needs one more line of code to check them