Buffers

You can use MonkeyTerm pretty well an never have to know about how buffers work. With this knowledge about buffers you will be able to do a lot more cool work like changing the way a substitute or action work to alter text on the screen from a web event.

Have you thought about that some commands sends the output to the mud, while other simple write it on the screen (without sending it to the mud) or some just write on the web bar instead? Well... commands sending output always outputs it to a buffer, then it flushes it; sending the data from the buffer to the desired destination. Actually you can send data to different buffers and then flushing each of them one by one. Now what is all this mombojumbo about you may ask? If you're asking this you probably don't need to read this section, on the other hand it wouldn't hurt (i promise to try not hurting your feelings or bore you to deah - ehh well not really).

Say you want the commands in a substitute to output the data to the MUDResponse buffer instead of the default (for substitutes) SubstituteResponse buffer. You want to do this in order to send the result to the mud instead of just changing some text on the screen. Normally you'd just use an action instead, but now you got the option of both removing some text on the screen (witch you can't do with actions) and you get to match ANSI codes (review the sections on actions and substitutes if you're unclear on the ANSI part).

An example will follow later...