fix(progress): prop replication overload#58
Merged
antond15 merged 1 commit intoCommunityOx:mainfrom Nov 3, 2025
Merged
Conversation
|
Can confirm this is indeed an issue. |
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.
Resolves an exploit introduced by overextended#515 (see #55) that allows bad actors to replicate an excessive number of props and force players within sync range to crash. This is based on changes by @Maximus7474 but with some additional fixes/improvements.
ox:progressPropLimit.If you aren't already, you should be aiming to support
setr sv_stateBagStrictMode 1in all your scripts to prevent unverified client-set values from being synced to all players.