When you select an item from the hotbar, it leaves behind a "ghost" spot to where that item was in the inventory. If you leave that item in your hands and re-log, that "ghost" disappears and pressing that same hotbar button of that item puts it in the first random avaliable space in the inventory. This happens with dedicated inventory slots as well, for example, the holster.
Description
Description
Details
Details
- Severity
- Minor
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Operating System Version
- 1909
- Category
- General
Steps To Reproduce
Apply any item to a hotbar slot, press that hotbar button on keyboard, see the character grab the item, open up the inventory to see the "ghost" of the item where it was in the inventory, log out of the server, log back in, open up the inventory and see the "ghost" missing, pressing the hotbar button puts that item to the next best inventory space where that item fits in.
Event Timeline
Comment Actions
Hello Masgel.
We have tested this issue based on your report but we were unable to produce the issue. Is it possible that this behaviour is triggered by something specific? And would it be possible to provide a video of the issue for us?
Regards,
Geez
Comment Actions
Thank you for answering and apologies for replying so late.
Best way I can describe it is with this situation:
You have a dedicated gun holster on your belt and it's got a Mlock in it, which is saved to space 1 in your hotbar. Coincidentally, you also have a space in your pea coat that can also fit that Mlock. You take the Mlock in your hand and log out somewhere, 'cause you're expecting players to be there when you log in again. So you log out with the Mlock in your hand, and then log in after some time. The Mlock is still in your hand. You see that it's safe out and press "1" on your keyboard to put your Mlock away, but the Mlock instead goes into your pea coat and not into the holster, which was it's dedicated slot in the first place. A little bit of confusion, but nothing terminal.
So far I haven't been able to tie this bug in with any other action pattern.
If this still doesn't explain my point, I'll make a video.