Extending Undo Functionality #157
Comments
drwhut
added a commit
that referenced
this issue
Dec 8, 2022
Functionally, nothing should be different. - push_undo_state now takes an additional argument, 'func_name', which automatically checks the timeout for that function. - Functions have been made to disable and enable the creation of undo states. This should account for multiple calls within a call stack. - Instead of storing timers which count down every physics frame, OS.get_ticks_ms() is used to store the last time at which a function was called.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently an undo state is created for:
When you play a pre-setup boardgame you usually don't spawn in or remove any pieces. The game is already setup and you just play.
In this case no new undo states are created.
Sure we have the autosave functionality but it seems kind of a waste if the undo functionality is not usable. Even after 20 minutes of playing you could hit "undo" and end up at the start of the game.
Describe the solution you'd like
Adding undo states for more actions:
Timeouts could be set to like 1-3min each?
Also the hand state should be included in the undo states. It is never included currently - so using undo will ignore the hand cards?
Describe alternatives you've considered
Using autosaves instead. However, the undo functionality seems only half implemented this way (to me).
The text was updated successfully, but these errors were encountered: