I'm not sure what you are asking. Are you asking if Mudlet restricts the size of the send buffer? The answer would be no, it doesn't. The buffer size is infinite. I recommend looking at your MUD driver code (too small input buffer) .

As far as I can tell, it will match any line containing both the color and the substring in it at any point. So if I wanted to look for a <red>apple, it would match that, but it would also match a <green>apple and a <red>pepper. If I put the substring first, I would expect that, since it would matc...

Also, color triggers don't respect order in AND triggers, so having a substring for the first pattern, and a color for the second matches exactly the same as if you reversed them. No, that's not correct. For a detailed explanation of the MSM have a look here: http://mudlet.sourceforge.net/wordpress...

NVDA's IA2 implementation doesn't help in our case because we're dealing with constantly changing page contend i.e. the displayed text is just a small part of a large fast growing buffer. Updating the displayed text screws NVDA's cursor badly.

SAPI provides callback funtions to let Mudlet know when a line, word or even phoneme has been read. Thus, Mudlet can feed the speech engine directly with the necessary data. I'd say that a word or line based callback would be all we need.

1. If the only skipping you allow is using up/down (like you said in the previous message), handle the queue yourself. Gather it, then send it to the screen reader line by line. When the user wants to skip a line, stop speech, and continue to the next loop (I.E. next/previous line based on what key...

local addRoom, setRoomArea, setRoomCoordinates = addRoom, setRoomArea, setRoomCoordinates

What's this supposed to be

Put debug messages into your script to find out where Mudlet hangs. If it hangs in any of the mapper functions, post a copy of your map file please.

Don't press any keys until SAPI is ready and Mudlet starts to read the game text. Then you can use the cursor up and down keys on the left side of the num pad to scroll through the game text, skip lines etc.. control+return forces the cursor to the end of the buffer immediately. control+cursor down ...

Filtering the input stream before triggers run is impossible. Initially, I had this filter feature on my main feature list in the very beginning of Mudlet, but it wasn't implemented because there are way too few use cases and these cases could be better handled on the server side using the ATCP/GMCP...

As a general rule triggers always match against text from the game. Depending on your specific needs you have a variety of ways to address your problem. Here's a new detailed explanation of the trigger engine: http://mudlet.sourceforge.net/wordpress/wp-content/uploads/2013/03/mudlet_technical_refere...