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

Introduce in-game Randomizer Settings menu, remove plando mode #4804

Merged
merged 9 commits into from
Jan 5, 2025

Conversation

aMannus
Copy link
Contributor

@aMannus aMannus commented Jan 4, 2025

Introduces a new in-game menu after selecting randomizer in the quest select screen, where players can generate a new randomizer seed in-game (with their currently selected settings) as a replacement for the plando mode introduced a while back.

This menu could be expanded down the line to select already existing seeds etc, but for now we just needed a replacement for plando mode that's more UX friendly.

I'd love to get some testing on this to make sure dropping spoilers on the game window and if generating new seeds works as expected now, as rando generation as is, is quite confusing.

Looks like this:
https://github.com/user-attachments/assets/47d16955-3f61-4f55-83fb-96d894914cce

Build Artifacts

Comment on lines +270 to +272
void ShowRandomizerSettingsMenu() {
mRandomizerSettingsWindow->Show();
}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not very happy with this living inside SohGui.cpp but I've tried to extern the window pointer in other places and just couldn't get it to work. If someone has any other options I'm all ears.

@aMannus aMannus merged commit 537a57c into HarbourMasters:develop Jan 5, 2025
5 checks passed
@aMannus aMannus deleted the rando-seed-gen-flow-ux branch January 5, 2025 18:44
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.

2 participants