fix(spawning): coalesce and gate WorldSpawnManager environment recalcs#25
Merged
Xytronix merged 1 commit intoMay 29, 2026
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
WorldSpawnManager.onEnvironmentChanged()schedules a environment recalc for every world on every call, these are about 40000 unnecessary recalcs on a 29 world server with each using 40-70ms of tick time.O(worlds² × roles) is suboptimal, this Mixin only queues one recalc per world at a time.
Related issues
Type of change
Implementation details
MixinWorldSpawnManagerskip worlds whereWorldConfig.isSpawningNPC()is false and patches absurd recalc logic of O(worlds² × roles) to only do one recalc per worldChecklist
spotlessApplywhen necessary)