That is exactly the problem, only better explained. I pick something up and the list sort of shuffles again. Thanks for reacting so quickly. :)
OK, I see it now. I suppose I just became accustomed to the default COAS behavior and needed to pay attention. I also figure the reason for the current behavior was for speed/efficiency as what they are doing is swapping the current item slot you just took from with the last item so that no shifting of items needs to take place. Shifting everything one slot, or sorting takes a little longer. But truth be told, we're talking so few items that I don't see a problem with shifting them. I put this on my list to do and it probably won't take that long to put this in the next ERAS update. I am not sure I will do it for COAS or GOF, but for sure will do so for ERAS.
Upon investigation, it turns out I was mistaken about that behavior was "always" that way. No, I accidentally introduced it for precisely the efficiency I mentioned, not the original devs. During an "attribute" deletion, I added the "swap with last element, then delete" behavior because it was quicker and there can be many attributes and deletions where a good deal of benefit could be obtained by changing the "shift every element after a deletion" instead with my "swap deleted element with last and delete the last." This had the unintended side-effect during the loot screen because it deletes the item as an "attribute" so then it swaps with the last. I added a feature in the engine to preserve the order in any special cases we desire to preserve order and added that special case to the loot screen; most of the time, we don't care the order of the attributes, so I wanted my efficiency change to remain in effect in all other cases right now.
Update Maelstrom first, then update ERAS, COAS, or any GOF version; I made the fix for all of them since this was actually contrary to original behavior, since it was my engine change that caused the problem, it made sense to fix them all.