I've reproduced this issue (inventory full) but with a twist:

1. full inventory
2. select reload for a magazine inside a case inside inventory (small protector case)
3. the magazine is loaded from the case
4. the magazine unloaded disappears (not swapped into case)
5. the newly loaded magazine in case can now be manipulated with an item link for both remaining inside case and loaded into the M4A1.

It takes some swapping things around to get the magazine to properly be represented by one manipulatable item. However, the original magazine is still lost.

Behavior is defective due to magazine deletion and odd double representation of a single item DB entity. I'm concerned this method could be used for item duping.

I think the satisfaction level of the toon would go way up if you could "cook"/craft a bowl of cereal with milk. But alas.... there is no spoon! (or bowl)

I don't think this behavior is caused by drink being accidently executed.

If I had to guess its reverse sick effect. Basically, calling the same function to apply sickness except sending a negative value. So instead of being a DoT its a HoT. A negative decrement is functionally an increment.

There's so many variables effecting status; it's difficult to give feedback on this system without white box debug capability. I do like the design choice of vague notification - it increases immersion (Am I sick because a zombie hit me or was it that rotten kiwi?) Also, delayed notification of status adds to that uncertainty. You first feel sick, then you have to wait for more symptoms to know what you're treating. There is no panacea. I dig it.

(Note from 2752)

I've reproduced this issue (inventory full) but with a twist:

1. full inventory
2. select reload for a magazine inside a case inside inventory (small protector case)
3. the magazine is loaded from the case
4. the magazine unloaded disappears (not swapped into case)
5. the newly loaded magazine in case can now be manipulated with an item link for both remaining inside case and loaded into the M4A1.

It takes some swapping things around to get the magazine to properly be represented by one manipulatable item. However, the original magazine is still lost.

Behavior is defective due to magazine deletion and odd double representation of a single item DB entity. I'm concerned this method could be used for item duping.