What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Frost] Synapse made by Weischbier

  • Thread starter Thread starter weischbier
  • Start date Start date
Status
Not open for further replies.
It seems that it doesn't cast Soul Reaper on bosses. Anyone having this issue?
 
I'm the last in Recount with this CC.. i don't understand.
There is something special to configure ?
Anyone have good dps ?
 
demonbuddymeh said:
apparently there's also a version .516 now that's working? should we use .516 or the latest beta build?
Click to expand...

I'm gonna look into it :)

.. It would seem that the latest HB .516 or .517 broke auras, it doesn't even detect KM procs at all now.. I will try and look into a temp fix for this issue, until now it's broken.. :D
 
Last edited:
alxaw said:
I'm gonna look into it :)

.. It would seem that the latest HB .516 or .517 broke auras, it doesn't even detect KM procs at all now.. I will try and look into a temp fix for this issue, until now it's broken.. :D
Click to expand...

so we should continue with the beta build?
 
demonbuddymeh said:
so we should continue with the beta build?
Click to expand...

It still would be the same, it finds the aura sometimes (51128) which is the wrong aura ID as well.. The aura ID should be 51124 which is the right proc for it. I hope HB team fixes this error quickly, as I know there is a lot of classes that depends on aura procs not just DK.
 
i don#t get this line:

Spell.Cast("Howling Blast", ret => Me.HasAura(59052) && Spell.GetSpellCooldownLUA("Obliterate") >= 1),

refering to elitistjerks using your rime proccs has a higher priority then OB, unless you have a killing machine procc.
 
does anyone knows if you go at tab advanced there is a thing called
awesome pvp what it does
cause mine is blank when i open it
 
Drizzt1990 said:
i don#t get this line:

Spell.Cast("Howling Blast", ret => Me.HasAura(59052) && Spell.GetSpellCooldownLUA("Obliterate") >= 1),

refering to elitistjerks using your rime proccs has a higher priority then OB, unless you have a killing machine procc.
Click to expand...

If you read advanced theory topic, you can see that you have time to wait if you have OB < 1 second (no dps loss) you can use HW on RIME proc instantly if OB is over > 1 second :)
 
Rime procs:
Rime procs are generated using obliterate, and give you a free howling blast. You can hold onto a rime proc as long as you want, assuming you don't wait the entire duration, or use obliterate during it, which has a chance of overwriting the proc. In practice, you rarely, if ever, go the full duration without having a free GCD to use it, so just don't obliterate with rime up.
To spend rime, use howling blast.

Advanced Frost Priority Tactics - Elitist Jerks

alxaw said:
If you read advanced theory topic, you can see that you have time to wait if you have OB < 1 second (no dps loss) you can use HW on RIME proc instantly if OB is over > 1 second :)
Click to expand...

I read the complete topic, but couldn't find it...
 
Last edited:
Drizzt1990 said:
Rime procs:
Rime procs are generated using obliterate, and give you a free howling blast. You can hold onto a rime proc as long as you want, assuming you don't wait the entire duration, or use obliterate during it, which has a chance of overwriting the proc. In practice, you rarely, if ever, go the full duration without having a free GCD to use it, so just don't obliterate with rime up.
To spend rime, use howling blast.

Advanced Frost Priority Tactics - Elitist Jerks



I read the complete topic, but couldn't find it...
Click to expand...

It seems your reading skills are low ->

Case new:
70 runic, 1F 1D fully depleted, 1U is up the other FU pair has 3 seconds remaining on regen, and the other D has 4 seconds remaining, KM up. You wait 3 seconds, instead of using FS. 1 obliterate with KM. Rime procs, and you suggest using rime, however, I'd say hold off on the rime proc until before you need to obliterate again. Since KM in not up the second after the first obliterate, you can safely tap FS for a non-crit. We're assuming KM procs at this point, so now you use rime, and then obliterate. You hold off on a GCD where you could be using obliterate, because you used FS before the obliterate to use up the proc, but you don't overcap runic. You start at 70, jump up to 94, down to 74, and up to 98. At this point, you are dangerously close to capping runic, so you want to tap out as many FSs as possible, waiting for that next proc. 90% of the time, you can get off 2-4 FS or more before that happens.
Click to expand...
 
"I'd say hold off on the rime proc until before you need to obliterate again."

Wouldn't that mean: Spell.Cast("Howling Blast", ret => Me.HasAura(59052) && Spell.GetSpellCooldownLUA("Obliterate") <= 1),

instead of: Spell.Cast("Howling Blast", ret => Me.HasAura(59052) && Spell.GetSpellCooldownLUA("Obliterate") >= 1),

because u want to use it right before the next obliterate to not waste your procc?


Maybe i missunderstood, englich is not my native language, so feel free to correct me if I'm wrong
 
Drizzt1990 said:
"I'd say hold off on the rime proc until before you need to obliterate again."

Wouldn't that mean: Spell.Cast("Howling Blast", ret => Me.HasAura(59052) && Spell.GetSpellCooldownLUA("Obliterate") <= 1),

instead of: Spell.Cast("Howling Blast", ret => Me.HasAura(59052) && Spell.GetSpellCooldownLUA("Obliterate") >= 1),

because u want to use it right before the next obliterate to not waste your procc?


Maybe i missunderstood, englich is not my native language, so feel free to correct me if I'm wrong
Click to expand...

Hi,

No, the tumb rule is to wait 1 GCD (1 second) max to OB again. So >= 1 is correct, because it tells the "rotation" to use HW if we have the rime proc and OB is over 1 second cooldown, then we can use HW.
 
alxaw said:
Hi,

No, the tumb rule is to wait 1 GCD (1 second) max to OB again. So >= 1 is correct, because it tells the "rotation" to use HW if we have the rime proc and OB is over 1 second cooldown, then we can use HW.
Click to expand...

Sorry to say that, but your wrong about that. You should ALWAYS spend the rime procc right before the next OB.

"For this reason, it's normally optimal to wait on a rime proc until you've used up as many of the staggered frost strikes as possible, and then to obliterate soon after. If killing machine procs during the frost strike taping, with rime up, you want to hit the rime proc, and then obliterate. "

maybe something like: Spell.Cast("Howling Blast", ret => Me.HasAura(59052) && Spell.GetSpellCooldownLUA("Obliterate") <= 2)

to make sure you use it in the gcd right before OB...

The way its coded now, it wastes rime proccs if u got the runes for 2 OB in a row, like when you've used ER->OB(creating a rime procc) and now u have 2D 1F 1U up, so cooldown for OB is not >1 and it wont use rime.



If you are german alxaw, maybe we can talk about this in TS or skype... its way easier to talk about that stuff in your native language then posting on english :-P
 
Last edited:
cameronmc88 said:
Does either of you guys PvP/Arena as Frost?
Click to expand...

Jesus Christ. I don't even own this thread and it's irritating to see the same question asked over and over. I have sympathy for Weisch. Take 5 minutes and look through this thread. They DO NOT SUPPORT PVP AT THIS TIME. I assure you that *IF* they do they will tell us on the first post
 
Well I have not tried this yet but your Donation suggestion is just a great idea I plan on releasing my profiles with the same....Thanks for the Idea....Trying this now
 
Ok guys...please update to v0.0.7 which is a Fix to all issues atm.
But with the latest .518 retail version it can crash your WoW.
This is not the CR's fault, it's due to lags in memory reading processes.

greetz

Weischbier
 
Status
Not open for further replies.
Back
Top