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] The level select window settings gets overwritten #42

Open
japtar10101 opened this issue Sep 11, 2019 · 1 comment
Open

[BUG] The level select window settings gets overwritten #42

japtar10101 opened this issue Sep 11, 2019 · 1 comment
Assignees
Labels
bug Something isn't working priority-high Indicates the 2nd highest priority.

Comments

@japtar10101
Copy link
Member

Describe the bug

The level select's window settings gets overwritten, even if the level passed is lower than the currently stored info.

To Reproduce

Steps to reproduce the behavior:

  1. As an example, say the player completes level 3, then returns back to the start of the game.
  2. The level select will have level 1, 2, and 3 unlocked.
  3. The user clicks on level 1, loads it, then returns back to the game without completing the level.

Expected behavior

Level 2 & 3 will remain unlocked.

Actual behavior

Level 2 & 3 will be locked. Only Level 1 is unlocked.

Additional context

Carry-over from the old Bitbucket Mercurial project:
https://bitbucket.org/OmiyaGames/hg-template-unity-project/issues/71/the-level-select-window-settings-gets

@japtar10101 japtar10101 added bug Something isn't working needs-priority Indicates the priority of the issue has not been determined yet. This is the default priority. labels Sep 11, 2019
@japtar10101 japtar10101 added this to the Complete migration to Git milestone Sep 11, 2019
@japtar10101 japtar10101 self-assigned this Sep 11, 2019
@japtar10101
Copy link
Member Author

In theory, this issue is resolved, but needs verification.

@japtar10101 japtar10101 added priority-high Indicates the 2nd highest priority. and removed needs-priority Indicates the priority of the issue has not been determined yet. This is the default priority. labels Sep 11, 2019
@japtar10101 japtar10101 removed this from the Complete migration to Git milestone Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-high Indicates the 2nd highest priority.
Development

No branches or pull requests

1 participant