Any particular reason why turning on MXP support forces me to autosay?

Did you guys change something in the formatting for displaying room names that have the (road) tag on them? Ever since you loaded this change, my IMapper has been being stupid and not recognizing road rooms properly. This happens even when MXP is configured off.

They removed the period after (road) - so, for example, where it was formerly

it is now

(note: I wrote those from memory, don't know if the room name is perfectly correct - it's an example!).

Oops, totally unintentional. Will fix this when I wake up in a few hours!

Aww. I like it this way! And, MudBot is easy to fix, if you use that...

Think you'd need access to the source to fix it, though - it's not treated as part of the room name.

Unintentional?

I bugged it and was told it was not a bug.

... and to envoy it, though it has absolutely nothing to do with skills, heh. It broke my whole map though, so fixing it will make me happy!

Easy peasy.

Aw man, don't fix it. I like it this way. (plus I fixed my mapper and triggers to match properly so don't want to do it all over again)

If you need to change your triggers anyhow why not just move to using the MXP tags? They make mapping very easy.

My mapper won't use MXP because MXP is optional and my script works without it. It'd be like requiring people to use ATCP when the prompt works just fine. Plus, MUSHclient has had issues with MXP support and I don't need clickable links all over the place.

Should be back to normal now.

So when will the and tags be supported?

Found a bug with the MXP-prompt:

Thanks!