Sadly, the IRC support in Mudlet is hardcoded to a specific server and port. I did add support to give the option for it to connect to any server and port at some point, but it was rejected. Forget the reason why, but it was a valid concern.

Honestly, I can't stress hard enough just how bad an idea it is to use a prompt detection trigger for this. You're going to experience severe performance issues before long.

It's just 'saying' that it's connecting to #mudlet-help. It does actually connect to #mudlet. (This was changed in 2.0 iirc).

Do I smell a new feature?

Can you post a screenshot of the script? This definitely, 100% works. I use it extensively in every single one of my IRE systems.

I've done a lot of work on the IRC support in Mudlet and I have never seen this happen. Ever. Would need more information before this can be debugged if possible.

Your screenshot also shows it connecting to #mudlet-help. This is an old, unsupported Mudlet version. It now connects to #mudlet.

Just add gmcp.Char.Status as the registered event handler and so long as the script name is the same as your function, the function will be called whenever Mudlet receives a char status string. As for the font size, you can literally just pass it as raw HTML: local out = [[<font size="12">...

Yeah, I'd not use an isPrompt() call for other reasons aside of those stated, though to quickly respond to setting the font size, just pass setFontSize() to your label. You also do have the option to pass HTML directly to one.

Seems odd. Did you try inspecting the map file and correlating how things look for the new area against some others? Maybe they just broke the map file or it became corrupted in some way. (Can try deleting it and forcing a redownload).

Seems somebody missed a step. grab this: https://github.com/vadi2/mudlet-lua and cp the folder over to the install dir.