Fix Guidebook trigger collision between Reeling Rods and Lively Lily Pads #1254
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
It's probably better to change the lively lilypads trigger since that's the one that's not appearing in the guidebook when both modules are installed. |
BPR02
approved these changes
Jan 22, 2026
github-actions bot
pushed a commit
that referenced
this pull request
Jan 22, 2026
…vely Lily Pads (#1254) * Change Reeling Rods guidebook trigger to 123 * swap to change Lively Lily Pads
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Both Lively Lily Pads and Reeling Rods are using guidebook trigger
121. This breaks the guidebook when both are installed, only showing Reeling Rods pages.Honestly not sure how I missed this, since those are modules are both mine and I was aware of this as a potential issue