Then you, like Beastfury, don’t want actual evidence, you just want evidence™ subject to your personal liking.
/shrug
And yet Feral issues and Druid issues were ignored often in Vanilla/TBC, despite how loud the forum goers were. I was there, we got passed over a lot.
GC was a godsend compared to what came before.
The hybrid tax was eliminated, but that wasn’t why we could suddenly chug potions in forms and benefit from weapon procs.
Which falls into the “don’t care” bucket since it sits at a lower priority than the thing it might break. That makes the Feral “problem” one everyone just has to live with since some other problem took priority. That is a distinction without difference.
So I will reiterate: if 2007 Blizzard didn’t care, why should 2021 Blizzard?
Yes…No… Not it does not prove that is a bug. Minior detail i never states as the reason why this i bug but you right minor detail. You continue to put words in my mouth, i have corrected you multiple times on posting complete and utter BS claiming i said something i didn’
I went i checked i didn’t find any, i am sorry i am old and stupid please help me out here, can’t be that hard can it?
Yet again which part of that blob was evidence? But i am sure you will just ignore this question yet again.
You are aware i literally just answered you? Ignore things you don’t like much lol?
But hey I will do you a favor:
As for why should they care, i gave you at very least 1 reason. At the time of the bug their development was focused on next expansion, because that is what will make next set income spike. There was limited time left (which kept being extended during end of tbc) before it stops mattering given the future rework of cat dps. This however is not the case now. The point of classic TBC is to play TBC not to hold out until wrath. It also affect WHOLE tbc not just sunwel.
Bwahaha it is the basis of your entire argument and why you refuse to accept the current “Not A Bug” list as satisfactory!
Moving on…
You do understand how quotes work right? Your reasoning is that they have time to squash bugs now that they didn’t before… but that only works if it is actually a bug, which it isn’t, as you accepted (very regretfully) above.
I was seeing what Draugwath’s reasoning was.
Anyway, you’ve given the concession so you and I are done.
Basis of my argument is CM post and lack of mentioning of that in the 2.2 patch notes. Your delusions are amazing.
You taking a statement made about transition of 2.4.3 → tbc classic as basis that 2.2 change 14 years ago is not a bug that is just next level of delusions.
Same way in vanilla classic they listed multiple clear BUGS in expected behavior because the entire intent of class is recreate original, so they recreated bug on purpose. They were listed not a bug during vanilla beta.
The fact that “not a bug” does not refer to 2.2 change however does NOT mean 2.2 was a bug you are correct here at least. But i did mentioned a minor detail you forgot however already.
So you still can’t produce any of the imaginary evidence, wonder why.
So you continently ignore the fact that are plenty of clear bugs (referred to as such by blizzard too), which were listed in vanilla response as “not a bug” because classic recreating the exact behavior of original and thus it is not a bug?
It is identical situation. LOL
It literally says so in the post.
As was the case with WoW Classic, there are many issues that have been reported to us in the Burning Crusade Classic beta as bugs, but are actually correct behavior in the original game, or are otherwise expected behavior in Burning Crusade Classic.
It is literally mentioned in the not a bug post, clearly stating the same logic and intent. Given that in vanilla classic bugs were recreated on purpose and placed on the “not a bug” list. It is more then valid to assume this remains the case for TBC given the literal comparison in the post itself. In theory it might not be so, but there is zero reason that i am aware that magically the logic and intent of the “not a bug” list change given that mentioned as “Just as in”.
Tut tut Beastfury! Rules for thee but not for me? How pathetic… you spent all that time arguing until you were blue in the face that anything looking back from the Wrath/Cata era was irrelevant and now here you are making assumptions trying to carry forward an explicitly different concept from Vanilla Classic to TBC Classic…
That being said!
This is the relevant portion, notably the very last clause.
“Otherwise expected behavior in Burning Crusade Classic” is different from “correct behavior in the original game.” Patch 2.4.3 isn’t explicitly mentioned either, but rather just “original game.”
So from all of this we can determine the following:
The full reset of Energy when shifting into Cat Form is explicitly stated by Blizzard to either be “actually correct behavior in the original game” OR is “otherwise expected behavior in Burning Crusade Classic.”
That means it isn’t a bug, either by accuracy to the original TBC or because this is the expected behavior (expected by Blizzard) for TBCC.
Bravo you figured out what i was telling you all this time. Now figure out the part that “actually correct behavior in the original game” can refer to a BUG.
Why?
Because in the same “not a bug” list in vanilla there are BUGS (marked as such by blizzard) are in that list.
Why do we can about vanilla “not a bug” list?
Because the TBC “not a bug” list specifically mentions the same exact post in Vanilla with modifier “JUST AS IN”.
So we know that we did have bugs in “not a bug” list classified as “actually correct behavior in the original game”. We also know that “not a bug” list is “JUST AS IN” vanilla.
Thus… the logical conclusion that we can have tbc bugs being in “not a bug” list classified as “actually correct behavior in the original game”.
I believe in you you can figure this part out too.
The marriage of both “correct behavior in the original game” and “otherwise expected behavior in Burning Crusade Classic” renders your distinction moot. It doesn’t matter if the originally faithful game produced a bug or not, because the catch-all clause blesses the entire ordeal. Further still, Blizzard made no distinction between “Not A Bug” based upon original game vs “Not A Bug” based upon expected behavior for TBCC for any given listed “Not A Bug.”
Blizzard has scraped the slate clean and said “Here are the rules as we move forward” and that is that. Original game is equated to otherwise expected behavior, and that means Energy resets on shift.
Your entire argument hinges on a false premise and misunderstanding of Blizzard’s own stated word. All of the other probative evidence surrounding this topic is more focused on convincing those desperate for a change in their favor to temper their expectations as Blizzard is HIGHLY UNLIKELY to give them their way.
But the most basic argument here is that whether faithful to the original game (patch agnostic) or faithful to the expected behavior of TBCC (according to the current Devs), the current state of Energy reset on shifting is not a bug.
Alrighty, as for if the energy issues is a bug from old client to modern client I think we can firmly say that is it “Not a bug”. As for if the original change when it was implemented in original TBC was a bug… it deserves a second look. The Community Manager post referenced does not necessarily prove that it was a bug since he/she was not in the position to make that statement. The fact that devs said later on that they did not condone powershifting also does not prove that it was not a bug. (This is because the reasons they made the change had nothing to do with powershifting directly but rather mana regen from evocation and such) We honestly won’t know unless we ask the original devs who implemented the patch. Regardless I don’t think it matters if it was a bug or not because…
Here is the part that matters!!! Devs certainly acknowledged in Wrath that feral druids were in a bad place at the end of TBC and made changes accordingly. I don’t think anyone is asking blizzard to pull wrath changes for feral into Classic TBC, however for the majority of TBC (and classic) feral was much more enjoyable to play due to powershifting (regardless of if bliz condoned the behavior or not). We as a feral community are simply asking for plz to consider adding powershifting into #somechanges.
Blizzard undoubtedly chose a later patch for TBC because most changes made throughout TBC made classes better, the reason your hearing about feral energy so much right now is because this is one example where the change made to the class in this patch was worse than it had been for the majority of the expansion. There is plenty of evidence that this change is worse, see all the arguments above. (clunker rotation, lower dps, ect.) Again for these reasons we ask the blizzard please add feral energy to the #somechanges. I promise you we will not ask you to keep powershifting in classic Wrath!
We just want to play the class as it was played originally (intended or not) for the majority of the expansion. A compromise I would suggest is to keep the energy regen in for phases in which it existed and take it out for the phases when it didn’t exist. This would be the most “ACCURATE” representation of the original experience.