oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
 Posted: Sat May 08, 2010 1:51 pm
Map Questions
|
Okay I will be the first to admit I have never really used the mapper in either Zmud or Cmud. I mostly just memorized the mud rooms in my head. However, I am getting older now and can't remember so good anymore.  So right now I am actually using the beta version and mapper. However, I have a bunch of issues I am running into and questions I need answered. This is an IRE mud that uses ATCP.
Issues:
1. When I first started mapping, Cmud did not record the VNum correctly from the mud using the Room\.Num (\d+) from ATCP. I put this trigger in to do so. But now my map is all messed up with some rooms not having the correct VNum before I added the trigger. This causes me problems because when I do a dash or gallop I want to teleport to the room I am ending up at and the mapper can't follow. So upon arrival I get the new ATCP info and then on prompt after the dash or gallop I #teleport to that room. Works just fine, except for the rooms that have the wrong Vnums I can't retrieve the correct room key. Anyone know how I should do this or a better way?
2. Serious problems with Other exits. When I create an Other exit like "enter grate" or something it automatically makes it a null link and won't let you uncheck the null link box even when there is a link from the other room to that room. For example, to enter the sewers you have to "enter grate" but then the room you end up at has an "up" exit back to where you entered. I can create a link from the room below with up exit to room I came from but when I open the room properties with the grate and add new link in the properties and put enter grate it again makes it a null link and won't let me change it. How do I get this to work right and how to you effectively write a script to handle other exits like "enter grate", "out", and "in"?
I'm using the following alias to create links manually:
| Code: |
<?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<alias name="createlink" copy="yes">
<value>#call %roomlink($firstVnum, $direction, $secondVnum)</value>
<arglist>$firstVnum,$direction,$secondVnum</arglist>
<notes>Creates a link between the two rooms. Use the key numbers like createlink 1234 east 234.</notes>
</alias>
</cmud>
|
Except of course you have to really use the room key and not the vnum when using it.
3. ATCP does not contain a description for the room. I can't get the mapper to effectively capture the description. Anyone know how to get that to work? Right now I am using a multiline trigger with the first line being the Room name and then capturing everything from second line. I have wrapping turned off from the mud. However, looking at some of my rooms it has the room name, which is captured by ATCP Room.Brief but then in the description it put the name of the next room I moved to. Some of them do capture the room description correctly though. How do I do this?
4. ATCP also sends coordinates of the room, room area, room environment, and room info. I'm not sure how to enter this information into the map room properties. |
|
