Page MenuHomeFeedback Tracker

Tent inventory has empty slots that cannot be interacted with.
Closed, ResolvedPublic

Description

I wasn't able to place items in some slots in my tent. I tried moving items already in the tent inventory to those locations and was unable to do so. I left the server and restarted my client. When I rejoined I still could not interact with those spots so I took a stack of AK ammo and split it repeatedly. Doing so resulted in skipping those bugged locations.

I am aware that sometimes items are not rendered, but usually taking an item from or dropping an item into a tent result in those spaces revealing their contents. In this case, those spots still rendered nothing.

In the attached screenshot, there are several blank spots in the tent inventory. I took a stack of ammo and split it repeatedly, and it skipped over those empty locations. It seems they are bugged, my best guess would be that the server believes there are items in those locations, while there are not, or they are not being shown.

Details

Legacy ID
3684801013
Severity
None
Resolution
Duplicate
Reproducibility
Always
Category
Inventory
Additional Information

Earlier in the day I had some food items from my inventory that I dropped into the tent in several of those locations. I proceeded to eat/drink directly from the tent. My best guess is that the server recognized they had been consumed, and rightfully removed the items from being visibly shown. However they are still considered present in those locations.

Event Timeline

zakificus edited Additional Information. (Show Details)Oct 5 2014, 4:41 AM
zakificus set Category to Inventory.
zakificus set Reproducibility to Always.
zakificus set Severity to None.
zakificus set Resolution to Duplicate.
zakificus set Legacy ID to 3684801013.May 8 2016, 8:13 PM

This might be a hard thing to do but try emptying the tent completely and pack it away then pitch it again.

I actually was going to attempt this, but there was a server restart. The restart seemed to fix everything.

andy added a comment.Oct 6 2014, 3:17 PM

Hi zakificus,
thank you for your report!
This seems to be caused by #17615 which we are currently looking into.
Regards,
Andy