Those are being made in the script editor on the Button tab, I don't think they're being created by code.

In general, Mudlet works hard not to break backwards compatibility.

I think the issue is your pattern is missing the closing parenthesis to end the capture group.

dodge_current = tonumber(matches[2])

The color of the room is dictated by it's environment. See https://wiki.mudlet.org/w/Manual:Lua_Functions#setRoomEnv, https://wiki.mudlet.org/w/Manual:Lua_Functions#setCustomEnvColor, https://wiki.mudlet.org/w/Manual:Lua_Functions#getCustomEnvColorTable for some more information on how they are used...

Try right-clicking on the minimized version shown when you highlight it on the taskbar and select 'maximize'

This most often occurs when you have more than one monitor in windows and then remove the monitor that Mudlet last ran on.

Would help if you provided some output from the game so we can see what it's trying to match against

Happy to help =)

You should put the code from the alias into a function in a Script, and then call that function from both the alias and the button. For example, if the alias does send("cast 'armor' " .. matches[2]) Then you could put a function like this in a script function castArmor(target) send("c...

Coroutines are one of the aspects of Lua (and by extension Mudlet) that I feel aren't very well understood by our community as a whole, so when someone's question gave me a great example to explain them with, I decided to make a blog post out of it. You can find it over HERE . If you have any questi...

It's been folded into Geyser as Geyser.StyleSheet: https://wiki.mudlet.org/w/Manual:Geyser ... StyleSheet