Page MenuHomeFeedback Tracker

Uniform/Vest Remote Bug
New, NormalPublic

Description

Sometimes Uniform and Vest inside a container getting bugged after a restart. (Dosent happen to backpacks and also dosent happen to all Vest/Uniforms in that specific container, can happen to 1 out of 10 items inside)
You cannot take it and if the container is LOCAL to you, then your Uniform/Vest on your character will duplicate. The duplication will drop into the container (Take&Put Eventhandler are not triggering). The duplicated Uniform/Vest has the same netID then the Uniform/vest you have on your character.
The duplicated Vest and Uniform are visible to every player on the server.

It only duplicates when the Container is local to the player.

Some commands I tried to get more information:

Client Sided:

getItemCargo CONTAINER // 2 Classnames getting listed
[["U_FRITH_RUIN_sdr_fabdpm_rs","U_FRITH_RUIN_sdr_ltrdrk"],[1,1]]

everyContainer CONTAINER // 1 Container is getting listed

[["U_FRITH_RUIN_sdr_ltrdrk",21a122d8100# 1067575: dummyweapon.p3d]]

Server Side:

everyContainer (ObjectFromnetromNetId NETID CONTAINER): // 2 Containesr are getting listed
[["U_FRITH_RUIN_sdr_fabdpm_rs",1c9607436f0# 1065412: dummyweapon.p3d],["U_FRITH_RUIN_sdr_ltrdrk",1c9738bb0b0# 1074841: dummyweapon.p3d REMOTE]]

Notes:
SetOwner Command on the bugged uniform/vest container does not help.

What is Intresting that there is no REMOTE behind that object on the bugged uniform/vest.
Also in the inventory UI the bugged unifrom/vest dosent show his load bar.
I found out that the ownership on the server for the bug Vest/Uniform is 0 and not 2. It also stays on 0 when changing ownership via setOwner on a player and back to the server.

JIP
Looks the bug only appears on containers which got created & filled before a client joined ? Never happend to fresh created containers when the client is already on the server.

Details

Severity
Major
Resolution
Open
Reproducibility
Random
Operating System
Windows 10 x64
Category
Multiplayer

Event Timeline

Hungry created this task.Aug 13 2023, 4:18 AM
Hungry updated the task description. (Show Details)
Hungry updated the task description. (Show Details)Aug 13 2023, 4:21 AM

After some more Investigation I found out that the ownership on the server for the bug Vest/Uniform is 0 and not 2. It also stays on 0 when changing ownership via setOwner on a player and back to the server.

Hungry updated the task description. (Show Details)Aug 13 2023, 5:01 AM

After more investigation I found out it has something to do with the ownerShip of the vest/uniform. I'm 100% sure.

All the bugged uniform/vest having a ownership of 0 and they are stuck in there.

If a player takes a uniform and drops it back in, then the uniform has the ownership of the player.
But as soon as he disconnects the ownership needs to get back to the server and thats where the problem is getting created. It stays stuck at 0. But if its on 0 no player can interact with it and then you can abuse it duplicate items.

Also JIP dont see the items from uniform/vest which they putted into an container before reloging.

Repo (Multiplayer Enviroment):
1.Container on Server
2.Connect to server
3.Put Unifrom Inside the Container
4.Disconnect
5.Reconnect
6.Check Ownership
Execute on server: (owner (everyContainer (ObjectfromNetID NETID OBJECT) #0#1)) If its 0 , then its bugged.

If step 6 didnt work, repeat from step 5

This comment was removed by Leopard20.