Repository navigation
docs(conventions): make a reload reach every reader of a setting - #32
Merged
Merged
Conversation
siracozmen01
changed the title
siracozmen01
force-pushed
the
docs/reload-reaches-listeners
branch
from
November 2, 2026 18:59
e50fe56 to
ccd77c4
Compare
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.
uxmEssentials' command control said its reload was applied while its listeners kept the lists they were built with, so edits waited for a restart. The reload rule now says every reader reads the swapped snapshot, what players already see is sent again, and a setting that cannot change for an online player is named in the reload report.