CI>> A road
CI>>
CI>> ####r####
CI>> ####r####
CI>> f###*rr##
CI>> ff####r##
CI>> fff###r##
CI>>
CI>> You are travelling upon a dirty old road.
CI>>
CI>> Exit(s) [ n e s w ]
CI>Wow. Real Hard. Just incorperate the map into the description. Sure,
CI>It'll take a bit longer to load, but it won't have to run the automap
CI>code everytime someone moves or looks. Oh, and the exits thing is just a
CI>varient of the autoexit code.
HARD CODE it? No way! What would the point of that be? An automapper
routine should handle parsing the surrounding rooms and generating a
displayable map on it's own.. so if the zone changes shape and expands
(and that never happens, heh) then there is no need to worry about
redrawing all of the maps.. I suppose if one had a tiny MUD and wasn't
planning on doing much expansion, then simply hardcoding the maps into
the description would be an option, but for a robust, flexible, and
highly active MUD an automapper routine is a must.
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST