Because it was unintended which is why it was fixed.
A post from 2023 about a different situation is not relevant here.
How is this not relevant? Both appear to be shadow nerfs, Care to elaborate why bear weaving is different instead of just stating that it isn’t?
And you didn’t answer my question about the inconsistency that you can still do this today while questing and in heroics. I work in product management with software developers, normally when you code for bugs, you shouldn’t be able to do this anywhere.
Because it’s about a different situation and it’s a year old.
This was a bug fix.
What is there to say here? I’ll make sure to report that bug so Blizzard can fix that as well?
How is the situation different? You’re totally a politician just saying things and not explaining how are they not relevant.
I just told you how. This was a BUG FIX.
Please read things.
You’re wasting your time with Blooms.
4 Likes
A new fan joins the thread.
lol your reason for it being a bug is because it’s unintended. How about you read Aggrend’s post because he uses the word, wait for it, UNINTENDED. Rofl.
Not all unintended things are bugs but all bugs are unintended. Bear-weaving was a design oversight. This was a bug that was exploited and abused.
The difference is obvious.
So then how is it obvious? This also fits in your own criteria as a design oversight too rofl. Keep digging my guy.
I wouldn’t say I’m a fan I’m more indifferent
I would say all these boomy threads have been very entertaining
I just explained this in the above post.
That’s funny, because I never even gave my criteria for what is considered a design oversight and what isn’t. If you can’t read things then I’m afraid this will not go any were.
Your fan behavior says otherwise hehe.
Then care to explain? Your above post is just a statement, not an explanation.
Explain what you mean by design oversight then.
And by the way, just because you say it’s a bug doesn’t mean it’s a bug. If it was, it would be listed here:
The problem is that you aren’t aware of what was changed with boomkins. Eclipse has always used the mastery stat when it is initiated, and it has always persisted when entering combat. The change is that an exception was made when entering boss fights where if one is in an eclipse, the eclipse state is reset. Do you understand?
1 Like
Yes. I understand that a bug existed in original cata, it persisted to cata classic, and Blizzard finally fixed it.
Do you understand this?
Bloomsday is a devoted troll and Blizzard simp, speaking to him is a waste of time.
2 Likes
You didn’t read what I said. This is how it was intended to work, and how other stats in WoW work. Which doesnt mean it shouldnt be changed. Changing it was a good idea. It was just changed in a way that also affected other areas of play negatively.
1 Like
Yeah, I’m still laughing how he doesn’t realize he’s speaking in circles xD? He‘ll be a perfect politician one day.
Him: blizzard fixed the bug
Me: how is this a bug when it still exists today? Also blizzard posted this about shadow nerfs:
Him: because it’s a bug and (doesn’t read the post) 2023 post isn’t relevant in 2024
Me: how is the 2023 post not relevant?
Him: (doesn’t read) because it’s a year old and this is a bug fix.
Me. You’re not explaining why it’s a bug.
Him: (speaks in circles) because it’s a bug! It was unintended so blizzard fixed it.
Me: *points to Aggrends post that there will be no more shadow nerfs in classic until tested in PTR first. So tell me why bear weaving is unintended and eclipse not working in raids are not the same? Both are unintended.
Him: bear weaving is a design oversight
Me: and eclipse can also be considered a design oversight?
Him: I didn’t give my criteria for what design oversights are:
Me: then explain what you mean by design oversight?
Again, you don’t get to decide that. The game belongs to Blizzard, not Asturiat. Blizzard decides how things are intended to work, not Asuriat.
And Blizzard decided this was unintended and changed it. That’s it, case closed, do not collect $200, do not pass go.