This object is in archive! 

Weird new inventory bug in the hotfix

Balloonie-cat Inflated shared this bug 4 years ago
Duplicate

I was testing the new hotfix to see if the inventory bugs had been fixed when I found this fresh one.

Repro steps as best I can tell

1) Start with an item in the engineer's backpack

2) Go to a connector (this may work on other inventories, but I have not tried). It should show up on both sides of the inventory screen. Double-click the item in the backpack to transfer it to the connector in the right-hand list.

3) Switch the left-hand list to connected inventories and search for another container on the grid (doesn't seem to matter which one). Double-click the item shown in the connector's inventory on the right-hand side to transfer it to this container.

4) Double-click the item to send it back to the connector.

5) Switch the left-hand view back to the engineer's backpack.

6) Double-click the item a final time.

Expected result: it will return to the engineer's backpack

Actual result: it will return to whatever container it went into in step 3

Alternate repro steps:

1) Connect to a grid's inventory and go to the inventory screen. For clarity, we will call the connector/inventory port you used to connect the "connection point".

2) Switch the left-hand view to connected inventory and search for a container with items in it (could be anything, as long as it has stuff)

3) Pick an item from this container. Double-click it to transfer it to the connection point in the right-hand list.

4) Switch the left-hand list back to the engineer's backpack.

5) Double click the item in the connection point's inventory.

Expected result: Item is now in the engineer's backpack

Actual result: Item has returned to whatever container it came from.


Real-talk time: I'm upset and disgusted to discover this - it took about 10 seconds to notice it, which makes me feel like y'all didn't even try to test your "fix" for the other inventory bugs. I wanna believe you did, but that just means your best wasn't good enough and you need to step it up. I just spent the last fifteen minutes carefully moving items between containers over and over, trying to probe the edges of the problem and get clear repro steps - in other words, your job. I find that kind of testing life-draining; I could barely stand to do it when I got paid to, and to have to sit and do it for free for a product I continue to shell out cash for turns my stomach. Seriously, guys, step up your action here - if you can't be bothered to do something as simple as transferring an item to a container, then to a different container, then back to you, I don't even know what you're doing in the QA department. Sorry, that's a mean thing to say, but it's also true - QA is about poking things and trying to break them so you know they are fixed, not getting your user-base to do it for you; if you can't handle that, you're in the wrong line of work.


With regret but also resolve,

-BC

P.S. Please, please up your skill-level guys - you're supposed to be better at this than some rando from the other side of the planet, and every time I have to do your jobs for you so the game I love will work again, I die a little more inside

Replies (1)

photo
1

This is not a duplicate - the bug you linked to doesn't say anything about items being returned to whatever container they came from instead of going to the topmost container in the list and seems to be about hidden containers and autoscrolling. Please remove the duplicate tag; thanks.


Edit - just double-checked, reading the other one carefully, and it says NOTHING about items being returned to whatever container they came from - it's all about filtering being ignored, which is a different problem. Thanks

Replies have been locked on this page!