Page MenuHomeFeedback Tracker

Vanishing items from backpack dropped-to-swap
Closed, ResolvedPublic


When You swap your backpack containing items with another backpack on ground
then items in the dropped backpack vanish
(note: items in taken backpack are correctly preserved)


Legacy ID
Unable To Duplicate
Steps To Reproduce
  1. you got backpack with items
  2. another backpack on the ground
  3. move some items from your backpack tot he ground one but keep some in yours
  4. swap the backpacks
  5. for short while the one you just dropped shows items
  6. the ground backpack invenstory list flashes and is empty now

... observe items gone from ground backpack, nothing around on ground

Additional Information

happened in 2 of 3 tries, might be related to lag

Event Timeline

Dwarden edited Steps To Reproduce. (Show Details)Dec 16 2013, 8:33 PM
Dwarden edited Additional Information. (Show Details)
Dwarden set Category to Inventory.
Dwarden set Reproducibility to Sometimes.
Dwarden set Severity to None.
Dwarden set Resolution to Unable To Duplicate.
Dwarden set Legacy ID to 1131444322.May 8 2016, 1:55 PM
Bohemia added a subscriber: lipek.Dec 16 2013, 8:33 PM
Franzuu added a subscriber: Franzuu.May 8 2016, 1:55 PM

There was a bug where dropped containers didn't show items that were in them. It has since been fixed. The items were there and slots occupied, but invisible. I think it had something to do with the guaranteed messaging system being broken. I think this was separate from the issue described here.

There are issues with dropping your backpack with valuable stuff because on laggy servers it might not show up or it will appear out of reach clipped into something or outside a building/on another floor. Or items being irretrievable because of lag or the anti loot magnet thinking you are too far away.

Items in a dropped backpack disappearing hasn't been an issue in a very long time.

IMO issue can safely be closed.

Geez added a comment.Mar 20 2015, 1:21 PM

Hello Dwarden and thank you for the report.
Unfortunately we were unable to reproduce the issue you have described. Please retest on latest build and report back to us in case the issue re-appears.