Fury DPS is already horrible.

Please try and address this issue as soon as possible Blizzard.

Throw us a bone :(

I have been Fury for life (vanilla, I also have no alts), when TBC came and saw the giant nerfs on the PTR I quit until they fixed Fury (few years later). Last month I cancelled my repeat subscription due to the insane quantity of nerfs (i worked out individually there was 6 or 7 to fury alone). I kept playing until the a/c expired. I listed my reasons for quitting due to the nerfs to fury.

Then when the blue post mentioned that BT getting a 20 rage cost buff (down from 30) and the 4 second CD (down from 5), I signed back up in the hope I will soon get to see a change from being near the bottom of the DPS charts.

I just play to raid, I don't personally feel viable when I am taking the spot of a rogue or a mage or a feral druid for instance.

However, I do personally believe this stealth nerf is very deliberate (if it wasn't, the percentage would be different, not a straight 25%). It could have been altered pre 3.1 but they have already admitted recently they are happy with some classes being 25% dps behind rather than the 5% they have tried to sell all of us for such a long time. The problem with trust is once its lost, it's usually lost forever, or at least takes a lot to gain it back.

The lack of feedback usually means that they got caught and are thinking up an excuse or trying to figure out if they do change it back, what do they tamper with next.

This game is meant to be fun and enjoyable (though addictive), but every nerf that comes takes that little bit of extra fun out of it. I personally will be eager to see the response from GC or Bornakk because I think this could be the straw that broke the camels back.

Thank you Landsoul, I am an avid user and reader of your work. I personally am very grateful for you finding this. Keep up the good work.

---

Q u o t e:
I have been Fury for life (vanilla, I also have no alts), when TBC came and saw the giant nerfs on the PTR I quit until they fixed Fury (few years later). Last month I cancelled my repeat subscription due to the insane quantity of nerfs (i worked out individually there was 6 or 7 to fury alone). I kept playing until the a/c expired. I listed my reasons for quitting due to the nerfs to fury.

Then when the blue post mentioned that BT getting a 20 rage cost buff and the 4 second CD, I signed back up in the hope I will soon get to see a change from being near the bottom of the DPS charts.

I just play to raid, I don't personally feel viable when I am taking the spot of a rogue or a mage or a feral druid for instance.

However, I do personally believe this stealth nerf is very deliberate (if it wasn't, the percentage would be different, not a straight 25%). It could have been altered pre 3.1 but they have already admitted recently they are happy with some classes being 25% dps behind rather than the 5% they have tried to sell all of us for such a long time. The problem with trust is once its lost, it's usually lost forever, or at least takes a lot to gain it back.

The lack of feedback usually means that they got caught and are thinking up an excuse or trying to figure out if they do change it back, what do they tamper with next.

This game is meant to be fun and enjoyable (though addictive), but every nerf that comes takes that little bit of extra fun out of it. I personally will be eager to see the response from GC or Bornakk because I think this could be the straw that broke the camels back.

Thank you Landsoul, I am an avid user and reader of your work. I personally am very grateful for you finding this. Keep up the good work.

---

Odds are it was an intended change, and Bornakk jut didn't know about it. I would expect it to show up in the 3.1.3 patch notes, or a list of recent in game fixes before this thread gets another response.

It shall fall under "undocumented changes". Remember another "change" we got that fell under that category? I remember that day well, and what a sad day it was.

So should I just start assuming warriors are New Orleans when katarina hit and blizzard is the US gov?

---

Q u o t e:
So should I just start assuming warriors are New Orleans when katarina hit and blizzard is the US gov?

---

How long have you been waiting to use that gem ?? :rolleyes:

---

Q u o t e:
So should I just start assuming warriors are New Orleans when katarina hit and blizzard is the US gov?

---

If they take 5 days to give us an answer, then yes.

<---Former New Orleanian.

---

Q u o t e:


How long have you been waiting to use that gem ?? :rolleyes:

---

He had to wait so that he wouldn't have to say, "Oh too soon <_<"

---

Q u o t e:


He had to wait so that he wouldn't have to say, "Oh too soon <_<"

---

Welcome to the WOW player base:

"We compare Apples to Orangutans"

---

Q u o t e:
So should I just start assuming warriors are New Orleans when katarina hit and blizzard is the US gov?

---

Pretty much.

---

Q u o t e:
We investigated this issue and found it was not true – the rage generation formula has not changed anytime recently. So we looked into it further to figure out why this was being brought up and here are some of the problems we came across:

• In the formulas people are using, there is a constant value which is labeled as ‘c’. At some point in the past, someone calculated a formula for determining c based on their level and that formula is not correct past level 70 as this value needs retuning from time to time like when a new expansion comes out. The value listed for c is 320.6 when it is actually 453.3.
  
  
• We modified the system for displaying power bars in Wrath of the Lich King to have the client display its best guess of how much power they have, which is very deterministic for mana or energy, but not so much for rage. This most likely results in the displayed rage being off slightly at times, making the data collection more difficult. The client displays its best guess and the server validates the power usage against the value it knows they actually have - the two can be out of synch occasionally which throws the data off.
  
  
• Some of the testing was done with ungeared characters hitting for very small amounts. There is a component to the calculation we haven’t previously mentioned that will make the rage gained from those attacks sometimes not match the formula. Basically, the normal formula is Rage = (7.5d/c+f*s)/2. However, that result can never be larger than (7.5d/c)*2. This essentially means that very low damage attacks have a limit on how much they can be averaged up by the f*s component of the equation.

To try and clarify things for the number crunchers, conceptually, here is the formula for rage generation:

• 1) Determine rage based on damage done divided by a level constant (7.5*d/c)
  
• 2) Determine how much rage would be 3.5 rage per second when factoring in the hit made and the weapon’s speed (f*s)
  
• 3) Average the two of them together (the divided by 2 part).

---

Thanks for getting back to us.

The sad thing is, the next time players want something like this they'll still say "Blizzard alway says they'll get back to us and they never do."

---

Q u o t e:
We investigated this issue and found it was not true – the rage generation formula has not changed anytime recently. So we looked into it further to figure out why this was being brought up and here are some of the problems we came across:

• In the formulas people are using, there is a constant value which is labeled as ‘c’. At some point in the past, someone calculated a formula for determining c based on their level and that formula is not correct past level 70 as this value needs retuning from time to time like when a new expansion comes out. The value listed for c is 320.6 when it is actually 453.3.
  
  
• We modified the system for displaying power bars in Wrath of the Lich King to have the client display its best guess of how much power they have, which is very deterministic for mana or energy, but not so much for rage. This most likely results in the displayed rage being off slightly at times, making the data collection more difficult. The client displays its best guess and the server validates the power usage against the value it knows they actually have - the two can be out of synch occasionally which throws the data off.
  
  
• Some of the testing was done with ungeared characters hitting for very small amounts. There is a component to the calculation we haven’t previously mentioned that will make the rage gained from those attacks sometimes not match the formula. Basically, the normal formula is Rage = (7.5d/c+f*s)/2. However, that result can never be larger than (7.5d/c)*2. This essentially means that very low damage attacks have a limit on how much they can be averaged up by the f*s component of the equation.

To try and clarify things for the number crunchers, conceptually, here is the formula for rage generation:

• 1) Determine rage based on damage done divided by a level constant (7.5*d/c)
  
• 2) Determine how much rage would be 3.5 rage per second when factoring in the hit made and the weapon’s speed (f*s)
  
• 3) Average the two of them together (the divided by 2 part).

---

So the formula was changed in 3.0. Thank you for telling us.

---

Q u o t e:
We investigated this issue and found it was not true – the rage generation formula has not changed anytime recently.

---

Dangit, I really wanted 25% more rage...Its ok, probably wouldn't know what to do with it.

Thanks for the update.

---

Q u o t e:
We modified the system for displaying power bars in Wrath of the Lich King to have the client display its best guess of how much power they have, which is very deterministic for mana or energy, but not so much for rage. This most likely results in the displayed rage being off slightly at times, making the data collection more difficult. The client displays its best guess and the server validates the power usage against the value it knows they actually have - the two can be out of synch occasionally which throws the data off.

---

I've experienced this myself where I go to shout or something and it says I don't have enough rage even though my screen shows I do.

sigh, working as intended

Why on earth wasn't this rage generation nerf documented?

I can see why the constants were changed though, it makes sense. It sucks how our client can be out of sync.

Regardless, thank you for your attention with this devs, timely response is always appreciated.

---

Q u o t e:
sigh, working as intended

Why on earth wasn't this rage generation nerf documented?

---

Is it a nerf? It sounds to me like there was a level-dependent number that was simply accepted as a constant in previous 70-era calculations. Now that we've moved on to 80, that number is different, but that doesn't mean it was a nerf. I assume it was done so that as you get more powerful and obtain incredibly powerful weapons (relative to 70) that you don't eventually just fill up your rage bar by breathing on opponents.