 |
MrMaunus
Newbie
Joined: 27 Jun 2009
Posts: 5
|
 Posted: Sat Jun 27, 2009 8:45 pm
Mapper bug?
|
Hey! I'm having still 10 days of trial left on cmud and I'm considering of buying it. Today I tried automapper with Icesus mud. There are two kind of exit keywords. Exits and exit. I used trigger to change exits into exit so I could use the one keyword. Now I've had some problems with mapper to change the room I'm in. Like sometimes when I exit through normal exit (for example I type s which is for south) and mud changes room the mappers position stays in the old one. (I'm having the mapping mode on) It's rather burdening to change the position manually. The same problem when I try to doubleclick on a room on the map and do the speedwalking(?) the position more often stays in the old room. The rooms are have been mapped correctly this far. (Except sometimes the mapper doesn't map the room at all)
|
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Sun Jun 28, 2009 3:08 pm
|
A keyword of 'exit' should also match 'exits', so you shouldn't have to use a trigger to change the mud output. Try setting the keyword to 'exit' and getting rid of your trigger.
When the mapper doesn't follow you, it is usually either because it didn't notice that you were trying to move, or because it did not recognize the room. Check whether the room name and room description in the mapper match the actual room. Does your configuration have Room Description marked? Do the room descriptions change, say at night time? If so, make sure Room Description Changes is marked. It is quite common to have to manually adjust the configuration after autoconfiguration, to deal with small situations which were not noticed by the autoconfigure. Matching rooms on modern muds can be tricky. In some cases, it may even be necessary to manually tag room names in order to map properly, but hopefully that is not necessary. The built-in matching algorithms are sophisticated and difficult to duplicate with constructed triggers. |
|
|
|
|
MrMaunus
Newbie
Joined: 27 Jun 2009
Posts: 5
|
Posted: Mon Jun 29, 2009 12:42 am
|
| Rahab wrote: |
A keyword of 'exit' should also match 'exits', so you shouldn't have to use a trigger to change the mud output. Try setting the keyword to 'exit' and getting rid of your trigger.
When the mapper doesn't follow you, it is usually either because it didn't notice that you were trying to move, or because it did not recognize the room. Check whether the room name and room description in the mapper match the actual room. Does your configuration have Room Description marked? Do the room descriptions change, say at night time? If so, make sure Room Description Changes is marked. It is quite common to have to manually adjust the configuration after autoconfiguration, to deal with small situations which were not noticed by the autoconfigure. Matching rooms on modern muds can be tricky. In some cases, it may even be necessary to manually tag room names in order to map properly, but hopefully that is not necessary. The built-in matching algorithms are sophisticated and difficult to duplicate with constructed triggers. |
Firstly thank you very much for answering :-) There aren't specific room names in Icesus. The description might tell something like: "You are in the spacious bar that connects the common room of the Double Dragon Inn with the street outside." The mapper couldn't find description either on autoconfig. Should I manually try to adjust the place of description or is it futile if there's no room name? The strange thing is that sometimes mapper does map the room or change position. o.O
I think the descriptions were about the same on nighttime as on day. If I remember correct there was just some extra line telling that it's night. Not 100% sure, so I'll check out.
Here is a capture from the mud:
You are in the spacious bar that connects the common room of the Double
Dragon Inn with the street outside. Massive oak doors to your west lead
into the common room, while an open passage to your south leads out into
the street. The room is lit by a single lantern that hangs from the
ceiling. From the common room, you hear the jovial sound of laughter.
The room is, however, very spacious, so you do not have to rub elbows with
anyone if you don't want to.
The obvious exits are west, north and south.
Pidzer's merchant booth, *>Nubcakes<* (2 items)
Ragged human refugee
Hp(488/488) Ep(273/265) > |
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Wed Jul 01, 2009 2:44 pm
|
Hm. It is definitely much harder if there are no room names. Is there a way to turn off server-side line-wrapping? That may be useful. Is the extra "nighttime" line part of the same paragraph? If you turn off server-side wrapping, does the "nighttime" line get put into the same line as the rest of the description? That would make it harder.
If you can't get the configuration to recognize rooms consistently, you may have to use the #TAG command to force it, perhaps using the %line2 variable to grab the room description based on a trigger for the exits line. I don't have any experience configuring for a mud with no room names, so I hope someone else will be able to help out here. If the room descriptions are actually variable based on day/night, you might need to turn off room description capture and just recognize rooms based on the exits line. |
|
|
|
|
MrMaunus
Newbie
Joined: 27 Jun 2009
Posts: 5
|
Posted: Thu Jul 02, 2009 6:05 pm
|
Hmm I'll try to figure out what line-wrapping is. I'll also check how the nighttime worked. One guy wrote in the mud's forum that he got it working with brief mode and some triggers for the "You can't go that way"-type of cases. For me the map still wouldn't follow even if I entered brief and autoconfigured map again.
|
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
