You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Items disappear and are essentially destroyed if placed at same time as a lag spike.
After picking up an item from your inventory, it will change your cursor until you place an item down in inventory, equip it, or drop it out of inventory. If you click to place it down at the same time as a lag spike, the cursor reverts to normal, the item disappears and is permanently gone.
To Reproduce
Join game on ZeroNet with user that causes a lag spike every 5-10 seconds.
Open inventory and pick up an item so it becomes your cursor
Place the item back down in an open spot in the inventory at the exact moment of a lag spike
Notice the cursor reverts and the item permanently disappears
Expected Behavior
The cursor does not revert until the item is placed. Items should never spontaneously disappear.
My suspicion is that cursors lose their current state if the state attempts to change at the moment a lag spike occurs. There are likely more manifestations of this.
The text was updated successfully, but these errors were encountered:
Operating System
Android
DevilutionX version
1.5.2
Describe
Items disappear and are essentially destroyed if placed at same time as a lag spike.
After picking up an item from your inventory, it will change your cursor until you place an item down in inventory, equip it, or drop it out of inventory. If you click to place it down at the same time as a lag spike, the cursor reverts to normal, the item disappears and is permanently gone.
To Reproduce
Expected Behavior
The cursor does not revert until the item is placed. Items should never spontaneously disappear.
Additional context
Related to similar issue #7151 (comment)
My suspicion is that cursors lose their current state if the state attempts to change at the moment a lag spike occurs. There are likely more manifestations of this.
The text was updated successfully, but these errors were encountered: