Re: Rogue Helper v6.0 [Complete Rogue Macro] (Updated: 10-26
Posted: Sun Nov 06, 2016 6:28 pm
http://www.macroquest2.com/wiki/index.php/TLO:Bool
I am not currently having an issue with comparison using RD, but through out the process of working on RD I sometimes get some wonky behavior.
Some things to note: It pays to end MQ and restart it now and again. Same for your machine, it pays to reboot now and again. Some things can go nuts after a bit.
I would put in a
into the macro you are working on, so you can add some debugging messages to help you narrow down issues. Can even make them more section specific like
or what ever you want to call them ( obviously heal or bard stuff wont be in this macro)
Then while your macro is running you can "/Varset Debug 1" to get the debugging working.
--------------------
Then of course you can add the lines of code to help you out. For instance
In other words you can add in helper messages to display information as the macro is running, that you would not normally see/want to see, or other things. You can put in "now entering this section" and "now leaving this section" type things, or "activating this" or "skipping that"
If nothing else, taking the time to follow through the macro and added some debugging lines here and there will help you understand the macro better.
I do not think Bool will accomplish what you are after.Description
Creates a bool object using text. Value is set to TRUE unless text is "NULL" "FALSE" or "0" (capitalization does not count).
I am not currently having an issue with comparison using RD, but through out the process of working on RD I sometimes get some wonky behavior.
Some things to note: It pays to end MQ and restart it now and again. Same for your machine, it pays to reboot now and again. Some things can go nuts after a bit.
I would put in a
Code: Select all
/declare Debug int outer 0Code: Select all
/declare HealDebug int outer 0
/declare BardDebug int outer 0
Then while your macro is running you can "/Varset Debug 1" to get the debugging working.
--------------------
Then of course you can add the lines of code to help you out. For instance
Code: Select all
/if (${Target.PctHPs}<${assistpct} && ${Target.Animation}!=32 && ${Target.Animation}!=110) {
/if (${Debug}) {
/echo Target ${Target.PctHPs} < ${Target.PctHPs}
/echo Target Animation is ${Target.Animation}
}
If nothing else, taking the time to follow through the macro and added some debugging lines here and there will help you understand the macro better.