Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] New game default settings are not correctly pushed #48

Closed
CrustaShrimp opened this issue Feb 23, 2020 · 0 comments · Fixed by #49
Closed

[BUG] New game default settings are not correctly pushed #48

CrustaShrimp opened this issue Feb 23, 2020 · 0 comments · Fixed by #49
Assignees
Labels
Verified bug Bug verified, rework necessary

Comments

@CrustaShrimp
Copy link
Owner

Describe the bug
When starting the application, all default settings work.
When starting a new game from a different game, the default settings are not used but the setrtings from the previous game.

To Reproduce
Steps to reproduce the behavior:

  1. Start a game with non-defaul settings
  2. Click on New game
  3. Use default settings
  4. See default settings not used

Expected behavior

  • The default settings used when a new game is started
  • The new game screen copying the previous settings as default.
@CrustaShrimp CrustaShrimp added Reported Bug Something isn't working Triage requested Should be verified labels Feb 23, 2020
@CrustaShrimp CrustaShrimp self-assigned this Feb 23, 2020
@CrustaShrimp CrustaShrimp added Verified bug Bug verified, rework necessary and removed Reported Bug Something isn't working Triage requested Should be verified labels Feb 23, 2020
@CrustaShrimp CrustaShrimp added this to the Release v1.0.3.32 milestone Feb 24, 2020
@CrustaShrimp CrustaShrimp mentioned this issue Mar 6, 2020
2 tasks
@CrustaShrimp CrustaShrimp linked a pull request Mar 6, 2020 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Verified bug Bug verified, rework necessary
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant