Using a timer with a keybind

Hi, I play on a star wars based mud which has timed skills, but expects you to know when that timer is up.

Is there a way to have a timer that starts on a specific keybind (eg like inputting slash)?

Or have a trigger that works on a timer having the start of the fight trigger the skill usage and then be put onto a timer from ther

For this you'll want to start with the introduction to MUSHclient Scripting at https://mushclient.com/forum/?id=6030 if you're not already familiar with it.

You create timers with the script function AddTimer. ( https://mushclient.com/scripts/doc.php?function=AddTimer )

If you want the action to keep happening every N seconds, just don't set the OneShot flag.

If you want to call AddTimer with a keybinding, create an accelerator that sends to script with AcceleratorTo ( https://mushclient.com/scripts/doc.php?function=AcceleratorTo )

If you want to call AddTimer on a trigger, make the trigger send to Script.

I'll dive into that and start seeing if I can understand it. I've never coded anything in my life.

IS there a way to stop it as well? Like could a trigger stop a timer?

You could similarly call DeleteTimer as appropriate ( https://mushclient.com/scripts/doc.php?function=DeleteTimer )

I don't want to delete it. It needs to be used ongoing.
This is all just confusing me.

When you create the timer, if you don't set it as one-shot, then it keeps firing every N seconds (or whatever). Deleting it is the same as stopping it.

I don’t want to delete it. It needs to be used ongoing.

• Timers fire after a time has elapsed (eg. 30 seconds) or at a time of day (eg. 10:45 pm). This is the “AtTime” flag.
• Timers fire once or forever. If forever, then a periodical timer would fire after that interval continuously, eg. every 30 seconds. And a “AtTime” timer would fire at (say) 10:45 pm every day.
• Timers can be made “OneShot” (another flag used when creating them) which means they delete themselves when they fire. In this case, of course, they only fire once.
• Timers can be made “Temporary” (another flag) in which case they are not saved to the world file, and are lost when you close MUSHclient.
• Timers can be enabled and disabled (see the EnableTimer function). Disabled timers do not fire, but are not deleted.
• Timers can be reset (see the ResetTimer function). This makes them start the timing interval again. So, if you reset a 30-second timer, it will count for another 30 seconds.
• Timers can be deleted, before or after they fire (see the DeleteTimer function).

Script functions are documented here.

You don’t necessarily have to have dozens of timers. You could have one “heartbeat” timer that fires every second or so, and in that timer (script) consult a table of things (timed skills in your case) and see if the time has elapsed. If the time has elapsed display a message and remove the particular skill from the table, otherwise leave it there for the next heartbeat check.

This is what my triggers currently look like:

http://prntscr.com/qimfzx

It's essentially all based on messages that are returned from the MUD I'm playing on.

I have a skill called "Slash" which can be used every 4 seconds, however there is nothing returned from the MUD when it is available to be used again.

What I'm trying to accomplish is starting a time that will input "slash" every 4 seconds once combat is started, and stop once combat is ended.

I've never scripted or done anything like this before, so it's really really confusing to me what I'm looking at in the documentation.

I don't even know where I would input this? In triggers? In timers? Or if it's even possible.

Thank you ahead of time!

That's why I said to first read the introduction to MUSHclient Scripting at https://mushclient.com/forum/?id=6030

After you've read that fully, search for "script directly in a trigger" and follow that using your triggers that detect the start and end of combat.

I don’t even know where I would input this? In triggers? In timers? Or if it’s even possible.

Virtually anything is possible.

Stop worrying, initially, about how to script. First make a plan. Imagine you are explaining your plan to a friend, in detail.

• When combat starts ¹
• Do a “slash” ²
• Keep doing a slash every 4 seconds ³
• When combat ends ⁴
• Stop sending “slash” ⁵

Now turn that into scripting:

1. How do you know combat starts? A certain message arrives from the MUD, presumably. So you probably need a trigger.
2. Use the Send function to send a command to the MUD.
3. Add a timer to send “slash” with an interval of 4 seconds. See AddTimer.
4. How do you know combat ends? A certain message arrives from the MUD, presumably. So you probably need a trigger.
5. In the trigger, delete the timer which is sending “slash”. See DeleteTimer

Script functions are documented here.

This actually helps a lot.

There's 2 ways combat start: Either by initiating it with a command or assissing.

Is there a way to write it so that it either starts because of a command input or a trigger?

I'm reaiding through the functions document and don't see anything that discusses that.

If you initialize by command input then you want an alias which can:

• Send the command you want.
• Do other stuff like starting a timer.