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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
table.wipe(playerItems)
?Looking at the file, should just wipe it when triggering
QBCore:Client:OnPlayerLoaded
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated to use table.wipe.
I assume you meant QBCore:Player:SetPlayerData
However would we want to do this table wipe if the player is using ox_inventory?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does qb not support logout at all? That's when I'd assume you want to wipe the table.
No need to wipe for ox_inventory unless logout is a thing (which is why I suggested OnPlayerLoaded).
Forgot there's no events for individual data changes (like just items, or a single item) so it's kinda gross in that file.. setting up item count everytime something changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not seeing how this is related to login/logout. The bug we're trying to solve is that when item data changes, say from the user dropping an item, the corresponding entry within playerItems needs to be cleared so that the target code has an updated understanding of the player's items. QBCore:Player:SetPlayerData currently is triggered every time a player's items changes; and since the table is rebuilt within setPlayerItems, the missing step is wiping the table beforehand so that ghost items don't linger around.