I think that at the moment the only way to understand condtions, is looking through PE code... If you are friendly with this type of language
I think that at the moment the only way to understand condtions, is looking through PE code... If you are friendly with this type of language
doesrequire firehack? or is that only needed for something like:Code:"modifier.enemies > 1"the reason I ask is because I dont want to use FH, and I think ill be ok if my profile isnt as smart (i can always use a toggle)Code:"area(10).enemies > 3"
Although I found lines for "player.enemies(10) > 3" and "modifier.enemies > 3" in two of the default CRs in PE (Frost DK and Guardian Druid respectively), neither appear to be registered as valid conditions that I could find. The only two enemy related conditions that I found registered are:
- unit.enemy which checks if the unit is attackable by the player.
- unit.area(distance).enemies which returns the number of units within the distance around the unit and requires FireHack to work.
End result, "modifier.enemies > 1" will not work from what I'm finding unfortunately. If any of this is incorrect, I'll let devs chime in! =)
Hmm, looks like there was also the makings of combat tracker for units in affecting combat, but I'm only seeing it called from a commented out healing tracker frame.
Last edited by Greymalkin; 12-31-2014 at 02:42 PM. Reason: hostile != attackable. oops.
how does the combat and time work?
Basically I want to have a sperate rotation for opener. then
Something along those lines. I want to perform more specific actions for the opener than the rest of the rotationCode:{{ -----------------insert opener rotation------------------ --------------- }, player.combat.time <= 6 },
As for what I could find on combat time, there are two related conditions registered that may be applicable to what you are working on.
- unit.combat checks if the unit is affecting combat. No time relation, just is or is not in combat.
- unit.time returns the difference between the current time and the time when the player entered combat. Since unit is not actually passed as an argument, only "player" should realistically be used for the unit value for CR readability purposes as far as I see.
About the idea of an opener, I noticed someone put a nested block of opener entries at the bottom of his/her OOC section, but I don't remember the specifics on what conditional or structure off the top of my head. (It might have been "tank.combat" now that I think about it.) I believe it was one of the Retribution Paladin CRs running around if you want to go check it out for ideas or inspirations. =)
Last edited by Greymalkin; 12-31-2014 at 06:21 PM.
thanks for the help!!
I actually found a work around using conditions. here is how I start (OOC):
Code:{"#109218",{"modifier.lcontrol", "!modifier.last"},"player"}, {"Mirror Image",{"modifier.lcontrol","!modifier.last","talent(6,1)"}}, {"Pyroblast",{"modifier.lcontrol"},"target"},
Then once Combat is entered, the In combat starts, and I obviously let go of Left Control. The routine does its standard of building up both pyros and heating up, then this is what I have (top priority)
So as per this guide on icy veins:Code:--Meteor combustion setup {"!Meteor",{"target.enemy","player.buff(Heating Up)","player.buff(Pyroblast!)","modifier.cooldowns"},"target.ground"}, {"!Fireball",{"modifier.last(Meteor)", "!player.moving", "!modifier.last"},"target"}, {"!Pyroblast",{"modifier.last(Fireball)", "player.buff(Pyroblast!)","player.spell(Meteor).cooldown > 40"},"target"}, {"!Pyroblast",{"modifier.last(Meteor)", "player.moving", "player.buff(Pyroblast!)","player.spell(Meteor).cooldown > 40"},"target"},
So my code for combustion is:We advise you to use the following opening sequence (or opener).
Use your Draenic Intellect Potion and start casting Pyroblast (-2.5 seconds).
Apply Living Bomb, if you chose it as your Tier 5 talent.
If you have Meteor as your Tier 7 talent:
fish for a Pyroblast! proc by casting Fireball;
when you get the proc, cast Fireball again, then Meteor and Pyroblast;
cast a second Pyroblast if you get another proc.
Cast Combustion.
Continue with your single-target rotation.
I was toying with the ! and not having the ! in front of the Spell (normally its supposed to cast regardless of current cast), but switching to offspring the ! infront of the spell doesnt seem to be workingCode:{"!Combustion",{"target.debuff(155158)","target.debuff(Ignite)","talent(7,3)", "player.spell(Pyroblast).casted >= 1"},"target"},
Doing more testing.
I think I had too many !. testing
YES.. working a whole lot better.. Had to remove some !. Got carried away thinking everything was uber important.
Last edited by Mackdaddy2887; 12-31-2014 at 07:15 PM.
Is there a way to test item cooldown? Something like GetActionCooldown(slot) with slot 14?
I want to do {"/use 14" , "getactioncooldown(14) = 0"} but it doesn't work.
There is interest^^
My rotation use my trinket with king of jungle, berzerk and tiger fury when i have BL buff.
{{{"/use14"} ,
{"Incarnation: King of the Jungle"},
{"Berzerk", "player.buff(King of the Jungle)"},
{"Tiger's Fury", {"player.buff(Berzerk)", "player.energy < 110"}},
}, {"player.buff(Bloodlust)", "modifier.cooldowns"}}
But like that, once BL cast, it use the trinket and always says "i can't do that now" cause it want to use the trinket which is on CD so the rotation need the condition "trinket cd =0" to work fine.
I'm using PE mainly for Focus control, and it inevitably comes with the problem with it clipping itself when trying to shoot at focus target who is is behind you (playing hunter).
Is there a condition for it to only shoot if target is in front, or not behind? I'm thinking that is probably too hard to check.
This says the spell is on cooldownCode:"player.spell(Spell Name).cooldown"
this says the spell cooldown is greaterthan/euqal to 5Code:"player.spell(Spell Name).cooldown >= 5"
Not on Cooldown,Code:"!player.spell(Spell Name).cooldown"
etc etc
Ah crap, totally screwed up what i wanted to ask because that i know.
What i want is to compare the cooldown of a spell to the duration of a buff.
So cast spell x if buff y has a duration longer then 2x the cooldown of spell x
And i also would like a way to refer to the gcd.
So cast spell x if cooldown spell y has a duration longer then 2x gcd.
That is essential becuase gcd and spell cooldowns are effected by haste ao just putting a static 4.5 or 1.5 doesnt work.