Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

  • #000304

  • 5 - Critical

  • Working as Intended

Issue Confirmations

  • Yes (1)No (0)
Photo

Mail System Defect, No State Locking

Posted by Hercules Bot on 25 October 2007 - 10:01 PM

Originally posted by theultramage
http://www.eathena.w...ker&showbug=304

Currently, chars don't get sent into a 'mailing' state that would restrict them from doing normal actions (similar to how you can't do anything while having kafra storage open). The lack of state means it's impossible to know whether you have a mailbox open or not, therefore the server can't prevent you from
1. moving while having storage open
2. sending arbitrary mailbox manipulation request packets, even when mailbox wasn't opened
3. dropping an item while sending it as an attachment at the same time

Third lets you duplicate items any time. At the moment, there aren't any checks for whether the char actually has the item in his inventory.
After a small modification (adding checks, and a mail deletion request if they fail), this problem's solution becomes identical to that described in bugreport #232.

Regarding the first two, we're lacking a "mail window closed packet" that would solve this. Problem is, it might not exist...

Ind 
changed status to: Working as Intended

Flagging as 'working as intended' because the feature doesn't have a close packet, the item dupe part was fixed years ago and is no longer possible.