The "Scripted Aliases" bit is indeed a folder, with the idea being to make it easier to keep them together in case you needed to delete them or something. It would be created as an alias, just as if you had created it by hand. You can, optionally, create temporary aliases, that are created...

The main difference between setting the variable in the script vs having it as a "variable" object is the value permanence between sessions. A variable object will remember its value even when you close Mudlet and reopen it, whereas using a variable declared in a script will instead always...

To make the variable persistent, but ONLY while the profile is open, you can make a blank script, make sure that script is checkmarked, and create the variable inside that script. Then it will always start with whatever value you give it in the script, without having a permanent variable created for...

In the version I'm looking at, the function capture_move_cmd starts on line 1334, this is where you are going to want to focus your attention. On line 1346, I see: local door = string.match(dir,"open (%a+)") That bit of code compares the command sent to the pattern given, and stores the ma...

As the person who wrote the basis of this script, I can say that it is at least possible, as the script looks at every command sent while it is active, to check for movement commands. So, as it already treats 'n' and 'north' as identical, it wouldn't be overly complicated to make it have a bigger li...

I didn't go into a lot of detail before because I had hoped that someone else would jump in to help, and that anyone who could help with syncing up multiple profiles in the way that you clearly want would easily be able to incorporate the idea that I mentioned without me spelling it out in the level...

So while I can't contribute to the module syncing part of this, I can say that as far as data storage and isolation goes, you could easily just have a table where you store all the relevant data at the end of each session, and retrieve it at the beginning of the session, using the character name as ...

So, it looks like what you have should work, though I'd advise you to make the roomExits variable you are using local, rather than global (just put local in front of it in the first line when you create it). With that setup, are you still experiencing any problems?

Can you post, and label, the existing exits trigger, multi line exits trigger, and the new trigger that you made that you said you got to work to capture both lines of exits, so hopefully we can work out how to get things working for you?

Okay, this is a bit of a long shot. I've been trying to get the mapper working, but I'm having issues with room exists taking up multiple lines, without actually being multi-line exits. The issue being the "and west" being printed after the script running. No combination of timers or rege...