Blood golem minions meta ftw
However, if it was supposed to go through a QA process not to let certain things occur or the coding was supposed to take in account of this and failed to do so without having appropriate catches, then it would be a bug.
I.e. they were supposed to firewall the attack speed off the damage from the ball lightning and screwed that up.
The fact of the matter is - you donât know, we donât know.
What we DO know is that they categorized tibaults and ball lightning as bugs.
They did not quantifiably consider overpower as a whole as bug.
So why second guess it?
To be itâs quite simple, if blizzard calls it a bug, it was a bug. We can play the semantics game or whatever you want to do redefine the words or how they were meant to be or what was the intent - but the tale of the tape ends with the patch notes as they stand.
This was obvious to anyone with more than 2 brain cells. Unfortunately many Blizzard Defense Force members donât.
1 Like
2 brain cells? Even single cell amoebas knew BL was bugged!! 
2 Likes
I didnât care if it was Bugged or not, Sure made the season a lot of FUN for me.
2 Likes
WellâŚ.now we are in S3.
Cant wait to hear what build is âbuggedâ for this season.
I agree with ctrlaltd1337, i dont think BL was âbuggedâ. I think that the build was exactly what the devs made it to be, and they called it a âbug fixâ to save face because of the outrage that ensued.
I didnt see anyone complaining about rogues, barbs or druids high damage. I wish people would just come out and admit they hate the sorc class so the complaining would stop.
What am i thinkingâŚthe complaining will never stop.
2 Likes
Bottom line is they did the right thing by not making the change during the season after people had invested time and effort into their characters as they existed. Between seasons is fine to make changes because you wonât feel like you have to abandon your character for lack of performance.
The rest is just semantics and you guys are arguing a very thin line of definition of what a bug is. Itâs silly. The power of ball lightning was an unintended outcome but whether it was a mistake or a product of developers that donât understand their own systems remains to be seen. One is a bug, the other is incompetence.
BUTâŚyou can have both of these at the same time.
And i think that is whats confusing people here.
The problem is, both of those things leads to the other.
The origin of this bug is patch 1.2.0 (the upcoming patch is 1.3.0 just as a note). Read their wording about the supposed BL tooltip fix in 1.2.0:
- Fixed an issue where the tooltip for Ball Lightning would erroneously display damage factoring in Attack Speed with the Enhanced Ball Lightning upgrade. Fixed an issue where the Enhanced Ball Lightning upgrade tooltip incorrectly displayed damage based on your attack speed.
Instead of adjusting the damage down to account for the attack speed increase as per the fix, they actually made the supposedly wrong display on the tooltip a reality with the patch.
If Iâm wrong or anyone understands it better, then please comment.
Well when does a bug get not fixed?
See i think they cant turn thr fixes around fast enough to be able to avoid major player QQ.
If the ball lightning was fixed within a day of finding the problem (tibaults) also, i dont think we would have this issue.
Sets the course to not fix any problems that give power like this, but this is a slippery slope.
It takes some refined mental gymnastics to say its not a bug fix when devs say its a bug fix.
Congrats some of u on yur gymnastic gold medals.
Has even 1 person said sorry I was wrong on BL when I said it is not a bug? No adults in the forums? Not surprised I guess.
2 Likes
Urza, itâs just people defining the word differently to control the narrative.
Just bad debate practices and extremely poor framing - and par for the course
Doesnt matter how other ppl define it. Devs have defined this as a bug and bug fix so saying this was not a bug fix is some sort of rogue smoke bomb look over here trickery!
Devs are the final say on what is and is not a bug fix not non-dev forum orcs.
So the final word is this was indeed a bug fix and I and the other ppl saying it was are right and those saying it was not a bug are wrong.
This is 100% facts now. 
2 Likes
And my post is PRETTY freaking relevant now, huh? Iâll just leave this right here.
Duces, silly gooses!
1 Like
You make alot of good points. You are good thinker wolf.
Maybe look at history of my posts before making this judgement. I give Bliz credit credit when they do well. I criticize when they dont. Im realist. Tell how it is.
Thatâs why itâs silly to argue over semantics.
If by âbug fixâ they meant âWe maffed again and it didnât work right so weâre unmaffing it. We thinkâŚâ
RIP BL sorcerer, back to druid
well to be fair what people could call a âbugâ is very very subjective
it depends on how you define a bug.
if for you bug is something unintended by the devs , then BL was indeed buggued .
but then again by that same logic : any skill overperforming or underperforming could be called a bug.
at the end of the day itâs just the devs not testing properly the balance of their own game or what they add / remove between each patch.
i personally wouldnât call it a bug (despite it being unintended) since i have a vision a bit different of what a bug actually is (like a chest looting stuff infinitely, snapshotting etc⌠but not an overperforming skill due to not being tested)
but thatâs my take
eitherway we knew about it being unintended and it was unintended.
No it doesnt. It doesnt matter anymore how any of us define a bug.
THE DEVS HAVE LITERALLY CALLED BL BUGGED AND BUG FIXED NOW!
IF we are not going to let devs be experts on what is and is not a bug in dev code then who is?
I mean this is just pure obama video shrugsville at this point saying BL not bugged.
2 Likes