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.
When syncing object delta information, special care has to be taken for Skull Levers on dlvl=16, since all levers in a group must be pulled before opening the trigger area (refer to the _oVar8 check of OperateLever). This check is not performed when object delta information is synced, and as such, if a player walks down to dlvl=16 when another player is already on dlvl=16 and has opened one Skull Lever (but not all Skull Levers) of a group, then for the new player entering dlvl=16 (and thus receiving object delta information from the player already present on the level) would have the lever group trigger activated and the map changed, even though all Skull Levers of the given group have not yet been pulled. As such, the map state of these two players will differ considerably.
Edit: furthermore, the
_oVar8
check is done for other object delta information sync functions (e.g.SyncCrux
).