[Bug] UI item quantity error when mining/transferring

  1. What is your character name in-game?
    Roland Vant

  2. Please explain what problem you ran into and show screenshots where possible, (JPEG, JPG, PNG)
    When mining, if you go to a market terminal → storage → drag a stack (e.g. 10 resources) to transport → keep the window open → wait til another mining process completes (i.e. 1 additional resource), you can then drag that 1 item stack to your inventory and it will display as if there are now 11 of that resource in your inventory → ship the 10 previously set for transport.

In other words, it appears to be a dupe, but when you leave and return to the world, the UI corrects and it only shows a resource quantity of 1 in your inventory.

  1. What items were you using at the time of the problem?
    None

  2. What world were you on when the problem took place?
    Ceres Delta

A similar bug occurred:

While again mining chems and chrome on CD, I went to the terminal to transfer some previously mined Vanadium. When I dragged the whole stack of vanadium out, on the next tick of whatever is mining (the chems/chrome), it re-populates the stack of vanadium into storage. I cannot drag that stack into transfer to dupe it, so it seems to be simply a UI issue.

Yes, there is still a visual bug going on. When the amount shown in storage is updated, it will recalculate the full amount you currently have and show that. Even if some items are still in the transfer window. You also cannot drag an item while its updating (if you mine something, and you are dragging it to transport it, if another one of those is mined, it will cancel your dragging, but it will not remove items already in the transport window.)

I believe this is only a visual bug at this moment. Seems to be something with the database recalculation not taking into account the items currently in your transport window and subtracting those when showing. Not sure if in the original FoM version you also had your dragging motion canceled upon resource amount changes in storage. Might have been a way to avoid you trying to put resources in transport while consuming them.

I am able to replicate that issue, so from investigating at least there isn’t an actual item duplication happening here and yes it does appear to be limited to UI design. Because when you move stuff to a “staging area” like transfer/transport to prepare that set to be moved, there is no DB calls being made yet to actaully transfer/transport the items to another container. That will only happen if you choose to submit that transaction, so yeah technically this would be a client side issue and perhaps something that can be addressed later on down the road, but not any time soon. Will keep this open though.