Going to jump on the bandwagon and add another thread with the same topic to the list. if you don't know what the rage nerf is all about here's the link to the original thread on Elitist Jerks, observations made on live:

http://elitistjerks.com/f81/t60632-rage_generation_changed/

Essential what we got is an unannounced flat -25% to all rage generation from damage done, which is a crippling nerf to already struggling dps warriors.

If you want to help in getting at least the attention of forum moderators then copy-paste thread or start one of your own with a similar topic name, because they do pay attention.

Discuss.

Edit: The nerf is actually indeed live on 3.1, sorry for any confusion caused.

---

Q u o t e:
Going to jump on the bandwagon and add another thread with the same topic to the list. if you don't know what the rage nerf is all about here's the link to the original thread on Elitist Jerks, observations made on 3.1.3 PTR servers:

http://elitistjerks.com/f81/t60632-rage_generation_changed/.

---

There is no 3.1.3 PTR. If you actually read the information you would see the current Rage Bug / Nerf is on live.

---

Q u o t e:
Essential what we are getting is an unannounced flat -25% to all rage generation from damage done, which is going to be a crippling nerf to already struggling dps warriors.

If you want to help in getting at least the attention of forum moderators then copy-paste thread or start one of your own with a similar topic name, because they do pay attention.

Discuss.

---

Copy paste spam of the thread will do nothing but get the threads deleted. The only attention it will getting is the delete button of the moderators.

Blizzard are aware of the issue, as Bornakk said.. ''We are taking a look at this as we didn't make any intended changes recently to rage generation. ''

http://blue.mmo-champion.com/28/17367760070-newly-discovered-rage-ghost-nerf-unveiled.html

Yep, this is just going to buff us :) If it is a bug that is.

---

Q u o t e:


Blizzard are aware of the issue, as Bornakk said.. ''We are taking a look at this as we didn't make any intended changes recently to rage generation. ''

---

Well not going to hold my breath on that one, wouldn't be the first time blizz tries to slide in unnanounced changes.

These kinds of threads might get deleted or locked, but moderators/blizzards henchmen do take note when a large ammount of whines about a particular topic arises, because usually there some justification behind it, nothing bad about voicing your oppinion.

Stuff like this makes me wonder when WotlK is going to be released.

I mean, we're playing a beta, right?

---

Q u o t e:
Stuff like this makes me wonder when WotlK is going to be released.

I mean, we're playing a beta, right?

---

A MMO game is always under development. If you do not like constant changes to your game, Counter Strike is -------> that way.

Welcome to an MMO.

---

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.

---

What was wrong with the old system, how is the new system better?

---

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.[/ul]

---

Occasionally? It's actually more out of synch then in synch to be honest.

I'd prefer my information to actually be correct instead of a guestimation.



If you saw my face when I see another "not enough rage" message when trying to do a Battleshout (while my UI claims its 13 or more), you'd know that I have PLENTY of rage.

---

Q u o t e:



Occasionally? It's actually more out of synch then in synch to be honest.

I'd prefer my information to actually be correct instead of a guestimation.



If you saw my face when I see another "not enough rage" message when trying to do a Battleshout (while my UI claims its 13 or more), you'd know that I have PLENTY of rage.

---

I agree.

Any chance we could get accurate readings on our rage bars?

---

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.

---

Well if you played a warrior you'd know that it's actually "out of synch" quite alot, more than it probably should be. For example being on 11/12 rage and trying to do a shout and it saying not enough... makes me rage! then it tick down to 9 *angry face*

So the nerf stays?

---

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).

---

Ok thanks for providing some small additional insight behind the menachics of rage generation Slorkuz.

Yet the 'sudden drop of rage' phenomenon that people are talking about (rage gain displayed by clients
rage bar is split second later dropped by x ammount) was obviously not around before 3.1 (read rage
calculation formula of client&server ended up at equal results pre-3.1).

And if both Server internal and Client use the same formula (as they should otherwise there is no telling
from Client side what we'll get) to determine the X ammount of rage generated from a warriors meele
swing, then how can client and server end up at different results?

Again, note that before 3.1 there were no discrepancies
between the rage gain calculated by the client and the
rage gain calculated by the server.

Not necessarely rock solid proof of a stealth nerf but,
neither did you present and solid proof that one didn't
take place either Slorkuz.

Blizzard has also repeatedly said in the past that they are unhappy with with rage becoming unavoidably
a pretty an almost infinite resource at extremely high gear levels + raid buffs, which results in seemingly
balanced warrior dps going through the roof without warning.

(The target here would this time yet again be The Dreaded and Overgeared Fury Warrior of the Future,
who already sits and waits in his full T10.5 hard mode gear to bring tears and agony to Blizzard and it's
development team.)

/end wall of pain, feel free to lock.

Btw keylogger up there.

---

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.

---

Why? The formula uses constants. The damage done is known both to the client and the server. How can it be off?

Very so true though. Oh the countless times I see that I have precisely the amount of rage to use an ability, and I get the 'not enough rage" error. I always thought that was a bug, or my math skills being bad, or losing rage at that very milisecond when ooc. Apparently this is indended.

---

Q u o t e:


Well if you played a warrior you'd know that it's actually "out of synch" quite alot, more than it probably should be. For example being on 11/12 rage and trying to do a shout and it saying not enough... makes me rage! then it tick down to 9 *angry face*

---

Ive noticed this lately on my warrior. Its been at even 12-13 rage and still it ticks down while im spamming shout:/

---

Q u o t e:

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).

---

Slorkuz & Bornakk.. Why does the rage generation formula has to be so complex?

As we level, the cost of our abilities doesn't increase. Our max amount of rage doesn't increase. I don't see why our rage generation has to change?

Make warriors generate rage per swing, not per hit. The amount generated would be normalized based on weapon speed, not damage done. This would solve a _lot_ of warrior issues, both for the players and for you developers.

Most importantly it would solve the main issue with balancing warrior damage, in that every buff or nerf to our damage is double dipped - Nerfing our damage nerfs our rage generation which nerfs our damage even more. And likewise when damage is buffed, leaving warrior damage in a perpetual yo-yo between overpowered and useless.

It would also solve the gear issue in that a poorly geared warrior is incredibly boring and frustrating to play, because you're constantly just waiting for enough rage to use another ability.. And with the way the rage formula works now, you can't buff that without making well-geared warriors overpowered.

And finally it would solve our constant pvp issue with not getting rage on shielded targets.

There is no point in askning here since he just copy / pasted the thing from another post on US forum and my guess is that he doesnt know a thing about it