Hotfixes October 4th – Fan of Knives Combo Points, Well of Existence, War Campaign UI



Comment by Melilithia

on 2019-10-04T20:14:38-05:00

No more “somebody spilled their pringles can” screenshots? Aw.

In all seriousness… phew. That visual bug was straight-up weird.

Comment by MorbidFable

on 2019-10-04T20:18:37-05:00

Better late than never. I honestly wasn’t seeing them though

Comment by musclepaw

on 2019-10-04T20:28:29-05:00

Looks like BFA $20 off sale is extended to OCT 20, 2019.r
r
Can we see the new RFA before OCT 20?

Comment by Ishtor

on 2019-10-04T20:38:34-05:00

Wow and it only took 3 1/2 months to fix a dumbass visual bug. But hey, at least I’m glad Blizz didn’t pull any programmers off of retail for Classic. Imagine the drop in quality and response times we’d have in BfA if they did that. There’d be stuff like broken classes on release without fixes for months and other weird things.

Comment by Leftkeywest

on 2019-10-04T21:00:58-05:00

Wow and it only took 3 1/2 months to fix a dumbass visual bug. But hey, at least I’m glad Blizz didn’t pull any programmers off of retail for Classic. Imagine the drop in quality and response times we’d have in BfA if they did that. There’d be stuff like broken classes on release without fixes for months and other weird things.r
r
I don’t think Classic needs many programmers, everything is already there just hidden behind phases as the game is the same one from years ago. With how small these hotfixes for BFA are though, I’d imagine everyone from Blizzard is working on the new expansion instead of focusing on BFA. You also have to take into consideration the amount of things in Classic is just a fraction of what’s in BFA, which contains every expansion, and those systems can collide with each other causing these bugs.

Comment by Ishtor

on 2019-10-04T21:23:29-05:00

But much of Classic required a rebuild from the ground up as Blizz had stated themselves repeatedly that much of it was simply lost. I’m not talking about BfA’s state right now but rather the abyssmal state it has been in ever since… well ever. I’m well aware where bugs like these come from. 99% of them are completely freak reactions of a 15 year old game engine that nobody could anticipate. It’s been apparent that BfA never had the manpower behind it that it required.

It was rushed to market in a pre-Beta state, several Classes simply weren’t ready, Dungeons were horribly bugged, Quests didn’t work, Azerite Traits were being rebalanced on an hourly basis, Azerite Armor as a whole were never properly tested or even thought through… and that’s just the first few weeks of BfA. The issues go on until today and yes, they include needing over 3 months to fix something as banal as a visual bug.

I understand Blizzards impulse to cut bait and move on past BfA towards the next expansion, but if they continue down this path I’m afraid that there won’t be many people left once they rush out the next eypansion to finally get BfA over with. What the game needs right now is care and repair. Not a scorched earth policy with a skeleton crew. If they want to work on the next expansion simultaniously, here’s a strange thought: Hire more people. It’s not like they can’t afford it. WoW is still Blizzards biggest earner and the second to third biggest earner in Actiblizz as a whole.

Comment by Rudeguy

on 2019-10-04T21:27:57-05:00

But much of Classic required a rebuild from the ground up as Blizz had stated themselves repeatedly that much of it was simply lost. I’m not talking about BfA’s state right now but rather the abyssmal state it has been in ever since… well ever. I’m well aware where bugs like these come from. 99% of them are completely freak reactions of a 15 year old game engine that nobody could anticipate. It’s been apparent that BfA never had the manpower behind it that it required. r
r
It was rushed to market in a pre-Beta state, several Classes simply weren’t ready, Dungeons were horribly bugged, Quests didn’t work, Azerite Traits were being rebalanced on an hourly basis, Azerite Armor as a whole were never properly tested or even thought through… and that’s just the first few weeks of BfA. The issues go on until today and yes, they include needing over 3 months to fix something as banal as a visual bug.r
r
I understand Blizzards impulse to cut bait and move on past BfA towards the next expansion, but if they continue down this path I’m afraid that there won’t be many people left once they rush out the next eypansion to finally get BfA over with. What the game needs right now is care and repair. Not a scorched earth policy with a skeleton crew. If they want to work on the next expansion simultaniously, here’s a strange thought: Hire more people.r
r
none of this is true, tldr.

Comment by slacker6

on 2019-10-04T21:30:40-05:00

here’s a strange thought: Hire more people.r
r
This is not a solution. More bodies won’t fix anything, especially with the amount of context in a a game engine like this. Your solution coined it – they need more time. It’s just hard to do that with how fast people want things.

Comment by Ishtor

on 2019-10-04T21:50:19-05:00

This is not a solution. More bodies won’t fix anything, especially with the amount of context in a a game engine like this. Your solution coined it – they need more time. It’s just hard to do that with how fast people want things.

I wouldn’t mind waiting a month longer for a patch to come out. But when it comes out and the conclusion to the war campaign takes a grand total of 10 minutes, not counting the (honestly great) cinematics, i can’t help but feel a lack of effort here. Has anyone considered the fact that the war is over and there won’t be a third warfront? That makes 2, count TWO, main features of BfA that are done and over with in 8.2.5. Creative way to cut the workload. But I’m getting off track.

My point is: If it’s not lack of manpower, then it’s effort that’s missing. Because if anyone can look me in the eyes and tell me that BfA is fine and doesn’t need more work they are either delusional or lying to themselves.

Comment by Peredhil

on 2019-10-04T22:25:38-05:00

But much of Classic required a rebuild from the ground up as Blizz had stated themselves repeatedly that much of it was simply lost. I’m not talking about BfA’s state right now but rather the abyssmal state it has been in ever since… well ever. I’m well aware where bugs like these come from. 99% of them are completely freak reactions of a 15 year old game engine that nobody could anticipate. It’s been apparent that BfA never had the manpower behind it that it required. r
r
It was rushed to market in a pre-Beta state, several Classes simply weren’t ready,, Dungeons were horribly bugged, Quests didn’t work, Azerite Traits were being rebalanced on an hourly basis, Azerite Armor as a whole were never properly tested or even thought through… and that’s just the first few weeks of BfA. The issues go on until today and yes, they include needing over 3 months to fix something as banal as a visual bug.r
r
I understand Blizzards impulse to cut bait and move on past BfA towards the next expansion, but if they continue down this path I’m afraid that there won’t be many people left once they rush out the next eypansion to finally get BfA over with. What the game needs right now is care and repair. Not a scorched earth policy with a skeleton crew. If they want to work on the next expansion simultaniously, here’s a strange thought: Hire more people.r
r
none of this is true, tldr.r
r
Unfortunately, plenty it is. I highlighted some, just in case you need help in text interpretation. I can also elaborate on each idea and why I consider these true. Don’t worry, my attention span extends beyond the tl:dr so feel free to express your opinion in detail ;).

Comment by JCarr178

on 2019-10-04T22:33:17-05:00

here’s a strange thought: Hire more people.r
r
This is not a solution. More bodies won’t fix anything, especially with the amount of context in a a game engine like this. Your solution coined it – they need more time. It’s just hard to do that with how fast people want things.r
r
very true. they need to start hiring people with actual skill in development and people that can program beyond a community college level. They hire people who “love blizzard” because they know they can pay them half what the rest of the industry pays, and they will lap it up like little puppies drinking mother’s milk.r
r
instead of hiring fanboys that suck at their job, hire some real game devs that understand what it is to make an enjoyable game.

Comment by Ishtor

on 2019-10-04T22:48:07-05:00

none of this is true, tldr.r
r
You have to love people who come to forums just to post that they didn’t bother reading. Would you care to elaborate on your claim or do you get distracted when you see yourself writing more than 6 words as well? Ah dammit, this is probably too long for you already. But don’t you worry, not everyone has the mental fortitude of a third grader. The world needs Burgerflippers as well so there you go. Bright future ahead.

Comment by toxicrusader

on 2019-10-05T01:00:57-05:00

I wouldn’t mind waiting a month longer for a patch to come out. But when it comes out and the conclusion to the war campaign takes a grand total of 10 minutes, not counting the (honestly great) cinematics, i can’t help but feel a lack of effort here. Has anyone considered the fact that the war is over and there won’t be a third warfront? That makes 2, count TWO, main features of BfA that are done and over with in 8.2.5.r
r
Never thought that way, and damn, this is so true!

Comment by catfishmike

on 2019-10-05T01:08:43-05:00

none of this is true, tldr.r
r
You have to love people who come to forums just to post that they didn’t bother reading. Would you care to elaborate on your claim or do you get distracted when you see yourself writing more than 6 words as well? Ah dammit, this is probably too long for you already. But don’t you worry, not everyone has the mental fortitude of a third grader. The world needs Burgerflippers as well so there you go. Bright future ahead.r
r
Calm down nerd.

Comment by Manthela

on 2019-10-05T01:26:04-05:00

As usual this thread, like any dealing with bug fixes, has turned into a “complain about anything” thread. Probably 99% of you mass complainers have zero inclining of what it takes to write code for a game this massive. Or to have to go through millions of lines of code to fix bugs after you add more code to it. Just because they work for Blizzard and make games doesn’t mean they are omnipotent and can pick out errors on a whim. Any of you that are complaining really think that when a developer or engineer sees or reads a report on a error that they say “hmm, oh well I don’t care if it looks stupid or doesn’t work right. I love all the complaints I get about the game being stupidly buggy!”? I would conclude to say no. No they don’t So in the spirit of Colonel Nathan Jessep I suggest you say “Thank You” and be on your way. Otherwise pick up a key board and learn to fix code yourself.

Comment by JaceDraccus

on 2019-10-05T02:00:09-05:00

here’s a strange thought: Hire more people. r
r
The last time they did that (WoD, I think?) it ended up delaying things even more, because all those new people needed to be trained up, which required time and manpower diverted from game development….

Comment by numy

on 2019-10-05T02:05:17-05:00

Probably 99% of you mass complainers have zero inclining of what it takes to write code for a game this massive. Or to have to go through millions of lines of code to fix bugs after you add more code to it. *snip* Otherwise pick up a key board and learn to fix code yourself.r
I’m a developer myself, and I do feel bad for blizzard’s devs, rage directed at them is totally unjustified; they’re not the ones making the decisions and prioritiesr
you can (and should) direct any rage you feel towards blizzard’s managementr
someone here said hiring more people fixes nothing; but that’s nonsenser
each bug fix will take a set amount of time regardless of how many devs work on it, but more devs = more bugs being looked at at oncer
blizzard could easily reduce the insane profit they make to a huge profit; and employ more and better devsr
but they don’tr
r
BFA is a very frustrating experience when you consider it’s got a huge company behind it; making a ton of profit;r
a small Indy company can get away with multi minute chat lag; 0 communication to addon devs; DCs when players fall to the ground in the wrong way; let alone all the bad bfa design choices (which can never be blamed on devs, it’s not their job)

Comment by Espinas

on 2019-10-05T02:48:36-05:00

When will the arena mount bar progress be fixed?

Comment by EmeraldBlue

on 2019-10-05T02:53:10-05:00

here’s a strange thought: Hire more people.r
r
This is not a solution. More bodies won’t fix anything, especially with the amount of context in a a game engine like this. Your solution coined it – they need more time. It’s just hard to do that with how fast people want things.r
r
very true. they need to start hiring people with actual skill in development and people that can program beyond a community college level. They hire people who “love blizzard” because they know they can pay them half what the rest of the industry pays, and they will lap it up like little puppies drinking mother’s milk.r
r
r
r
Actually, that is not true.r
An interview a few months back revealed that barely anyone of the WoW team plays the game.r
For most it is just a job.r
r
Which may explain why they are so completely out of touch with the game and the playerbase.

Comment by sepiur

on 2019-10-05T03:31:14-05:00

Probably 99% of you mass complainers have zero inclining of what it takes to write code for a game this massive. Or to have to go through millions of lines of code to fix bugs after you add more code to it. *snip* Otherwise pick up a key board and learn to fix code yourself.r
I’m a developer myself, and I do feel bad for blizzard’s devs, rage directed at them is totally unjustified; they’re not the ones making the decisions and prioritiesr
you can (and should) direct any rage you feel towards blizzard’s managementr
someone here said hiring more people fixes nothing; but that’s nonsenser
each bug fix will take a set amount of time regardless of how many devs work on it, but more devs = more bugs being looked at at oncer
blizzard could easily reduce the insane profit they make to a huge profit; and employ more and better devsr
but they don’tr
r
BFA is a very frustrating experience when you consider it’s got a huge company behind it; making a ton of profit;r
a small Indy company can get away with multi minute chat lag; 0 communication to addon devs; DCs when players fall to the ground in the wrong way; let alone all the bad bfa design choices (which can never be blamed on devs, it’s not their job)r
r
As a dev you should also recognize that more people doesn’t mean what you are saying it does like if you really are a dev you should know there’s priorities right? and a visual bug that barely affects gameplay or another that does but it’s rare and really really hard to reproduce is pretty low in the priorities compared to gamebreaking gameplay issues.r
r
As someone in dev I somehow feel you are not as you say you are because your post smells of nonsense or rookie specially when you compare indie devs vs AAA where there’s a dozen bureaucracy and pipeline issues that indie devs just outright don’t have to deal with because the scope of their projects are small in comparison and they can take a lot of personal time to fix X or Y issue and dev more on the moment rather than “let’s work on things that we will release in 5 years down the line while also current content” which is AAA in a nutshell.



Source link