EPTGraviton Beam Bug - Page 3
| Forum Index > SC2 General |
|
GagnarTheUnruly
United States655 Posts
| ||
|
Wiwiweb
France56 Posts
| ||
|
Khalleb
Canada1909 Posts
On September 29 2010 01:30 Wiwiweb wrote: This isn't a bug. This is obviously an advanced technique that will help seperate noobs and pros. Now we'll have to press ESC on stopped phoenixes instead of the game doing it for us like a noobified game. It looks complicated, stupid and without any real purpose but if you don't agree with my opinion that means you're really just a bronze noob. Also since I got the idea of naming it first, we'll call it Wiwiwebing. is the ESC stop the action i mean it will be able to move again, i know about is stop the beam bfr the patch im only 1.1.0 because is wont be that big of a deal if so | ||
|
DeckOneBell
United States526 Posts
| ||
|
HunterX11
United States1048 Posts
On September 29 2010 01:13 SilverPotato wrote: SC2 is still a new game, I challenge any one of you to make a game as large scale as SC2 and not have any bugs or imba the first patch let alone after a 2 month beta. Also, if they did patches every time one little thing went wrong, we'd never be playing SC2 because everyone would be patching to the latest version. Calm down and takes this opportunity to try out some new units. I don't think people are upset that there are bugs so much as that Blizzard clearly is not even doing the most cursory testing. I am capable of starting up a custom game and testing out how a Phoenix or an Ultralisk works. Even without a custom map, I can test the obvious, simple, common, evident, straightforward uses of Phoenix graviton beam and Ultralisk cleave in less than an hour. Yet apparently Blizzard did not even have a single employee spend a single hour testing the most elementary aspects of this patch. I am not talking about crazy unforeseen consequences or complex side-effects, but the simple effects. It is not a "challenge" to test something; any eight-year-old can do it. | ||
|
TheAngelofDeath
United States2033 Posts
| ||
|
BlasiuS
United States2405 Posts
But when your patch introduces a very serious gameplay bug that drastically affects game balance, then it becomes a serious problem. I am severely disappointed in blizzard for this  | ||
|
enCore-
98 Posts
| ||
|
anilusion
Sweden247 Posts
On September 29 2010 02:27 BlasiuS wrote: small bugs aren't that big a deal. For example, your achievement points not displaying properly, or highlighting the incorrect character when you view someone on the ladder. But when your patch introduces a very serious gameplay bug that drastically affects game balance, then it becomes a serious problem. I am severely disappointed in blizzard for this Overreact much? Considering that you still can cancel the channeling manually, I don't see how this is a "very serious gameplay bug that drastically affects game balance". | ||
|
Seide
United States831 Posts
On September 28 2010 20:15 kudlaty_true wrote: Lol, blizzard releasing a bugfix patch, which is generating next bugs. And this is after everybody yell at them for not testing their patches (ultras splash). Seems they not listened. Seriously, how much worktime it requires to test a change on number of scenarios? From someone who works as a software test engineer: It requires a lot of work time. So let me get this straight: Blizzard waits and tests everything b4 patching = blizzard get yelled at for talking too long to patch. Blizzard releases a quick patch and creates a few bugs while fixing old ones = blizzard gets yelled at for trying to act quick. Lose lose situation for Blizzard. Part of the reason the community is often not listened to. You cant keep everybody happy. | ||
|
DeckOneBell
United States526 Posts
On September 29 2010 02:59 anilusion wrote: Overreact much? Considering that you still can cancel the channeling manually, I don't see how this is a "very serious gameplay bug that drastically affects game balance". When you don't auto-drop and you're trying to deal with say, 10 marines with 6 phoenixes, you're going to be in for a lot of pain. Especially since esc cancels all beams, not just the latest one. Phoenixes are essentially useless in larger numbers. But I'm not as down on Blizzard as this poster. | ||
|
spheresword
14 Posts
On September 29 2010 02:59 Seide wrote: It requires a lot of work time. So let me get this straight: Blizzard waits and tests everything b4 patching = blizzard get yelled at for talking too long to patch. Blizzard releases a quick patch and creates a few bugs while fixing old ones = blizzard gets yelled at for trying to act quick. Lose lose situation for Blizzard. Part of the reason the community is often not listened to. You cant keep everybody happy. What they are saying is they want fast, and high quality patches. It's harder, but this community has higher expectations. | ||
|
intergalactic
Canada428 Posts
On September 29 2010 02:59 Seide wrote: Blizzard waits and tests everything b4 patching = blizzard get yelled at for talking too long to patch. Blizzard releases a quick patch and creates a few bugs while fixing old ones = blizzard gets yelled at for trying to act quick. Lose lose situation for Blizzard. Part of the reason the community is often not listened to. You cant keep everybody happy. Yeah, but think about it. How long would it take to test a patch before publishing it? A couple hours, to test all the units and their abilities? Especially when they patch a particular unit, and they don't even test the unit they just patched. It would spare a whole lot of drama, since this has happened at least twice so far. | ||
|
HunterX11
United States1048 Posts
On September 29 2010 02:59 Seide wrote: From someone who works as a software test engineer: It requires a lot of work time. So let me get this straight: Blizzard waits and tests everything b4 patching = blizzard get yelled at for talking too long to patch. Blizzard releases a quick patch and creates a few bugs while fixing old ones = blizzard gets yelled at for trying to act quick. Lose lose situation for Blizzard. Part of the reason the community is often not listened to. You cant keep everybody happy. How much time does it take to test the various conditions under which one might use a graviton beam? This isn't about thorough testing, this is about at least doing a quick once-over. How about Blizzard tests each change in a patch AT LEAST ONCE before releasing it. How many employees do they have? Three? Four? Sure, they might have to hire a fifth, but I think a company like Blizzard can afford the manpower. | ||
|
BlasiuS
United States2405 Posts
On September 29 2010 02:59 anilusion wrote: Overreact much? Considering that you still can cancel the channeling manually, I don't see how this is a "very serious gameplay bug that drastically affects game balance". rofl, you think severe disappointment is an overreaction here? ok | ||
|
DharmaTurtle
United States283 Posts
How on earth did they not find the Ultralisk bug, and did any programmers even spend half an hour playing with the phoenix to make sure it played okay? | ||
|
Seide
United States831 Posts
| ||
|
drooL
United Kingdom2108 Posts
| ||
|
Rolster
United States19 Posts
On September 28 2010 20:38 Elefanto wrote: What's wrong with you Blizzard? You used to be so solid, but fucking nearly _EVERYTHING_ up with sc2. Chatchannels, Lan, Crossrealm Play, Custom Games, Bnet2.0 overall, time by time bug patches and others fails. START WORKING PROPERLY, IF I WOULD DO THIS IN MY JOB, HELL I WOULDN'T HAVE ONE BY NOW IF I WOULD WORK LIKE THIS. Getting really mad about Blizzard after last couple of months. User was warned for this post On a scale from 1 to Chris Brown, how mad are you? | ||
|
TequilaBR
3 Posts
On September 29 2010 03:05 HunterX11 wrote:How much time does it take to test the various conditions under which one might use a graviton beam? This isn't about thorough testing, this is about at least doing a quick once-over. How about Blizzard tests each change in a patch AT LEAST ONCE before releasing it. How many employees do they have? Three? Four? Sure, they might have to hire a fifth, but I think a company like Blizzard can afford the manpower. Or maybe they just tested with 1 ground unit and 1 phoenix, so the gorund unit was lifted after 50 energy without any trouble and they assumed the bug was fixed. With no unit kill you cant notice the new bug. | ||
| ||
