You really have to play with it in order to get it to work correctly. Here are some of the rules of thumb mostly for Cmud users:
1) The biggest thing is to set the options in Genesis not to wrap.
Code: Select all
options screenwidth off
2) Set #NODIR triggers for all the "error" messages in movement. #NODIR tells the mapper that your attempt to move in that direction failed. Set one for all the ones in the area you are mapping. One basic one is
Code: Select all
There is no obvious exit*
Code: Select all
#TAG name %1
#Tag desc %2
5) Edit your maps as you go. It's better to fix the problem with a room right then and there then edit a mistake later. Yes, this is tedious, but it happens.
6) There are some areas will require quite complicated logic in order to capture. In CMUD, I had to create my own custom map trigger in zscript. Here is an example of what I mean:
First, I had to create a variable with all the short names of the rooms in an area:
Code: Select all
#VAR MatchingRooms {On the road|On the plans of Solamnia|etc...}
Code: Select all
^{~> |}({@MatchingRooms}).[a-zA-Z ,].[a-zA-Z ,]. (*)
Code: Select all
#Tag name %1
#tag desc %2
#TAG exit {north|south|east|west}
#OK
Hope this helps as a starting guide. If you have any additional questions, please post here so that everyone can benefit from your questions and the answers.