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

Actually no not intentional does not mean bug, it merely means they hadn’t thought about that ahead of time. Especially when talking about high level changes to large systems, sorry if your super niche gimmicky play style wasn’t included in the decision making process.

1 Like

“PROVE MY SPECIFIC NEGATIVE HYPOTHETICAL OR BE SILENT!!” - the fool said

2 Likes

Paladin seals say hi to trollol…

But even so, making a stand that hey we picked 2.4.3 and you need to deal with it is a FAIR stance. And i seems to be that this is their stance for now. My personal way of dealing with it was to cancel subscription. No one is disputing that this is bug that has to be fixed. But due to combination of things we are asking blizzard to reconsider. If you can come up with a different change that has same amount of reasoning why i should be made, i would probably even support it, not that my support means squat in this case.

1 Like

Oh, is your issue with powershifting actually because of spell batching working differently now vs in TBC?

I thought it was because of a specific patch that actually changed the mechanic during TBC.

except power shifting is an exploit, so the fact that it negatively impacts feral druids abusing an exploit is irrelevant. Therefore it’s NOT A BUG!

1 Like

Again i dont know where you come from. In world of software development unintended side effect = bug.

A software bug is an error, flaw or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.

Even if unintended way ends up positive (which this was not) it is still a bug.

1 Like

it is exploit because you said so?.. or …

1 Like

Blizzard did, that’s why they killed it.

There were given seal of blood. it has nothing to do with batching trollol

1 Like

Considering you have consistently and bluntly lied in this thread, your world without a source means nothing.

1 Like

But it was not an error, flaw or a fault in the code. The change was implemented exactly as designed. The impact it might have on power shifting was simply not considered one way or the other.

Oh the straws are so thin now. The design was to give innervate QoL change. it created some (negative) impact to some part of the customers, which was NOT part of the design, clearly stated as such. It is what is commonly know = BUG.

1 Like

You’re here gaslighting everyone all day every day. I don’t think you get to call anyone out on moral integrity.

Just be honest and ask for buffs.

1 Like

Okay so now we’re not arguing about whether it’s a bug or not, it was just lack of proper research into the full impact of the change. Of course given that blizzard deemed it a non issue when it came up that should give you an idea of how they would have felt about it had they known before hand.

This is also assuming they didn’t know before hand.

https://thebigbearbutt.com/category/wotlk-beta/

Sorry for your loss.

1 Like

Hi Blizzard, just checking in to see if you care about the community…magic eight ball says no.

1 Like

First of all good job on finally trying to provide a source.
Second of all lets do a search for powershifting, shell we?

GC: We think this would encourage quickly shifting from one form to another, which is something we have actually taken pains to discourage (RIP powershifting).

We have taken steps to discourage in WRATH, and they did, you no longer powershift in wrath.

. Anything that starts to feel like the old powershifting (changing just to generate mana) is what we’re trying to avoid

Yet again, in the new design of wrath they want to move away from powershifting. And they did.

So where does it in anyway shape even remotely said it is an exploit?

Just because they decided to change the way cat works in the next expantion does not make powershifting an exploit. Does any change to class mechanic makes previous an exploit by this logic trollol?

Sorry for your loss.

1 Like

From the Beta you silly person. Sunwell was still ongoing.

Right there you dope. The behavior was never supported and anything that might start to look like it was explicitly avoided.

Sorry for your loss.

1 Like

So let me translate attempt to argue:

They were told about the issue, they did not fix = they didn’t think it is an issue or they thought it was good for the game.

so by this logic:

14+ years ago they were told forums do no update levels correctly, 14 years later that is still the case thus they decided it is not a bug and/or is good for the game.

Sure thing…

1 Like

You do know how quote right there is where exactly? Which particular line in your confused troll mind calls it an exploit?

1 Like