-
-
Notifications
You must be signed in to change notification settings - Fork 797
Closed
Labels
invalidThis doesn't seem rightThis doesn't seem right
Description
Describe the bug
New metadata is not updated immediately after being changed, only when the player leaves and re-enters the server.
To Reproduce
Steps to reproduce the behavior:
- Create a server-side command to register new metadata and use it.
- Create a command to view metadata on the client side and use it.
- Create a command to change metadata on the server side and use it.
- Use the command created on the client side to view the metadata.
Expected behavior
When using the command to create new metadata, xPlayer.setMeta(‘test’, 1), and viewing it on the client side ESX. PlayerData.metadata.test, the value 1 is expected. When using the command to change the metadata xPlayer.setMeta(‘test’, 50) and viewing it on the client side, 50 is expected, but 1 is returned.
Screenshots
Debug Info (please complete the following information):
- OS: Windows
- FiveM Artifact: 17000
- ESX Version: 1.13.3
Additional context
I would also add that when you create the meta for the first time and try to view it immediately, it will return nil.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
invalidThis doesn't seem rightThis doesn't seem right