|
It is Tuesday on EU, the patch has been applied and the bug is still present.
Why am I not surprised.
|
On June 14 2016 15:15 Cascade wrote:Show nested quote +On June 14 2016 13:49 ZigguratOfUr wrote:On June 14 2016 13:36 Cascade wrote:On June 14 2016 07:56 ZigguratOfUr wrote:On June 14 2016 07:53 PinoKotsBeer wrote:
Took them 2 weeks, i assume the entire overwatch and world of warcraft team helped as well to fix it this complicated bug. Or they took 15 seconds to fix the bug, and then waited for the next patch. Or people on this forum are very naive about the effort required to fix bugs. Having briefly worked in the industry, I'm perfectly willing to believe that fixing this particular bug involved little more than changing a few numbers, and took almost no time at all. Scheduling a patch has significantly more overhead since you need approval from management, need to schedule downtime if needed etc, so doing a patch for a single bug isn't worth it unless the bug is really severe. It can also be a much deeper issue that needed a fair amount of work and testing. Judging from how fast it was done, probably not too deep though. People seem to think that "fixing" things in sc2 is super easy. "Common blizzard, fix protoss". "Fix e-sports". "fix WCS". "Fix mech". "Fix this bug". As if it could be done in half an hour, but they choose not to do it. I don't know the details of this bug, but I get a bit worked up by everyone assuming it is trivial to "fix" everything, when they actually don't have a clue about what is actually needed. actually tweaking a number and changing the reference for the button wouldn't take longer then an hour for someone experienced in the editor. Maybe even 10 minutes if you know what you're looking for. Then you just need to test it in-game if it works and that's it.
Obviously "fixing protoss" or other things would require much more testing and brainstorming (and will) then fixing a simple bug.
but changing a stat is simple.
|
Will they fix the bug where the Cyclone isn't the Goliath?
hue
|
I wonder if I will see them in my games ?! would be fun to see a new unit after 6 months
|
I think the community has been pretty chill about the cyclone bug. It's a big, big, big mistake... makes me wonder how they test the game.
|
With the fix, we might be able to put much more pressure with Cyclones.
|
On June 14 2016 17:45 Nazara wrote:Show nested quote +On June 14 2016 15:15 Cascade wrote:On June 14 2016 13:49 ZigguratOfUr wrote:On June 14 2016 13:36 Cascade wrote:On June 14 2016 07:56 ZigguratOfUr wrote:On June 14 2016 07:53 PinoKotsBeer wrote:
Took them 2 weeks, i assume the entire overwatch and world of warcraft team helped as well to fix it this complicated bug. Or they took 15 seconds to fix the bug, and then waited for the next patch. Or people on this forum are very naive about the effort required to fix bugs. Having briefly worked in the industry, I'm perfectly willing to believe that fixing this particular bug involved little more than changing a few numbers, and took almost no time at all. Scheduling a patch has significantly more overhead since you need approval from management, need to schedule downtime if needed etc, so doing a patch for a single bug isn't worth it unless the bug is really severe. It can also be a much deeper issue that needed a fair amount of work and testing. Judging from how fast it was done, probably not too deep though. People seem to think that "fixing" things in sc2 is super easy. "Common blizzard, fix protoss". "Fix e-sports". "fix WCS". "Fix mech". "Fix this bug". As if it could be done in half an hour, but they choose not to do it. I don't know the details of this bug, but I get a bit worked up by everyone assuming it is trivial to "fix" everything, when they actually don't have a clue about what is actually needed. actually tweaking a number and changing the reference for the button wouldn't take longer then an hour for someone experienced in the editor. Maybe even 10 minutes if you know what you're looking for. Then you just need to test it in-game if it works and that's it. Obviously "fixing protoss" or other things would require much more testing and brainstorming (and will) then fixing a simple bug. but changing a stat is simple.
How do you know that's all that has to be done though? How do you know it's not a symptom of some deeper issue? If it indeed is just a parameter that the cat changed, then yes, they only thing you have to do is to change a single character and it "should" work. I'm not saying it necessarily is more complicated, just that we can't be annoyed that it took them two weeks to fix when we don't know what the problem was.
|
On June 14 2016 15:39 MockHamill wrote:
It is Tuesday on EU, the patch has been applied and the bug is still present.
Why am I not surprised.
Because the patch didnt happen yet, Europe gets the patch wednesday morning as always.
|
On June 14 2016 22:49 Cascade wrote:Show nested quote +On June 14 2016 17:45 Nazara wrote:On June 14 2016 15:15 Cascade wrote:On June 14 2016 13:49 ZigguratOfUr wrote:On June 14 2016 13:36 Cascade wrote:On June 14 2016 07:56 ZigguratOfUr wrote:On June 14 2016 07:53 PinoKotsBeer wrote:
Took them 2 weeks, i assume the entire overwatch and world of warcraft team helped as well to fix it this complicated bug. Or they took 15 seconds to fix the bug, and then waited for the next patch. Or people on this forum are very naive about the effort required to fix bugs. Having briefly worked in the industry, I'm perfectly willing to believe that fixing this particular bug involved little more than changing a few numbers, and took almost no time at all. Scheduling a patch has significantly more overhead since you need approval from management, need to schedule downtime if needed etc, so doing a patch for a single bug isn't worth it unless the bug is really severe. It can also be a much deeper issue that needed a fair amount of work and testing. Judging from how fast it was done, probably not too deep though. People seem to think that "fixing" things in sc2 is super easy. "Common blizzard, fix protoss". "Fix e-sports". "fix WCS". "Fix mech". "Fix this bug". As if it could be done in half an hour, but they choose not to do it. I don't know the details of this bug, but I get a bit worked up by everyone assuming it is trivial to "fix" everything, when they actually don't have a clue about what is actually needed. actually tweaking a number and changing the reference for the button wouldn't take longer then an hour for someone experienced in the editor. Maybe even 10 minutes if you know what you're looking for. Then you just need to test it in-game if it works and that's it. Obviously "fixing protoss" or other things would require much more testing and brainstorming (and will) then fixing a simple bug. but changing a stat is simple. How do you know that's all that has to be done though? How do you know it's not a symptom of some deeper issue? If it indeed is just a parameter that the cat changed, then yes, they only thing you have to do is to change a single character and it "should" work. I'm not saying it necessarily is more complicated, just that we can't be annoyed that it took them two weeks to fix when we don't know what the problem was.
Because the guy who reported the bug looked it up in the editor and saw the error there. Having worked with the editor myself, I would be very very surprised to hear this took longer than 30 minutes.
|
On June 14 2016 22:49 Cascade wrote:Show nested quote +On June 14 2016 17:45 Nazara wrote:On June 14 2016 15:15 Cascade wrote:On June 14 2016 13:49 ZigguratOfUr wrote:On June 14 2016 13:36 Cascade wrote:On June 14 2016 07:56 ZigguratOfUr wrote:On June 14 2016 07:53 PinoKotsBeer wrote:
Took them 2 weeks, i assume the entire overwatch and world of warcraft team helped as well to fix it this complicated bug. Or they took 15 seconds to fix the bug, and then waited for the next patch. Or people on this forum are very naive about the effort required to fix bugs. Having briefly worked in the industry, I'm perfectly willing to believe that fixing this particular bug involved little more than changing a few numbers, and took almost no time at all. Scheduling a patch has significantly more overhead since you need approval from management, need to schedule downtime if needed etc, so doing a patch for a single bug isn't worth it unless the bug is really severe. It can also be a much deeper issue that needed a fair amount of work and testing. Judging from how fast it was done, probably not too deep though. People seem to think that "fixing" things in sc2 is super easy. "Common blizzard, fix protoss". "Fix e-sports". "fix WCS". "Fix mech". "Fix this bug". As if it could be done in half an hour, but they choose not to do it. I don't know the details of this bug, but I get a bit worked up by everyone assuming it is trivial to "fix" everything, when they actually don't have a clue about what is actually needed. actually tweaking a number and changing the reference for the button wouldn't take longer then an hour for someone experienced in the editor. Maybe even 10 minutes if you know what you're looking for. Then you just need to test it in-game if it works and that's it. Obviously "fixing protoss" or other things would require much more testing and brainstorming (and will) then fixing a simple bug. but changing a stat is simple. How do you know that's all that has to be done though? How do you know it's not a symptom of some deeper issue? If it indeed is just a parameter that the cat changed, then yes, they only thing you have to do is to change a single character and it "should" work. I'm not saying it necessarily is more complicated, just that we can't be annoyed that it took them two weeks to fix when we don't know what the problem was.
Stop pretending. Everybody who did at least some data editing knows, that this particular bug doesn't take longer than 10 minutes to fix.
|
The patch has been applied to EU.
We got new emotes but no cyclone fix.
Guess the Cyclone fix will be included in the Christmas update.
|
Great job blizzard, i dont know how i feel about how long it took to fix this in the first place though
|
Calm your tits people. The fix is live in the US.
|
Why not in EU? We are 9 hours ahead so the patch should be here first.
|
On June 15 2016 03:50 MockHamill wrote:
Why not in EU? We are 9 hours ahead so the patch should be here first.
How exactly do timezones affect when the people at Blizzard decide to deploy the patch to your server?
|
On June 15 2016 03:50 MockHamill wrote:
Why not in EU? We are 9 hours ahead so the patch should be here first.
We didn't even have server maintenance yet so I have no idea why you're surprised about anything. EU never gets patches before NA.
|
The cooldown has been fixed on NA, but the bug where it fails to autocast and decides to move to 5 range and plink away with its main weapon is still present. It would be nice to have a change log.
|
On June 15 2016 00:17 RoomOfMush wrote:Show nested quote +On June 14 2016 22:49 Cascade wrote:On June 14 2016 17:45 Nazara wrote:On June 14 2016 15:15 Cascade wrote:On June 14 2016 13:49 ZigguratOfUr wrote:On June 14 2016 13:36 Cascade wrote:On June 14 2016 07:56 ZigguratOfUr wrote:On June 14 2016 07:53 PinoKotsBeer wrote:
Took them 2 weeks, i assume the entire overwatch and world of warcraft team helped as well to fix it this complicated bug. Or they took 15 seconds to fix the bug, and then waited for the next patch. Or people on this forum are very naive about the effort required to fix bugs. Having briefly worked in the industry, I'm perfectly willing to believe that fixing this particular bug involved little more than changing a few numbers, and took almost no time at all. Scheduling a patch has significantly more overhead since you need approval from management, need to schedule downtime if needed etc, so doing a patch for a single bug isn't worth it unless the bug is really severe. It can also be a much deeper issue that needed a fair amount of work and testing. Judging from how fast it was done, probably not too deep though. People seem to think that "fixing" things in sc2 is super easy. "Common blizzard, fix protoss". "Fix e-sports". "fix WCS". "Fix mech". "Fix this bug". As if it could be done in half an hour, but they choose not to do it. I don't know the details of this bug, but I get a bit worked up by everyone assuming it is trivial to "fix" everything, when they actually don't have a clue about what is actually needed. actually tweaking a number and changing the reference for the button wouldn't take longer then an hour for someone experienced in the editor. Maybe even 10 minutes if you know what you're looking for. Then you just need to test it in-game if it works and that's it. Obviously "fixing protoss" or other things would require much more testing and brainstorming (and will) then fixing a simple bug. but changing a stat is simple. How do you know that's all that has to be done though? How do you know it's not a symptom of some deeper issue? If it indeed is just a parameter that the cat changed, then yes, they only thing you have to do is to change a single character and it "should" work. I'm not saying it necessarily is more complicated, just that we can't be annoyed that it took them two weeks to fix when we don't know what the problem was. Because the guy who reported the bug looked it up in the editor and saw the error there. Having worked with the editor myself, I would be very very surprised to hear this took longer than 30 minutes.
Oh, he actually found the bug? I thought he just patched on top of it, but I didn't read in detail and haven't worked in the editor myself. Thanks.
|
They should also fix the bug where it has only 30 hp per supply.
|
can anyone confirm if auto-cast range is still broken? last time I checked, cyclones could manually lock-on from 7 range, while you had to move within 5 range in order to lock-on with auto-cast.
|
|
|
|
|
|
EPT
