Skip to content

Conversation

@leggettc18
Copy link
Contributor

@leggettc18 leggettc18 commented Dec 12, 2025

Also comes with a menu reorganization. Please give feedback on this aspect if you think it can still be organized better!

Also randomizer/context was renamed to SeedContext because I was having name collision issues with the Context in LUS.

Build Artifacts

@Malkierian
Copy link
Contributor

Was the #pragma once lines in the files you added the ifdefs to not enough?

@leggettc18
Copy link
Contributor Author

This is a branch that I started on months ago, stopped for a while, and then resurrected, so I'm not 100% sure exactly what was happening that would've prompted me to add it. I'm fairly certain that if it's in there it's because I ran into an issue that it resolved, but my memory on that is hazy.

Copy link
Contributor

@serprex serprex left a comment

Choose a reason for hiding this comment

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

finally freestanding item shuffle not out of place. things were getting crowded with all the new shuffles

imo we should replace #ifdef guards with #pragma once, LUS already has it happening

@leggettc18
Copy link
Contributor Author

Headerguards removed, it built fine locally, I guess I didn't need them after all, not sure why I added them.

@leggettc18
Copy link
Contributor Author

Addressed review comments from @Pepe20129

@leggettc18 leggettc18 requested a review from Pepe20129 December 16, 2025 23:32
Copy link
Contributor

@Pepe20129 Pepe20129 left a comment

Choose a reason for hiding this comment

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

Just one small non-blocking thing.

@Malkierian
Copy link
Contributor

Do we care about rando settings showing up in search normally?

@leggettc18
Copy link
Contributor Author

I kind of assumed that would have been a desired behavior, is it not?

@Malkierian
Copy link
Contributor

I'm conflicted, personally. On one hand, it just works as it is, but on the other, there are so many rando options, having them clutter the search when people are looking for enhancements doesn't seem like good UX.

@leggettc18
Copy link
Contributor Author

Hmmm, maybe search filtering options are in order beyond just filtering out these, maybe we should be implementing more generic filters so in addition to filtering out rando options they can also filter out say, cheats, or something else like that. I can definitely see people wanting to search specifically for a rando option as well.

@Malkierian
Copy link
Contributor

Well, I do think that general filters probably would be a good thing, though I'm not sure how we could implement them seamlessly in a way that would be intuitive for the user. Perhaps a button next to (or inside at the right end) of the search field that would bring up a list of filters that can be applied (maybe, at first, relating to headers or CVar prefixes), that would then put the filter text into the search field so the user could see how they can apply it themselves without the filter window? Up to you whether you want to apply that here, but if not, I think you can just resolve the conflicts and we can get it in as is. Even if the rando options show up in general search, it's still better to have them there than not.

@leggettc18
Copy link
Contributor Author

Alright, got it merged up with latest develop, had to do some manual stuff for the added bean stuff, I think I got it all but a sanity check from someone else would be good.

@serprex serprex merged commit 14a241e into HarbourMasters:develop Jan 2, 2026
6 checks passed
@leggettc18 leggettc18 deleted the feat/randomizer/modern-menu-integration branch January 2, 2026 02:35
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.

4 participants