Zugg Software :: View topic

Posted: Tue Aug 14, 2007 7:59 am

My mud makes extensive use of colour; So much so that room detection fails on trying to use speedwalks. If I set the mud to not use colour the speedwalks work once I've remapped the rooms. This however is a dull experience.

Is there anyway to pre-process the text that is sent to the automapper to strip out colour information?

Posted: Tue Aug 14, 2007 8:28 am

You shouldn't need to do that. How do you have you map configured? You can try changing it to map on just room name instead of room name and description. Also if you have a custom mapping script you can modify that. Finally you can come up with your own trigger(s) to send #OK (map movement confirmation command) to let the map know the mapper movement was successful.

Posted: Wed Aug 15, 2007 7:18 am

Posted: Wed Aug 15, 2007 10:32 am

Are those <font> tags MXP tags sent by the MUD, or are they html tags you wrote to try and duplicate the colour of the description?

If it's MXP sent by the MUD, you could ask them to use the RoomXXX element flags to delimit rooms. That'd help the mapper immensely.

Trouble is that the most reliable way to capture rooms, I've found, is by forcing the MUD to colour rooms a certain way and using ANSI triggers. This can't be done in your case, so I really don't know what to suggest. If you can manage to set up a full set of #tag triggers (Room name, exits, prompt, and description as well if you can) that only fire on rooms and on nothing else, you'll probably see an improvement. The trouble is getting it to that state without ANSI triggers.

Posted: Wed Aug 15, 2007 2:36 pm

Posted: Wed Aug 15, 2007 2:39 pm

Descriptions are usually the hard part, but they're not needed. It's the names and exits that're important.

Exit lines are normally always in the same format (and thus are matchable), and room names always come after a direction command (so you know which line they're going to be if you use an #oninput trigger).

Posted: Sun Aug 19, 2007 7:31 pm

I managed to get a more complete dump of the mud output - it turns out that the roomX elements are there, but improperly nested. For example -

SubAdmin Joined: 18 Nov 2001 Posts: 5182

First bit of advice it to let the mud admins know about it. It is likely a relatively small fix for them to make. Beyond that you would have to do some pretty complex scripts to overide the MXP tagging. I can't suggest going to that effort when the mud admins will likely fix it rather rapidly.

Posted: Sun Aug 19, 2007 8:14 pm

Well I have asked, and i've been told it's been put on the ToDo list - along with the other 41 items. I'm just trying to look at this from all angles.