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

The Witness: Fix Shuffle Postgame always thinking it's Challenge Victory #3504

Merged
merged 2 commits into from
Jun 15, 2024

Conversation

NewSoupVi
Copy link
Member

@NewSoupVi NewSoupVi commented Jun 9, 2024

In the last reworking of automatic postgame, I changed some stuff about how the victory location is dealt with in postgame.

There is a pretty major bug with it.

handle_postgame uses the victory location before it is actually set, so it just uses the default value every time, always acting like it's Challenge Victory.

This makes shuffle_postgame just not work correctly at all.

Considering this a blocker because a whole option just doesn't work and results in people having locations in their seed they don't want.

My base unit tests PR is not merged yet so I can't add a unit test for this yet, but I can make that property not have a default value, so it errors when it's not set

@NewSoupVi NewSoupVi added affects: release/blocker Issues/PRs that must be addressed before next official release. is: bug/fix Issues that are reporting bugs or pull requests that are fixing bugs. labels Jun 9, 2024
@github-actions github-actions bot added the waiting-on: peer-review Issue/PR has not been reviewed by enough people yet. label Jun 9, 2024
Copy link
Collaborator

@Exempt-Medic Exempt-Medic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merged in the change and checked that the proper locations were being removed from the postgame. Removing the default value makes sense and properly throws an error in the old code

@NewSoupVi NewSoupVi added waiting-on: core-review Issue/PR has been peer-reviewed and is ready to be merged or needs input from a core maintainer. and removed waiting-on: peer-review Issue/PR has not been reviewed by enough people yet. labels Jun 9, 2024
@NewSoupVi
Copy link
Member Author

NewSoupVi commented Jun 9, 2024

Putting on core review because it's 1 line change + moving 1 block of code

@NewSoupVi NewSoupVi merged commit 2a11d61 into ArchipelagoMW:main Jun 15, 2024
17 checks passed
sflavelle pushed a commit to sflavelle/Archipelago-tgc that referenced this pull request Jun 20, 2024
…ory (ArchipelagoMW#3504)

* Fix postgame thinking it's the wrong panel

* Also don't have a default value for it so it doesn't happen again
qwint pushed a commit to qwint/Archipelago that referenced this pull request Jun 24, 2024
…ory (ArchipelagoMW#3504)

* Fix postgame thinking it's the wrong panel

* Also don't have a default value for it so it doesn't happen again
GameWyrm pushed a commit to GameWyrm/Archipelago-GW that referenced this pull request Jul 4, 2024
…ory (ArchipelagoMW#3504)

* Fix postgame thinking it's the wrong panel

* Also don't have a default value for it so it doesn't happen again
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects: release/blocker Issues/PRs that must be addressed before next official release. is: bug/fix Issues that are reporting bugs or pull requests that are fixing bugs. waiting-on: core-review Issue/PR has been peer-reviewed and is ready to be merged or needs input from a core maintainer.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants