New User To Macroquest

Help section from before the user variable changes that broke all macros

Moderator: MacroQuest Developers

FUBAR
decaying skeleton
decaying skeleton
Posts: 1
Joined: Wed Dec 11, 2002 3:10 pm

New User To Macroquest

Post by FUBAR » Wed Dec 11, 2002 3:17 pm

I am having problems running my first macro from this site, it is a brewing macro witch i have pasted below. I have the macro pasted in the right folder, when i try to run it i type /macro brewing obviously this isnt enough to make it work, if u could please tell me the correct wording to type and how it is possible to vary speeds on your macros, and i am also using the new interface if that makes any diff at all. Tx for ur time and patience with me.



| - Brewing.mac -

#include routines.mac
#turbo

Sub Main
| Initialisation
/press ctrl
/press shift
/press alt


| Main Loop
/itemtarget Brew Barrel
/face item
/click left item
/varset v98 $char(skill,Brewing)
/if n $v98<45 /goto :Makeheady
/if n $v98<61 /goto :Makefishwine
/if n $v98<151 /goto :Makeskull
/goto :Done

:Makeheady
/sendkey down ctrl

/finditem "Packet of Kiola Sap"
/if $find()==FALSE /goto :Done
/click left enviro 0

/finditem "Packet of Kiola Sap"
/if $find()==FALSE /goto :Done
/click left enviro 1

/finditem "Water Flask"
/if $find()==FALSE /goto :Done
/click left enviro 2

/finditem "Bottle"
/if $find()==FALSE /goto :Done
/click left enviro 3

/sendkey up ctrl
/click left enviro combine

/if "$cursor()"=="TRUE" /goto :AutoDrop
/for v1 1 to 5
/delay 2
/if "$cursor()"=="TRUE" /goto :AutoDrop
/next v1

/goto :Makeheady

:AutoDrop
/click left auto
/doevents
/goto :Makeheady

:Done
/sendkey up ctrl

/click left enviro done

/return

:Makefishwine
/sendkey down ctrl

/finditem "Grapes"
/if $find()==FALSE /goto :Done
/click left enviro 0

/finditem "Fresh Fish"
/if $find()==FALSE /goto :Done
/click left enviro 1

/finditem "Water Flask"
/if $find()==FALSE /goto :Done
/click left enviro 2

/finditem "Bottle"
/if $find()==FALSE /goto :Done
/click left enviro 3

/sendkey up ctrl
/click left enviro combine

/if "$cursor()"=="TRUE" /goto :AutoDropwine
/for v1 1 to 5
/delay 2
/if "$cursor()"=="TRUE" /goto :AutoDropwine
/next v1

/goto :Makefishwine

:AutoDropwine
/click left auto
/doevents
/goto :Makefishwine

:Done
/sendkey up ctrl

/click left enviro done

/return

:Makeskull
/sendkey down ctrl

/finditem "Vinegar"
/if $find()==FALSE /goto :Done
/click left enviro 0

/finditem "Spices"
/if $find()==FALSE /goto :Done
/click left enviro 1

/finditem "Short Beer"
/if $find()==FALSE /goto :Done
/click left enviro 2

/finditem "Cyclops Skull"
/if $find()==FALSE /goto :Done
/click left enviro 3

/sendkey up ctrl
/click left enviro combine

/for v1 1 to 10
/delay 1
/if "$cursor()"=="TRUE" /goto :AutoDropAle
/next v1

/goto :Makeskull

:AutoDropAle
/if "$cursor(name)"=="Cyclops Skull" /goto :AutoDropSkull
/click left auto
/delay 1
/if "$cursor()"=="TRUE" /goto :AutoDropAle

:AutoDropSkull
/click left auto
/if "$cursor()"=="TRUE" /goto :AutoDropSkull
/doevents
/goto :Makeskull

:Done
/sendkey up ctrl

/click left enviro done

/return

Vendor001
Cheezily Banned
Cheezily Banned
Posts: 78
Joined: Wed Nov 13, 2002 1:37 pm

NG for NewUI

Post by Vendor001 » Wed Dec 11, 2002 4:48 pm

From what I understand, MQ doesn't support clicky with NewUI...so you'd have to go back to old-skool UI to run your tradeskill macro.

Also, to usually figure out where something is crashing(when you don't have a useful debugger), you can just put /echo statements in the code to figure out where it's going. For example:

Code: Select all

:Done 
/sendkey up ctrl 

/click left enviro done 
/echo Exiting Brewing.mac
/return
At least then you'd have a rough idea where it was going. Usually you'd try to put them around statements you think might be problematic or which you dont think are executing(inside IF statements, FOR loops, etc.)

ashplayah
decaying skeleton
decaying skeleton
Posts: 8
Joined: Tue Dec 10, 2002 5:55 pm

Post by ashplayah » Wed Dec 11, 2002 4:56 pm

You could also set DebugSpewToFile=1 in MacroQuest.ini file. This will provide you with endless amounts of debug text from the macro engine (in a file in your Logs directory).