Zugg Software :: Search

It wasn't behind anything. Clicking it in the list of windows under the menu-Window command doesn't do anything different than the other methods to invoke it.

This was the problem: It didn't minimi ...

No matter how I try to open it (right-click, Ctrl+P, toolbar), the room properties window will not appear.

Earlier I had that window and the documentation window and the map configuration window al ...

Indeed, I started this thread to get help with MXP tags. After reviewing everything said here, going over the documentation, and looking again at the raw server output, I figured out the problem I was ...

Daern, I thought I made it clear that I understood that this particular limited functionality of multi-state triggers was by-design, which is why I said:
A redesign of multi-state triggers to remove ...

Hey Hazram, I've been working on the same problem. We have probably duplicated each other's efforts. Are you going to post your solution any time soon? It would likely save me a lot of time.

It was useful to learn that ESC[5S will match a lot of MXP, though it won't discriminate. Apparently ESC[5S matches MXP mode changes, which precede every MXP tag on my MUD. I'll experiment more with M ...

It did occur to me that the window might be hiding somewhere, so I cleared the desktop and scrutinized. Shortly afterwards, other apps starting acting anomalously, so it wasn't a problem with CMUD. A ...

The Editor (not the package editor) won't open by any of the means I know of: Tools->Editor, Shift+Control+Enter, Editor button on the toolbar.

I have figured out that using the script editor to view ANSI codes turns a lot of MXP tags into: <esc>[5S, which can then be matched with an ANSI trigger. This is useful, and answers my most pre ...

Aha. I really should have checked there - I didn't realize the "New" dropdown menu was dynamic. Thanks much for helping this CMUD newbie Very Happy

Maybe I'm just missing something, but I can't find any easy way to make a multi-state trigger in the package explorer. I've tried inserting the xml from another trigger into the xml for the top-level ...

Thanks for the offer :)

Ok, I scrutinized my raw output and learned a few things, and went over the spec again. I still can't manage to match the vast majority of tags in my output with MXP or rege ...

Ah, okay. I find the specification pretty hard to understand, partially due to my lack of background knowledge about XML, HTML, etc., and partly due to the style it's written in - not really designed ...

from the Specification:

To ensure that tags are difficult to send by MUD players, an escape sequence, similar to ANSI or VT100 is used:

<ESC>

The only tag I've been able to catch with ...

I tired that, but can't get that to work either. Here's some output from a log, showing tags:
<u>@</u>

I tired an MXP trigger with pattern:
u

And got no match.

From the help fil ...

I'm trying to figure out how to match MXP tags with regular expressions - any help would be much appreciated.

I gathered from the MXP specification that tags begin with <ESC>[# so I tried \e\ ...