Getting this Error and cant load load your Rotaion:
2x Probably_boxos_shaman\elemental.lua:48: '}' expected (to close '{' at line 46) near '"modifier.lalt"'
Getting this Error and cant load load your Rotaion:
2x Probably_boxos_shaman\elemental.lua:48: '}' expected (to close '{' at line 46) near '"modifier.lalt"'
must have missed something and uploaded between edits. Should be fixed now
thx it works now
As a quick update, I've done all the normal mode fights with my resto profile, and so far it has been good. Not great, however. I am currently looking for some help.
I started making these profiles as something that I could use for myself, but I'm not a programmer, and I've never done anything like it before. I'm trying to create some custom functions that could make healing easier in general, but don't know how to do it. I tried piecing together pieces of existing PE code, and modifying it, but so far it does not work.
If anyone wants to take a look at it, or wants to help me work through it, the profile is here:
https://drive.google.com/folderview?...mM&usp=sharing
Any help is appreciated.
Tried out your MM hunter one. I absolutely loved the auto trap if more more than 1 mob was there. Saved me from having to remember to do it all the time. A few small improvements could be made for an opener but not bad at all.
heads up about Resto shaman.
It casts cloudburst, then overwrites it with Healing stream
Yeah, I know. I haven't pushed an update in a while. Without a good way to cast riptide, it hasn't really been worth it, and I don't know how to get riptide to work.
Cant get your elemental aoe and cleave rotation to work I'm using latest Firehack unlocker too.
edit. Also how do i configure it so it doesn't include healing spells in it's rotation? or I could simply toggle them off.
Last edited by LtButterman; 01-02-2015 at 06:11 AM.
Is there a way to log the abilities its trying to use, on the Warrior one it seems to be hanging up for me, the mouse cursor is lighting up with the hand and it appears to be trying to do something but it doesnt happen.
Essentially, cast riptide on cooldown on relevant targets. at the moment, that's not really possible with PE. I've set up a workaround to cast on mouseover targets, but without the ability to target the lowest health unit without the buff, it's not really worth doing much else.
Well, it'll take a lot of code, but setting up something similar to my druids resto, but something more of cascading levels of importance. Like:
Anyways, the logic Is this,Code:{"Riptide", {"lowest.health < 90", "!lowest.buff"}, "lowest"}, {"Riptide", {"tank.health < 90", "!tank.buff"}, "tank"}, {"Riptide", {"focus.health < 90", "!lowest.buff"}, "focus"}, -- these three first to insure that whoever is "lowest" and "tank/focus" always have riptide priority. --Then a array of cascading priority for additional riptides at 30%, 60%, then lastly 90%: {"Riptide", {"raid1.health <=30", "!raid1.buff"}, "raid1"}, {"Riptide", {"raid2.health <=30", "!raid2.buff"}, "raid2"}, --repeat this line for raid members 3->20 --next repeat those lines using the next priority of 60% --lastly repeat the array again using the last priority of 90%
It'll ALWAYS riptide the lowest first if they don't have it. Next the tank/focus, then it'll riptide anyone/everyone who's below 30%, then 60%, then lastly 90%.
Excuse any errors I did this from my phone. But just using logic we can try to attempt a priority for riptides since we don't have any other functions at our disposal. Works relatively well, because it's how a player behaves anyways, we just look at the bars and guesstimate who the lowest is anyways, ya know? We don't know the exact lowest or second lowest, etc.
Also I just made up the numbers, feel free to change/use as you see fit.
Personally, I added exactly that to your rotation, and afew other tweaks for my personal use and it works great
Last edited by Mackdaddy2887; 01-02-2015 at 06:51 PM.
What appears to be hanging up for me is Vigilance, when it casts it, the cursor lights up I guess cause its a targeted ability, but in the PE AL log you see it counting up but not casting. This test this time was on a dummy which may be cause nobody to cast on but will test it again in a dungeon. In the pic the number before Vigilance counted up to over 800
https://dl.dropboxusercontent.com/u/59229956/war.png