Doors & unknown exits

[Barnabus]

Hi all,

One feature that was better supported on CMUD/ZMUD is exits. I also miss the ability to have known exits to unknown targets.

So, to bring this to Mudlet, I propose creating an exit class, containing optional target and optional door name. Converting room code to use a list of these instead of storing exits in-class will easily break the build, it means all points that need patching will stand out.

Does anyone have objections to either the idea or the approach? Obviously the mapper and exit UI will need updating too.

Phil

[chris]

I have no idea what you're asking. It may be related to exit stubs, which should be in the latest release candidate or the next one.

[Barnabus]

Exit stubs sounds like it covers the unknown exits; I'll wait until that code is in before looking at doors.

FYI, CMUD/ZMUD has a door property on exits, so that open <doorname> <dir> can get inserted automagically in speedwalks. More usefully, it also renders visually, which helps make maps more detailed.

[chris]

I just have that stuff coded in my mapper. Use the room user data to assign doors and other special commands

[Heiko]

"Exit stubs" have already been available since Mudlet-2.0-test5. Test7 or 8 will add a feature where you can add images to the map. Store door information as room user data and add an image of an open/closed door to the respective exit and you're done.

[Heiko]

Added doors + exit weights. This will get into Mudlet-2.1 this weekend.
Doors can be open (=green), closed (=yellow) or locked (red). Doors can be attached to any exit including special exits, but only n, s, w, e, nw, ne, sw and se are being visualized graphically on the map.
functions: setDoor( roomID, exitCommand, doorStatus) e.g. setDoor(1853, "n", 3)
getDoors( roomid ) returns a table with the above information.

doors.PNG (27.72 KiB) Viewed 8332 times

[Vadi]

This feature has been added and is available in Mudlet 2.1 now.