[Prevention] Timeout-based Client>Server Validation for Inventory Updates #478
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
Client request server before updating inventory data
Server validation for internet dupers, log is optional and commented - kicks player if they update inventory while not online
qb-log still commented for use if that's preferred
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.
Description
Legitimate client inventory data updates will rely on a validation response from the server when attempted.
Players using internet disruption techniques to dupe items in your server will be kicked instead of data being updated and exploited once connections re-established. Additionally, if the action takes longer than 2 seconds to receive a server response for the transaction ID, player is kicked.
Two logging options can be found in the server event
'inventory:statusBreak'Checklist