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

Improve Better Victory Screen Compatibility #23

Merged
merged 4 commits into from
Apr 14, 2024

Conversation

heinwessels
Copy link
Contributor

@heinwessels heinwessels commented Jan 11, 2024

This fixes two small problems

The main goal is that it changes the disable_rocket_victory() to always set the set_no_victory in silo-script and better-victory-screen. The reason is explained in the comments. If this is left as-is it's not that bad. Rather, until K2 compat is released, a BVS victory GUI will be shown on a regular rocket launch (once). The K2 victory will still trigger as per normal.

It also adds a global.finished, because BVS does not set either the two conditions you currently check for. If this is not added then nothing will go wrong because BVS does this internally already. But it will prevent edge cases, for example if BVS is removed after FF victory is achieved, then you'll be able to trigger the victory again.

@RedRafe RedRafe self-assigned this Jan 12, 2024
@heinwessels
Copy link
Contributor Author

Removed the changes to disable_rocket_victory() because it's now part of Better Victory Screen itself. Also removed the changelog entry because I don't think this a big enough change.

@tburrows13 tburrows13 merged commit 2fb362f into tburrows13:master Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants