You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 4, 2021. It is now read-only.
As I was fearing, the inventory is managed on the client-side, I will see if I can manage a way to force inventories update and listen on these events.
If you have any ideas, do not hesitate !
More info:
Pickup an item process (as I have understood by retro-engineering the code):
When a player pickup an item:
-> Humanoid.Pickup is called on client side
-> Humanoid.Pickup calls ItemDrop.Pickup
-> If ItemDrop.CanPickup() returns true (that means that the client is the owner of this object (Client is the owner = the server leaves the responsibility of the status of that item to the client, it's not the server who controls it anymore))
-> The local inventory is updated with the item, the client destroys the item
-> Else
-> The client sends a "RequestOwn" packet (to ask the server for the ownership of this item) and waits that the ownership of the item switch to the client
-> When the ownership switched to the client, the item is added to the client's inventory
That's exactly why it is very tricky to handle. The server is not authorative, and we will need tricks to handle it.
The text was updated successfully, but these errors were encountered:
As I was fearing, the inventory is managed on the client-side, I will see if I can manage a way to force inventories update and listen on these events.
If you have any ideas, do not hesitate !
More info:
Pickup an item process (as I have understood by retro-engineering the code):
When a player pickup an item:
-> Humanoid.Pickup is called on client side
-> Humanoid.Pickup calls ItemDrop.Pickup
-> If ItemDrop.CanPickup() returns true (that means that the client is the owner of this object (Client is the owner = the server leaves the responsibility of the status of that item to the client, it's not the server who controls it anymore))
-> The local inventory is updated with the item, the client destroys the item
-> Else
-> The client sends a "RequestOwn" packet (to ask the server for the ownership of this item) and waits that the ownership of the item switch to the client
-> When the ownership switched to the client, the item is added to the client's inventory
That's exactly why it is very tricky to handle. The server is not authorative, and we will need tricks to handle it.
The text was updated successfully, but these errors were encountered: