Yeah, these old game engines have challenges like this. You can create a trigger that goes off on the next line: https://wiki.mudlet.org/w/Manual:Mudlet ... ineTrigger, but it creates complications in scripting...

This is easiest and best fixed by asking the MUD not to wrap the lines for you, and getting Mudlet to wrap them instead - this way your triggers get 1 easy line to work with. Can you turn line wrapping off in your game?

They are supported now: https://www.mudlet.org/4-1

This is a quality release bringing improvements to Mudlet editor, Geyser, while adding MSSP, HTTP POST/PUT/DELETE, and more. Enjoy

Please provide all feedback and problem reports on 4.1 here or over on Github!

Certainly, I think you mean this option in the connection screen:

Sorry that it's being difficult. Can you post what happens when you start mapping with 'map debug' on?

Yep, just make a separate trigger for each action. You can put them into a folder together to group them!

That's pretty cool. I like the style!

Yes, it is the word wrap for the main console (and you can also set it per-miniconsole if you wish). It has nothing to do with how much data is read in: that is a low-level implementation detail that players don't have to mess around with, Mudlet makes it "just work" out of the box :) Mudlet reads i...

450 characters in a line should be fine. Try it out!