You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched for existing Bug Reports and found no similar reports.
Expected Behavior
When loading a new encounter, if the previous encounter was in a started state, auto-save the encounter. Including the HP and conditions of all creatures and players.
rationale: The user might have paused the battle at the end of the session and during preparation for next session accidentally started a new battle without meaning to lose the current battle.
Current behaviour
embellishments:
auto-save the previous five encounters in this fashion
Have a "pause" button which appears together with the current stop/previous/next buttons which acts as a quick-save (saves with the current encounter name without prompting)
Reproduction
be me.
obsessively play with starting battles b/c the UI for the initiative tracker is cool
forget that you needed to save the big battle that you ended the last session in the middle of.
Which Operating Systems are you using?
Android
iPhone/iPad
Linux
macOS
Windows
Obsidian Version Check
1.6.5 and 1.6.5
Plugin Version
13.0.12
Confirmation
I have disabled all other plugins and the issue still persists.
Possible solution
No response
The text was updated successfully, but these errors were encountered:
Check for existing bug reports before submitting.
Expected Behavior
When loading a new encounter, if the previous encounter was in a started state, auto-save the encounter. Including the HP and conditions of all creatures and players.
rationale: The user might have paused the battle at the end of the session and during preparation for next session accidentally started a new battle without meaning to lose the current battle.
Current behaviour
embellishments:
Reproduction
Which Operating Systems are you using?
Obsidian Version Check
1.6.5 and 1.6.5
Plugin Version
13.0.12
Confirmation
Possible solution
No response
The text was updated successfully, but these errors were encountered: