On experimental when you drop a storage item (Backpack, shirt, pants, etc..) and you remove an item from the dropped storage item, every item within the storage item disappears. In some instances where you put the storage item back on and replace the item that you took out of it, all the items that disappeared will now reappear.
Description
Description
Details
Details
- Legacy ID
- 2043899520
- Severity
- None
- Resolution
- Unable To Duplicate
- Reproducibility
- Always
- Category
- Inventory
Steps To Reproduce
- Drop a storage item (packed with items)
- Remove a single item from the dropped storage item and place it either on the ground or in another means of storage.
- Every item within the dropped storage item should now disappear
*Mainly tested on jeans/pants
Additional Information
-consistent results. mainly tested on pants.
-In some instances when you put the storage item back on and replace the item that you took out of it, all the items that disappeared will now reappear.
-This issue was first noticed 2 versions before 0.47.124.641 right before persistent items and re spawning loot were implemented. The issue still remains on 0.47.124.641
Event Timeline
Comment Actions
confirm this issue.
I had the same problem today on stable 0.47.124641.
First i had an dead spot in my backpack, so i placed the backpack on the floor. The backpack disappeard completly. I found him 2 floor higher at the same place, but the backpack was blank, no items anymore inside. I placed the backpack again on the floor, he disappeard an i found him one floor lower, but now the items where in the backpack.
I tried the same with a jacket. Droped the jack tabed it, was blank. Took the jacket back in my inventory, saw still no items. In next step i tried to but somethin in the original jacket, and the old items were visible again.
here to movies with the behaviors:
jacket: https://www.youtube.com/watch?v=LWtV-T95GgA&feature=youtu.be
Backpack: https://www.youtube.com/watch?v=gY9USoMC0HA&feature=youtu.be
Comment Actions
Hello JeanChretien,
Thanks for sending in your feedback on this issue. I'll close the ticket since it's not possible to reproduce the bug in the latest internal build.
Regards,
JStewart