Bug #245: Interacting with locked chests
ID | #245 |
---|---|
Submitter | Plasmastar |
Product | EOSERV |
Severity | Normal |
Status | OPEN, CONFIRMED |
Submitted | 17th Apr 2013 |
Updated | 3rd May 2013 |
Fully functionality if you ignore the client and send the packet anyways.
The behavior on EOMain is to send back a Action:SPEC_Family:CHEST packet, specifying it's locked. Albeit, EOMain does send back the list of items in a locked check if you ADD/REMOVE items. It might be good to do a small check for a key anyways.
Comments
Sorry, that should say "Full functionality" and "locked chest", not "locked check". Wish to have edit button...
Oh, yea I noticed that there was no key checks whatsoever in the chest code, how odd. ;.;
Chest keys are weird, and unimplemented.
Updated Status to CONFIRMED
Add Comment
Please don't post unless you have something relevant to the bug to say.
Do not comment to say "thanks" or "fix this please".
Please log in to add comments. EOSERV Bug Tracker > Bug #245: Interacting with locked chests