Compatibility with Restrict Markers #32
Open
Conversation
This file contains 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.
The mod Restrict Markers handles any received global marker and turns it into a local one on any client that is close enough to the creator. Internally it handles the markers of a dedicated server so that the server receives any created marker, but does not duplicate it if it is re-shared to others.
However, the re-sharing creates new local markers on clients, which are then recorded by OCAP events and sent to the server. This causes the server to record many duplicated markers, which harms playback performance.
My fix checks whether Restrict Markers is loaded and enabled on the server, and if so blocks any OCAP marker event on clients from being forwarded to the server.