Hm, its actually really difficult to have a priority system do a straight rotation.
I am thinking of adding macros to allow users to track their own "states" in case they want to do more rigid rotations rather than priority. This wasn't really an issue in WoW because everything is proc based over there - here it is kinda lame that almost every class (aside from ranged) is completely static. At least it meant spreadsheets gave fairly accurate models.
Anyway the syntax would look something like this:
Conditional:
(p1.macro.test == 1)
Action:
{macro.test, macro.test.inc, macro.test.10, macro.test.dec}
macro.<id> : initialize
macro.<id>.inc : increment by 1
macro.<id>.dec : decrement by 1
macro.<id>.<#> : set macro to #
All macros would be integers. They are initialized to 0. You can create and set as many macros as you like (I suggest you do this in precast).
so for example (in the future) this rotation would be something like:
[p1.PRECAST]
(){macro.state_var}
[p1.GCD]
# still want to use 4th combo when we can
(p1.aura.enhanced_wheeling_thrust){wheeling_thrust}
(p1.aura.sharper_fang_and_claw){fang_and_claw}
# if state is 0, do first half first line
(p1.macro.state_var == 0){heavy_thrust, impulse_drive, disembowel, chaos_thrust, macro.state_var.inc}
# if state is 1, do second half first line
(p1.macro.state_var == 1){phlebotomize, true_thrust, vorpal_thrust, full_thrust, macro.state_var.inc}
# etc. etc, to reset after last line, it would look like
(p1.macro.state_var == 5){phlebotomize, true_thrust, vorpal_thrust, full_thrust, macro.state_var.0}
