A little preface: I figured out how to have a separate window for Lusternia's built-in automap two weeks ago, which is awesome. The map output is gagged from my main window, and shows up in the Map window instead, updating as I move. It works flawlessly.

Alas, tells and aether channels aren't as easily conquered. In a perfect world, I could do this:

#TRIGGER {tells you,} {#CAP Tell;#GAG}

Problem is, that only works on one-liners. I could add a numeral to the #CAP string, but that would only capture lines above the initially captured line (additional lines of text in tells show up below, not above).

Is there a simple and/or elegant solution to this problem? I used to be fairly decent with CMUD/zMUD scripting, but it has been awhile....

CONFIG WRAPWIDTH 0

What? It's what everyone else does!

You can also make that "tells you, " trigger enable another trigger that matches on every line and captures them to the new window, then disable the trigger on your prompt (preferably not capturing your prompt across).

Hmm. I definitely get the gist of what you're saying, but not the specifics; I'm unsure what "match on every line" means, nor how I'd go about doing that. However, having the capture script begin on the line containing "tells you," and end at the prompt makes a lot of sense.

I went to the CMUD forums and actually found several threads about multistate triggers, which are apparently a requirement for capturing multiple, variable-length blocks of text. Multistate triggers are really quite complicated, however, and I'll need to read the documentation thoroughly to figure them out, which I'm not really up to just now. I'm cleaning the house and getting ready to drive across the state to see my mother for a week or so, then house-sit her pets while she's on vacation for eight days — I'll have those eight days all to myself, so I'll definitely be doing some MUDding (and learning to script) then.

This means that a tell is always all on one line, as far as your client is concerned. Way easier to deal with.

Well, yes... but doesn't it also mean that text will extend all the way over to the right-hand side of my screen? That doesn't seem worth it, somehow.

Or can I turn off server-side wrapwidth, then turn on client-side wrapwidth, getting the benefits of one-line chats without the drawbacks of no wrapwidth? That would be great.

My client, TinyFugue, can do that, but I don't know about yours. Not sure if this makes sense, but ... just make the window narrower?

Oh! That does make sense, actually. Quite a lot, in fact.

I'll have to get used to it, I suppose. I'm going to try client-side wrapping first, though.