I think room control commands should be more consistent than that... two single-clicks to disable a room is something that can be done too frequently. Perhaps a right-click menu on a room, or some room controls elsewhere + keybinding. as long as they can be re-enabled the same way I think two singl...

Vadi wrote:Hm... actually before you're even connected and right after mudlet starts

Hehe yup, that's why I changed it into a script that could me made to run on a login trigger. Come to think if it, I could make it part of the 'CharName' event handler, since that only runs at login.

Sometimes, for no reason I can understand, the delete key stops working. All keybindings also won't fire. ALT-DELETE will still delete a whole word, but the delete key on it's own will not delete single letters. This applies for both the scripting window and the main window. Sometimes switching out ...

listAdd() is indeed listed in the manual. There is indeed a function defined by that name. It appears to work like a less versatile version of table.insert(). Won't be using that any time soon. On the other hand, the other two related functions look interesting. listPrint() prints a list in a slight...

You need to look at www.lua.org/manual/5.1/manual.html to see what lua functions work in Mudlet. Dunno what you're used to, but search on that page for table.insert, that's the function you need. No idea what listadd() is.

Dunno where you're getting that listRemove() function from. Change to Aside from that your code looks fine, I use similar stuff in some of my scripts.

Is it right that if i click 'All' to select it, then when i click it again, the topborder gets set to 0? Yes, that should happen whenever you click the currently selected tab. The reason I change the border is so scolling up works properly when the chat box is blocking the top part of the screen, a...

not a bug. The "pattern" in the alias window uses regexp matching to determine when the Alias is to fire. If you only want this one to fire when you type "att" on its own, nothing else, then use "^att$" as the pattern.

'or' should be 'for', in your second line. Also, if your in_love_with table is just a table of values like { "this", "is", "a", "table" } as opposed to { this = "is", a = "table" } then you probably want to use: for _,lover in ipairs(in_lov...

Looks cool, though.. One of the biggest issues that I see is that everything sort of blends together - you can't just tell at a glance where you are, where things are in relation to you, and so on..you've got to look at it for a while and try and un-jumble all the boxes and lines..and even then, I ...