I am also interested in this problem
Including things from luarocks can be difficult, especially if you're trying to support all three OSes Mudlet is available for, as several of them include c bindings. For just personal use you can setup luarocks to use the same build chain as Mudlet and install them using LuaRocks as normal, but for sharing with others I've yet to come up with a good workflow for that. I did get started on working one out that I could use to repackage luarocks as mpackages but haven't had time to properly test i...
kill alias
and I don't think what you typed is necessarily easier than inputting it in two spots. But we may just have to disagree there.
.
you can click and drag this window to another side, make it pop out, or click the X on the far right
Rooms dialog
The room number in the centre of the Room Exit is the Id of the room you are setting the exits from - it is there for information only (like the room weight below it) and cannot be changed (the cursor should change to the Forbidden one whilst you hover over it IIRC). The special exits (if any) are shown in the table at the bottom and you need the room Id that the exit goes to in the left most column AND the literal command to send to use that exit (or for I.R.E. MUDS - and StickMUD - which have their own special mapper package included which can run predefined scripts to access a special exit the name of that script preceded with the word
script:) in the rightmost column.
If the id number of the room the special exit goes to is NOT valid it will be red - though I have a work in progress to change that to a more styling friendly icon something like: ✅ /⚠️ / ❌ for valid room id (in same area) / valid room id in another area / invalid (non-existent room id......