Discussion in 'Priest' started by Pasterke, Dec 6, 2014.
Works perfectly, many thanks!!!
now for solace :B ?
hehe many thanks +1 for your rotation
will look for solace, but that will be tomorrow now
Thank you so much! Works very good now!
Can I ask you about few things:
1) The same problem is or were for tuanha pally routine - at the UBRS trash (before the first boss) casting this spell Incendiary Shell - Spell - World of Warcraft in normal mode it is the magic debuff, in heroic or cm it is simple debuff which can't be dispelled. Bot try to dispel it like a crazy, spends all gcd on it, moreover from the watcher's side it looks very weird =)
2) Is it possible to do Divine Insight - Spell - World of Warcraft instantly spending on the tank or onto the player within lowest health?
Thank you very much, I'm really appreciate your work!
Divine insight supported.
I added hotkeys to enable/disable Dispel/Purify on demand.
Really looking forward to testing your holy cr when I get a bit of gear :-D
I started testing your combat routine for the shadow priest and it works better then the Singular one since yours actually uses the insanity spell if you cast devouring plague.
Has anyone compared dps output to for example the Insanity routine of millz?
I am gonna test dps output a bit more with your routine and compare it with the insanity one, which gave me around 14k dps with ilevel 642 in dungeons and raids.
Will you do Holy and disc pve specc also?
Rl miss that 4 dungons and raids, been levling a druid now, since there is no good free healing pve for priest.
Ah there is holy in ur routine awsome.
Thank u so much will test it out pronto.
I see no tab on the cc for shadow priest, and i have to lates version of SVN.
Disc for 95% ready, works very good. Testing it out for the moment in dungeons and LFR. Not all talents supported for now, I wrote it with a fresh started priest. Is now lvl 76. Best way to add spells when you get new ones.
But disc in dungeons and LFR with my lvl 100 priest works fine.
But i'm not a pvp'er, will need assistence to add pvp features
Wonderful routine for shadowpriest ... I only have one question/issue. I think I have everything for movement turned off properly cause I always control everything but most of the rotations done, but while playing my spriest it won't let me move backwards out of stuff. I can strafe and all, but moving backwards just refuses to. I'll press the key to move but it stops me immediately. Just wondering if I missed something in the settings or just a random issue? Cause other than that it all works lovely.
Thanks for the routine Pasterke its great
What key you use to move backwards ?
I use the AWSD keys for movement. AWD work normal just S for backing up is the one that doesn't let me.
Normaly he should let you move back. Movement, targeting and facing is default on. Movement, targeting and facing when you are in group are default disabled.
Maybe you have a keybinding on the "S" ? Other reason can be a plugin.
Ok I'll check through my keybindings and all. Thanks for the insight
Ok no keybinds interferring, and I dont have anything other than the plugin(s) that come with HB. I'll just mainly strafe and stuff til I can find the issue.
He should not longer stop moving if you try to move backwards. Found the reason
awsome work..this going to stay free or this just testing before it goes on the buddy store? I dont want to grow attached if i am going to lose it lol .
It will stay free
Today I updated to the latest SVN 117 and tried to do shadow dps in a raid, but my computer completely went down to 5 fps, while with singular as combat routine it is 15 fps or more. But with your routine my priest stands there and starts the routine but then stops dead.. doing nothing. It will do a Shadow word: pain if it has run out, but then nothing more.
Keep up the good job updating the SVN. Thank you very much for share it.
I keep getting this:
Compiler Error: c:\Users\Troy\Desktop\HonorBuddy\Honorbuddy\Routines\Singular\Helpers\Item.cs(456,50) : error CS0234: The type or namespace name 'Priest' does not exist in the namespace 'Singular.ClassSpecific' (are you missing an assembly reference?)
Separate names with a comma.