Haste Breakpoint, Right or Wrong?

[Riencel]

Haste for 2 ticks on Corruption:
(((9 + 2 - 0,5) / 9) - 1) * 100 = 16,66666667%

Haste - 5% (Raid Buff):
1,1666666667 / 1.05 = 1,1111111111428571428571428571429 (11,11111111428571428571428571429%)

Haste Rating:
11,11111111428571428571428571429 * 425,19 = 4724,333334683142857142857142859 (4725 Haste Rating)

http://www.wowpedia.org/Casting_speed
http://www.wowpedia.org/Haste

I missed some calculation, the formulas have changed/are wrong or is there another reason?

[Cyner]

Haste breakpoints are still 4198 and 4717

No clue where you got your numbers from.

[Riencel]

Haste breakpoints are still 4198 and 4717

No clue where you got your numbers from.

http://www.wowpedia.org/Casting_speed
http://www.wowpedia.org/Haste

[Rustjive]

You forgot to round. The haste required is 16.652092%. It's too much for me to translate right now but here's the formula from Keldion's spreadsheet - https://docs.google.com/spreadsheet/...ZmFYa0E#gid=12 -

=IF(MOD($B82, ROUND(D87, 1)) / D87 = 0.5; IF(ISEVEN($B82 / D87); FLOOR(D87 - 1, 1) + 0.4999; FLOOR(D87, 1) + 0.4999); FLOOR(D87, 1) + 0.4999)

where B82 = base duration of 18s
and D87 = tickspeed required which is base duration / (11 -.5)

[Hellfury]

This awesome spreadsheet already has all the haste calculations need for all 3 lock specs and some other classes

https://docs.google.com/spreadsheet/...xZmFYa0E#gid=7

Sorry forgot the author's name

[Woz]

Corruption : (5%)
231 (N/A) : 1 tick of corruption
4717 (4249) : 2 tick of corruption
9211 (8699) : 3 tick of corruption

Agony : (5%)
3043 (2592) : 2 tick of agony
6400 (5915) : 3 tick of agony
9778 (9261) : 4 tick of agony

Unstable Affliction : (5%)
872 (N/A) : 1 tick of UA
6637 (6151) : 2 tick UA
12439 (11895) : 3 tick UA

*() are #'s for goblin

[Deleted]

I found with my current gear, 4717 haste was a DPS loss compared to me having 5200 Haste, which infact gained me 3k DPS, not sure why because im confused as 5200 isnt specifically on the spreadsheet, hmmmm...

[Shauni]

That's because haste breakpoint are overrated. Not that they are bad, but people tends to see them as a "Cap that should be respected at any cost".

Actually, Mastery and Haste are quite equals, sometimes mastery > haste, sometimes not. Recently a new trends appeared, saying that the optimal way to reforge is
"Haste > 4717 then keep Haste = Mastery - 500 points."

Use wowreforge to find a plot that match this rule, sim it and see if it's true.

[Deleted]

I found with my current gear, 4717 haste was a DPS loss compared to me having 5200 Haste, which infact gained me 3k DPS, not sure why because im confused as 5200 isnt specifically on the spreadsheet, hmmmm...

did you remember to add the upgrades to your items on your list of items in simcraft? as you need to add a ",upgrade=1" or a ",upgrade=2" without the " ofc as the upgrades arent included when you import your char, might give you a different result.

[Deleted]

did you remember to add the upgrades to your items on your list of items in simcraft? as you need to add a ",upgrade=1" or a ",upgrade=2" without the " ofc as the upgrades arent included when you import your char, might give you a different result.

Yeah made sure i added all my upgrades that i have... I've always found that 4717 haste was the threshold to go by then full mastery, but according to sims 5200 is best for me, i read something few months ago about people saying they're confused about why some players are going 5200-5300 haste then mastery, as that spreadsheet didnt show anything about 5200 haste... So im yeah, very confused atm lol and simming takes hours, which is annoying!!

[Deleted]

Haste for 2 ticks on Corruption:
(((9 + 2 - 0,5) / 9) - 1) * 100 = 16,66666667%

Haste - 5% (Raid Buff):
1,1666666667 / 1.05 = 1,1111111111428571428571428571429 (11,11111111428571428571428571429%)

Haste Rating:
11,11111111428571428571428571429 * 425,19 = 4724,333334683142857142857142859 (4725 Haste Rating)


I missed some calculation, the formulas have changed/are wrong or is there another reason?

You're right in theory, but you didn't round properly.

1:
(baseDuration / (desiredTicks - .5))
(18 / (11 - .5)) = 1.7142857142857142857142857142857

2:
round down (floor()) at 3 decimal places = 1.714

3:
Add 0.00049999 = 1.71449999

4:
baseInterval / newInterval = hastePercent

( 2 / 1.71449999) = 1.1665208583640761642699105527554

5:
Apply % based increases (5% spell haste for example)

1.1665208583640761642699105527554 / 1.05 = 1.1109722460610249183522957645289

6:
Convert haste percent to haste rating

ceil((hastePercent-1)*42500);

(0.1109722460610249183522957645289 * 42500) = 4,716.3204575935590299725699924798

rounded up (ceil()) = 4,717