There is a distressing lack of critical thinking here. I don't mind if you disagree with me, but you should at least try to get your facts straight.
"You glitched the game and lost your items as a result. Therefore you deserved it."False. I did not lose items as a consequence of using any glitch. You can
send mail with storage open simply by clicking the "Send Messages" button when your storage is open. This does not rely on any tricks or arcane knowledge. It does not bypass anything. The button is there for anyone to click at any time. It always works regardless of whether you're in storage or not. I've yet to see anyone claim that this method of sending mail is "silly" or "unintended" or "jumping through hoops."
"Fixing this particular bug would encourage 'abuse' of this 'glitch.'"False. The trick is useful only for
receiving mail. I am not aware of any bugs that can destroy items in that process. The bug that affected me (and the other person who reported it six months ago, and got the items restored) applies only to the process of
sending mail. Sending and receiving are different. How would fixing a bug with sending mail make one more inclined to invoke a trick that only helps with receiving mail? Answer: it wouldn't!
The trick has nothing to do with the bug. It is a red herring. It is completely irrelevant. I could easily have said that, instead of clicking
Inbox and then
Write, I pressed
Cancel followed by
Send Messages. Where's your glitch now?
I guess that part is true. It shouldn't be reduced until you click send. But as for the rest of it...
Hi. My comments above were not directed at you, so please don't feel offended; I appreciate your candor. I'll go over this point by point.
You're at maximum weight capacity.
You move items out of your inventory.
Your carried weight decreases.
You put more items in your inventory.
You're at maximum weight capacity again.
You try to put more items in your inventory, by closing the message.
Doesn't work.
I'm already well aware of the mechanism by which items are lost.
As you've noted, carried weight should not be reduced until the mail is sent. This was part 1 of my proposed solution in the original irowiki thread. This alone would have prevented the loss of my items in this situation, since I would not have been able to put more items into my inventory (inadvertently, I should add).
The items can't go into your inventory. There's no room.
The items can't go back in the message. It no longer exists.
So 2 options. Either the items fall at your feet, or they disappear into the aether.
The former is less likely. You aren't picking the items up off the ground after all (that wouldn't work; you'd get an error and the items would stay where they were). It would have to be programmed specifically to do that in that situation. But someone else might find some slightly different way of losing items through the mail.
Part 2 of my proposed solution was to allow attachments from cancelled messages to go into your inventory even if they would cause you to exceed your weight limit. This prevents item loss in the case where the sender is already overweight prior to sending the message. Combined with part 1, it could not be abused to carry more than you normally would because it would be impossible for you to put additional items into your inventory.
I would not recommend "Part 2" by itself since it could then be abused, but my point is that it's easy to control circumstances in such a way that it becomes an acceptable option.
So instead they fixed it by making it so you can't use both mail and storage at the same time.
Actually, there is no indication that they ever consciously intended to preclude concurrent mail and storage use. If they did, they would not have subsequently implemented a feature allowing mail to be sent at any time. In addition, the way that simultaneous storage and inbox use is normally prevented--disabling most uses of the mouse cursor when storage is open--isn't a measure designed especially for this problem, but rather a holdover from ancient times. I would consider that more of a fortuitous accident than a deliberate design choice. Incidentally, I'll reiterate that the game allows you to accept and complete trades even if you have a pending outgoing message.
Unless, of course, you use what is essentially a hack (a method hack I'm talking about here, not a code or security hack) to get around the fix they've put in place.
As I've mentioned several times, you can send mail while your storage is open without using any "tricks."
I don't intend to be rude, and hope I don't come across sounding like it. You have my sincere sympathy on the loss of your items. But I don't understand why you'd expect to be able to put more items in your inventory when there's no room in your inventory, nor where you otherwise expect those items to go.
I wasn't deliberately trying to exceed my weight limit. What actually happened was that when I tried to send one message, I missed the send button, because it was mostly obscured by an invisible portion of the chat window--the part between the tabs and the buttons (poor UI design). I didn't notice this because there is very little fanfare when you successfully send a message--just a short nondescript message in the chat window that's very easy to miss amidst the multitude of other messages, including earlier "mail sent" messages. (So I'll chalk that one up to poor UI design (again) and fatigue.) Then, when I got more items and tried to send the next message, it cancelled my incomplete one and the items poofed.
It was only after sending 30000 items, finding that the recipient had only gotten 22500, cross-checking my chat logs, drawing upon my knowledge of the bug from past investigation, and finally doing some tests to verify the regression that I was able to deduce what had transpired.
Maybe I'm just too programmer-minded. I see this as the same as when you have a big fence with signs saying "Danger! Hazardous area. Do Not Enter." and someone climbs over the fence, enters the area and gets hurt, and says they didn't see the sign. Granted, the sign is missing here, but there's still the big high fence.
Add that the fence turns invisible and incorporeal whenever anyone gets close to it, and you'd have a pretty good analogy.
Despite not being a programmer per se, I still end up doing a lot more programming than I'd like to. I know the kind of silly bugs I would never tolerate in my own work. I also know that it's not as easy to fix problems when you have to cut through so many layers of red tape. Even so, seeing the lengths to which they'll go to find excuses for doing nothing is quite simply depressing.