Repository navigation
workshop phases leave optional mods out - #24487
Merged
IDCs merged 1 commit intoOct 12, 2026
Merged
Conversation
workshop phases leave optional mods out
IDCs
approved these changes
Oct 12, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Cherry-pick of #24485 into
release/v2.9.Optional mods install after every phase, so the Collections Workshop shows them as "Optional" in the Phase column and its grouping, and "Assign order" is disabled on them. The phase menu lists the phases the required mods use plus one new phase. Switching a mod between required and optional drops its phase, so a mod made required starts in phase 0.
getCollectionTotalPhases returns the number of distinct install phases, the optionals counting as one, and getCollectionCurrentPhase walks only those phases.
fixes LAZ-1009