Join my journey/Tumble Speed Reps

[Stunseed]

I'm learning scripting. I also have a Rogue just starting in the guild. Guildx does not work with tumble speed or audience reps. I am posting my simple, yet efficient script for AFK scripting the speed reps.

What I'm not positive how to do at this point, is make it auto-stop when completed, or perhaps move to ask DeLuca for further instructions. At this point, it does its job for the first 10 ranks of Gambits.

#F'in tumble script

goto REPS

REPS:
put rgam tumble back
pause 1
put rgam tumble back
pause 1
put rgam tumble back
pause 1
put rgam tumble back
pause 1
goto REPS

Until you learn tumble < direction >, simply remove the direction for it to work.

Edited so the title makes sense.

[Edited on 7-4-2005 by Stunseed]

[Bobmuhthol]

Wouldn't it be easier to just do

REPS:
put rgam tumble back
pause 1
goto REPS

?

And if you want it to stop after your reps are done, input them with %1, set counter to %1, and subtract when you get the success message.

counter set %1
goto %c

LabelError:
put rgam tumble back
match YES Success message.
match NO Failure message.
matchwait

YES:
counter subtract
pause 1
goto %c

NO:
pause 1
goto %c

0:
exit

[Jorddyn]

Originally posted by Bobmuhthol
And if you want it to stop after your reps are done, input them with %1, set counter to %1, and subtract when you get the success message.



Or just do a match on the "You have completed this task" phrase.

Jorddyn

[Bobmuhthol]

...

Well hot damn, I forgot that you can use a match without a matchwait.

[Jorddyn]

Originally posted by Bobmuhthol
...

Well hot damn, I forgot that you can use a match without a matchwait.

Match TumbleAgain (repetitions remaining message)
Match TumbleAgain (tumble success message)
Match TumbleAgain (tumble failure message)
Match Done (all done message)
matchwait

Jorddyn

[Bobmuhthol]

1. That wouldn't work.
2. I wasn't being sarcastic.

[Jorddyn]

Originally posted by Bobmuhthol
1. That wouldn't work.
2. I wasn't being sarcastic.

1. Really? Could you tell me why (seriously curious)?
2. Damn, I was right the first time. Should have kept my mouth shut for once :)

Jorddyn

[Bobmuhthol]

It wouldn't work because you're matching it in the wrong order. The way the messaging would show up is:

<success/failure message>

<reps left/no reps left message>

If you match them in the order you did (reps left, success, failure, no reps left), when there are no reps left it will look for reps left unsuccessfully, but it will always match a success or failure because you put those in before the no reps message. You could do it the way you did if you did

Match TumbleAgain (repetitions remaining message)
Match Done (all done message)
matchwait

or

Match Done (all done message)
Match TumbleAgain (tumble success message)
Match TumbleAgain (tumble failure message)
matchwait

but you only need a

Match Done (all done message)
goto REPS

because either you get the done message and end or loop.

[Jorddyn]

Originally posted by Bobmuhthol
Match Done (all done message)
Match TumbleAgain (tumble success message)
Match TumbleAgain (tumble failure message)
matchwait


Damn :( SO close. Thanks :)

Jorddyn

[Bobmuhthol]

Actually, I think I lied. I overlooked the line rule. In a match, it goes line by line. The success or failure message will always be first, so it sees if there's a match in the match table, starting with the first entry in the table. That would work only if the done message was on the first line.

Match TumbleAgain (repetitions remaining message)
Match Done (all done message)
matchwait

That would still work because it's matching the same line.

Match Done (all done message)
goto REPS

That would still work because it acts like an IF statement (IF done THEN exit).

[Edited on 7-5-2005 by Bobmuhthol]