Charasis Doors

[Tabasco]

I'm seeing a lot of doors in charasis with keyitem values of 1 (latest PEQ) and this was causing a zone crash when players clicked the door.

Based on some guides I've set what should be appropriate key items for keyed doors.
This should be every door that requires a key for that zone:

INSERT INTO `doors` (`id`, `doorid`, `zone`, `version`, `name`, `pos_y`, `pos_x`, `pos_z`, `heading`, `opentype`, `guild`, `lockpick`, `keyitem`, `nokeyring`, `triggerdoor`,
`triggertype`, `doorisopen`, `door_param`, `dest_zone`, `dest_instance`, `dest_x`, `dest_y`, `dest_z`, `dest_heading`, `invert_state`, `incline`, `size`, `buffer`, `client_version_mask`, `is_ldon_door`) VALUES
(6481, 8, 'charasis', 0, 'SBDOOR102', 167.854, 6.95582, 18.002, 0, 22, 0, 201, 20511, 0, 0, 0, 0, 0, 'NONE', 0, 0, 0, 0, 0, 0, 0, 100, 0, 4294967295, 0),
(6479, 10, 'charasis', 0, 'SBDOOR102', -167.853, -6.94283, 18.002, 256, 22, 0, 201, 20513, 0, 0, 0, 0, 0, 'NONE', 0, 0, 0, 0, 0, 0, 0, 100, 0, 4294967295, 0),
(6478, 11, 'charasis', 0, 'SBDOOR102', -6.95046, 167.856, 18.002, 128, 22, 0, 201, 20512, 0, 0, 0, 0, 0, 'NONE', 0, 0, 0, 0, 0, 0, 0, 100, 0, 4294967295, 0),
(6470, 29, 'charasis', 0, 'SBDOOR102', 62.0415, -735.728, 18.002, 256, 22, 0, 50, 20515, 0, 0, 0, 0, 0, 'NONE', 0, 0, 0, 0, 0, 0, 0, 100, 0, 4294967295, 0),
(6468, 35, 'charasis', 0, 'SBDOOR102', -51.9493, 639.698, 18.002, 128, 22, 0, 201, 20515, 0, 0, 0, 0, 0, 'NONE', 0, 0, 0, 0, 0, 0, 0, 100, 0, 4294967295, 0),
(6494, 40, 'charasis', 0, 'SBDOOR102', 541.793, 153.857, 0.002, 128, 22, 0, 201, 20514, 0, 0, 0, 0, 0, 'NONE', 0, 0, 0, 0, 0, 0, 0, 100, 0, 4294967295, 0),
(6466, 46, 'charasis', 0, 'SBDOOR102', -705.694, -51.9199, 0.002, 256, 22, 0, 201, 20516, 0, 0, 0, 0, 0, 'NONE', 0, 0, 0, 0, 0, 0, 0, 100, 0, 4294967295, 0);

[cavedude]

Edit: Was looking at the wrong column. We do indeed have doors in charasis as keyitem 1, but they are correct and are handled by Perl since multiple keys open those doors.

It doesn't crash on Linux, so perhpas a code update is needed to fix that under Windows.

[Tabasco]

I honestly didn't look into it that deeply since the guides I found said nothing of multiple keys and one door had an expected item key while the others did not.

I'm running on debian, so it's not a windows issue either.
I apologize for putting up such a hasty fix though. I'll investigate it further and let you know what I find.

[Uleat]

I didn't see where this was a long-standing problem or something that has crept up recently.

When I modified doors.cpp I did not alter the way that doors are actually checked, just how the client action is processed.

If it turns out to be something that I did, let me know and I'll be glad to take a look at it.

[cavedude]

Each door can open with a specific key, or a master key that opens them all. I didn't set this up, but it's pretty well documented on the PEQ forums.

I'll take a look at it and see if I can get it to crash, though I haven't seen any door related core dumps lately and I am sure I would have heard about it on the PEQ forums by now.

[Tabasco]

I wasn't familiar enough with the area and a player could consistently reproduce a crash so I didn't investigate in places where I should have.

It appears to be client related, but not in terms of SoF/SoD/HoT, etc. but rather an individual player install (With and without 3rd party stuff). I don't even know how that would happen, it makes no sense, but I can key for charasis on an unprivileged account and it all works fine.

This can be nuked or ignored.

[cavedude]

It appears to be client related, but not in terms of SoF/SoD/HoT, etc. but rather an individual player install (With and without 3rd party stuff). I don't even know how that would happen, it makes no sense, but I can key for charasis on an unprivileged account and it all works fine.


Welcome to my world. :)