Removing the during-load condition duplication fix #785
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
still222
changed the title
notfood
added
fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Apparently, part that was suppose to prevent condition duplication during the initial load desyncs on new client connect when condition causers present.
Main part of the fix still works fine.
Ideally, I want help here, as
Multiplayer.LocalServer.FullyStarteddoesn't do correct job for stopping conditions from duplicating (as it affects only 1 client locally). It needs something to return false during that stop-time "Creating join-point" and similar ones.But simple removal works too, as that patch fixed only first 5 seconds after the launch and is far less important.