Honestly, i don't see that being best done through gated triggers, as you have an open ended amount of time before you are done needing the follow up trigger. Rather, it seems to me that it would be easier to just use the first trigger to enable the failure condition trigger, and possibly a third tr...

You are right that. I'm totally sleep deprived. My bad.Thanks.

Edit: Fixed the original post to use the right brackets, and pull out the other bit.

Interestingly, you can actually use tables to bypass most of the if/then stuff here, like this. local dirs = {"go 9e, 9n, 18w, 2s, 16e, 5s, 2w, 3n, 2w, 3s, 2w, 3n, 2w, 3s, 2w, 3n, 2w, 3s, 2w, 3n, 2w, 3s, d", "go 11s, 18e, 8n, 2w, 6s, 2w, 6n, 2w, 6s, 2w, 6n, 2w, 6s, 2w, 6n, 2w, 6s, 2w,...

So long as they are already using speedwalk with a delay, you could absolutely do something like that, where they set an extra delay variable in their script, that is executed, and it is reset when the continue_walk function runs its own wait timer where you indicated. And given that it would be ess...

Yeah, speedwalks with waiting included require special implementation because of the way that speedwalks work. Normally, they just spam out all the commands as fast as possible, and assume everything will go through properly. As far as I see it, there are three different approaches that could work i...

I rewrote some of your if statements just to highlight the sorts of things you can do with Lua to simplify your code. function command_count(event, command) commandCountKill = commandCountKill or 1 currentCommand = command commandCountKill = currentCommand == lastCommand and commandCountKill + 1 or ...

Instead of using an alias, you can create an event handler for the sysDataSendRequest event, and handle it that way. There is an example in the wiki, located here: https://wiki.mudlet.org/w/Manual:Lua_Fu ... urrentSend

Another way, especially if you have different actions to match different words you are looking for, is to use your matched words as keys, and the actions as entries, like this: action_table = {apple = "drop apple", orange = "eat orange", pear = "cast fireball pear"} -- ...

The description of the problem is great, as is showing it in action, but it would be useful if you showed the code you were using to generate those buttons, so we could hopefully figure out where the problem is occurring.

So, you can add in a bit to make it work in both circumstances: ^Hp: (\d+)\((\d+)\) [\s\*\d]*Gp: (\d+)\((\d+)\) Xp: (\d+)\((\d+)\) Basically, it just makes a group of characters, spaces, numbers and asterisks, and then says that your pattern should look for 0 or more of them right before the Gp in y...