Please revert feral hotfix/use 2.0 energy [FIXED, ty Blizz!]

We have a handful of active posters on either side of the issue. Stop pretending there’s thousands of active people upset about shred spam being slightly less effective and only 2 people pointing out that feral is over all in a very good place right now.

1 Like

Then you should understand that doing every single thing asked by every customer is a recipe for disaster.

1 Like

There is a drastically more support for the change in this thread. Please learn to count. And if you remove blunt trolls it becomes 100%. Stop pretending. And thanks again for all the bumps.

1 Like

Again your trolling is just grasping at straws now. Let me repost what i wrote it 2 posts ago if your memory is falling you.

Customer’s wishes is what drives the direction for any software development. Obviously there are plenty of conflicting wishes and and one point company needs to make a decision to address it one way or the other based on variety of metrics (not doing anything is also way of addressing it). The number of people for and against a change is 100% one of the key metrics to look at when you make a decision. Hardly the only one, but important never the less.

At least before you attempted to pretend you not complete troll, but when you literally trying to tell me what i wrote a post earlier and claim as a counter “argument” is crossed the line. Have a nice day and please keep bumping the thread.

2 Likes

And given that blizzard has addressed the customer raised issue on this twice and both times decided it’s not a bug and not something they’ll be changing it seems they’ve met your criteria for what a company should do and you should accept that.

If you actually understand that companies shouldn’t always just blindly do whatever anyone asks them to.

1 Like

fix the tick
thanks
<3

3 Likes

Resorting to to blunt lies now?

1 Like

Please elaborate.

There are 2 separate events discussed you either intentionally or due to lack of common sense still do not grasp it.

Change in 2.2 - BUG. Confirmed by Blizzard. Never fixed because …

  1. They decided it is better this way.
  2. Because like 100s of other bugs just never got fixed like the fact that i am 66 and forum shows 60 and this was the case for 14+ years.
    I do no have any valid data on which one this was. Nor did i see any blue posts stating #1.

Second event creating TBC classic using 2.4.3 as a template.
2.4.3 energy work same (or nearly the same… not sure if 19 energy ticks were there) as current tbc classic. - NOT A BUG (this is the part that was stated to not be a bug). Maybe someone called this a bug i didn’t and majority of the posters didn’t.

However due to the fact that the original change in 2.2 was a BUG in combination with #somechanges stance by blizzard and the fact that change of making medioce dps utter trash makes no sense and does not represent experience for the majority of raid content in TBC community is asking to include this change in #somechanges.

The change makes no sense no matter what your opinion on powershifting is. It did not remove, it is still optimal. It made it less enjoyable which is hardly a goal for any change made by blizzard. Clearly blizzard did not feel ferals should be worst dps because few month later after 2.4.3 wrath came out and made cat’s amazing.
Obviously buffs to class X is not always positive thing, if you buff hunters now by 50% a lot of people will be pissed since they are already #1, but buffing currently worst dps by 14% and making their rotation more fun is hardly making any one else’s experience around them worse. ( Obviously there are exceptions like you but that is a extreme trolling minority )

This was explained to you multiple times and yet you keep resorting to stating blunt lies that this was not a bug. It was in 2.2 and that is exactly what i stated and yet you come here and bluntly lie.

Is that elaborative enough for you?

1 Like

Confirmed as not a bug by modern Devs. Players called the lack of continuous tic Energy a “bug” and reported it as such in Beta. Blizzard confirmed it wasn’t, not because it was merely accurate to 2.4.3, but because it was simply how it was supposed to be. People reported then that it was a bug from an earlier iterations, Blizzard was unmoved and kept it as is.

That’s why Zipzo tried to make a thread proving Blizzard wrong, that partial tics still existed in 2.4.3. This was shown to be false.

You keep belaboring a lie. Stop that.

Do you have source for that??? No you don’t.
There is however a link from 2.2 era where blue states this was not intentional.

Which is why i am going back to you resorting blunt lies? If there would be a source for dev’s confirming it was not a bug you would be shoving it down people’s throats every post. But you don’t because you don’t have anything but your own BS to back it up.

1 Like

Cope harder.

Irrelevant to modern Devs.

Source? oh right… your own bs doesnt count trolol

1 Like

Are you god? to know what is and what is not relevant to modern devs of classic tbc? Clearly it matters to a noticeable part of feral community. And pretty sure current player base opinion on state of the game matters to current devs. So i find it hard to believe it does not matter to current devs personally but hey i am not a god i don’t know for sure.

1 Like

No but not sure I know what this has to do with old Devs

huh this is new low even for you. Is there a point somewhere in there?

You go off on tangents unrelated to what I say… you tell me.

See my previous comment.

The irrelevant comment was referencing the statements of old community manager posts… can you read?

Delusional much? This what you quoted. This was part of answer to you about modern devs. More so no where in the rest of the post you started to quote mentions old devs. Yet again new low.

1 Like