Script format help please

My trigger is based on my prompt line:
trigger: <(H|T|HT)>
Regular expression

Runs this subroutine:

sub DiscardQueue (name, line, wilds)
world.DiscardQueue
IF world.getvariable ("Sleeping") = "yes" then
world.send "rest"
end if
if world.getvariable ("Sleeping") = "no" then
end if
dim count
for count = 1 to 3
world.send "emote drinks soup"
next
world.send world.getvariable ("Sleeper")
end sub

(note: I do have the variable for when I sleep, and when I wakeup change the variable "Sleeping" when appropriate)

This doesn't quite work the way I thought it should work.

I was figuring it to do the if statements, then the dim then the last world.send. But it doesn't for some reason it does the dim first, then everything afterwards.

basically i want it to check to see if I am sleeping, if yes, then rest, drink soup 3 times, then sleep again.
if no then drink soup and sleep pillow.

Of course discarding the queue first regardless of what its supposed to be.

basically trigger looped myself because of my prompt.
I needed to test if it worked while I was sleeping. It didn't. So I changed world.send "drink soup" to world.send "emote drinks soup"
I had a world.note in there as well but for the reasoning I posted it up on the forum it wasn't needed. It was for testing pourposes.

I don't know what you mean by "it does the dim first". Dim just declares a variable, and AFIK the dim statements should come at the start. It doesn't really "do" a DIM.

I don't see what this line does:

if world.getvariable ("Sleeping") = "no" then
end if

Why bother doing an IF if you don't do anything inside it?

Is this a typo? ...

world.send world.getvariable ("Sleeper")


The variable you were using before was "Sleeping" not "Sleeper".

Ok. I see how you would be confused. I was originally going to do something else with the "no" statement but I changed my mind.

I dropped that.

What I mean is simply this. Originally I wanted it to set my speedwalk at whatever when the script is called. I.E. 6000ms or something.
Then once the counting script is completed, it set the speedwalk back to 0ms

Now, being a linear type of guy i figured. it would go through the script and no big deal, it sets the speed walk at 6000ms, does the counting part, then changes Speedwalk back to 0ms at the end, this way, I don't have to worry about changing the speedwalk delay whenever I want to use it.

This being the Logical assumption on how it works.

In reality, it does not work this way, at least when I tried it.

I set it up like this:

sub SpamCast(name, output, wilds)
world.setvariable "Sleeping", "no"
world.SpeedWalkDelay = 7000
world.colournote "yellow", "black", "My speedwalk delay has returned to: " & world.SpeedWalkDelay
dim count
for count = 1 to world.getvariable ("SpellCount")
world.queue "c " & world.getvariable("SpellName"), 0
next
world.send world.getvariable ("Sleeper")
world.send "inventory"
world.speedwalkdelay = 0
world.note "Speedwalk 0ms"
end sub

What happens is it sets the variable fine, it sets the speedwalk delay fine, world.notes me fine, then sets the speedwalk again at 0, and notes me again, THEN goes through the whole counting part of the script.

The speedwalk delay is a global thing, it doesn't remember the delay per queued command.

What you are doing is queuing a whole heap of things, and then, before it has a chance to do the queued things (which it will when the script exits) you have set the speedwalk delay back to zero, so they all get sent at once.

I think I know what you are trying to accomplish. I do the same thing often, though without using delays between commands, and here's what I use to do some tasks after the commands are executed...

You have a series of commands you want to send: command1, command2, command3. And you have a series of actions you want to perform after all the commands are done with: action1, action2, action3. This seems like a straightforward enough task - just have an alias call the script, have the script send the commands and then the actions. However, this won't work, since the actions will be performed before the commands have any chance of even leaving your computer. Thus, I do it in a different way - I add a fourth command (command4) into the series of them, that one is usually an emote. Then I add a trigger to match on that emote and call a script which will do: action1, action2, action3. Commands and actions are contained in different script routines, connected through a trigger by the last command in the series.

In your case, it could look like this (ignoring MUD-specific syntax):

Ok, I have another idea on how to do this.
What is in the queued command part I put in an if statement that is run everytime.

sub SpamCast(name, output, wilds)
world.setvariable "Sleeping", "no"
world.SpeedWalkDelay = 7000
world.colournote "yellow", "black", "My speedwalk delay has returned to: " & world.SpeedWalkDelay
dim count
for count = 1 to world.getvariable ("SpellCount")
world.queue "c " & world.getvariable("SpellName"), 0
if <myvariable> = <number> then
<set the speedwalkdelay to 0ms>
else
<set myvariable at what it is +1>
next
world.send world.getvariable ("Sleeper")
world.send "inventory"
end sub

Umm. No... That just does the same thing as before, but in a different way. The thing you have to remember is that scripts are in the same 'thread' as your input. What I mean is that any commands it sends 'must' be delayed until the script itself ends. Example:

1. You type "cast light 5". i.e. cast light five times, not sure what syntax you are using here.
2. The script is called and does 'everything' you are telling it to, then exits.
3. The commands the 'script' sent are processed.

You are expecting it to do this:

1. You type "cast light 5".
2. Script sets speedwalk.
3. Script sends command.
4. Client executes command.
5. Script sends next command.
...
13. Script sets speedwalk back to normal and exits.

This 'would' work if the script ran seperate from the program, but it doesn't. Instead, everything the client normally does is suspended 'until' the script exits. You commands will never happen before the speedwalk delay is changed, since they never get sent until after the script has finished. You would need to do something more like this:

1. You type "cast light 5".
2. Script sets mushclient variables Spell = "light", Count = "1" and SpellEnd = "5", then enables a timer.
3. Timer calls a script which sends the cast command, then increases Count by one. If it is now greater than SpellEnd it disables the timer.
4. Timer calls a script ...

In other words, instead of using for-next, you build one. In this case, you can also set the delay with the timer length, instead of the speedwalk, but imho since the timer can't be set more accurate than 1 second intervals, it is a bit annoying. However, since your delay doesn't have to have millisecond precision, in this case it will work fine.

After thinking about it for a few minutes I think I understand why it doesn't and won't ever work.

The script is instantaneous. As soon as it it called it does all the meat within the subroutine right away. it doesn't wait for the queued commands to go through. The only way I could change that is too... Nevermind, I got it. Problem solved. Thanks a bunch

Queued commands won't, you are right. "Immediate" commands (like world.note, world.send) are done during the script execution.