Firstly, if you are walking into the same game room from different locations on the map, it won't assume they are the same room, and will make a new one. So you need to make things line up on the map in order for it to work properly in that regard. Secondly, depending on how doors are handled on you...

When trying to do things in an organized manner, you want to use ipairs, not pairs.

No, only for Geyser labels.

I just tested it in 3.19.0, on a Mac, and it worked as expected. When I click and drag in the middle of the label, it moves around. When I click and drag within the label close to the edges, it resizes the label.

To do the resizing, you just need to click near enough to the edges of the label, and when you drag it will change the size of the label, rather than move it around.

So, I went to your game, took your script, and modified it until I got it working, at least to the extent that I can wandering around in the starting city of Midgaard. Here is the code I'm using: map = map or {} map.room_info = map.room_info or {} map.prev_info = map.prev_info or {} map.aliases = ma...

EDIT: See below.

So, to capture your prompt, I would do this: map prompt %(PowerLevel:<[%d%.]+b%|[%d%.]+b>%) If the "b" part of things can change, then you can replace each of the two 'b's with %a instead, so it will match any letter. Then, to capture the exits, I would take the Multi-Line exits trigger and modify i...

What you would do is make a script, with the code like so: local highlight_strings = {"string one","string two","string three"} function do_highlight() local index for i,v in ipairs(highlight_strings) do index = 1 while selectString(v,index) > -1 do fg("red") index = index + 1 end end deselect() res...

While the original version of this script works with Mudlet 2.1, the current version does not. It uses numerous changes that have been made since as part of how it functions, including the error you noticed here. Fixing this particular error would be easy, but it would just lead you down a path of h...