|
United States7166 Posts
On April 23 2010 16:11 Daniri wrote:Show nested quote +On April 23 2010 15:27 Zelniq wrote:On April 23 2010 15:25 littlehearts wrote:This person believes it is an intentional change. click here uh ya what he posted is obviously an intentional change. damnit please think first before posting stuff like this. this exploit is an unintended result from this change, they did not intend people to abuse this to keep increasing larvae count, they just wanted to remove the penalty for canceling larvae What's so obvious about it being intentional that eggs revert to larva? from a programming/logical standpoint it's impossible for it to be an accidental change.
from a programming standpoint it's analogous to unintentionally making breakfast when you tried to just sit in a chair and play some sc2.
|
Also has anyone noticed that the larva count indicator on the select larva icon is wrong?
|
On April 23 2010 16:19 ukshi wrote: Isn't the patch out in EU yet?
Anyone knows?
Scheduled maintance 19CET tonight. I guess it will get patched then.
|
On April 23 2010 14:12 Kevmar wrote: They made this change for a reason. To keep with the spirit behind the change (prevent the issue where canceling a unit leaves you with no larva). I would suggest that all larva gets destroyed unless destroying the larva would leave you with less than 3 larva.
So if you had 3 drones in eggs and you cancel, you have 3 larva for zerglings. If you have 7 drones in eggs and you cancel, you are only left with 3 larva. This removes the ability to generate extra larva for that early pool and still accomplishes the same thing.
I kind of think they made this change to help deal with early rushes. Giving the user the ability to spot the early rush or cheese on its way, cancel the workers and make units. But when the larva dies too, this isn't an option. Early game is where that one or two larva will make the biggest difference.
im fine with it giving back lava to a max of 3... any more than that is insane...
DL'ing patch atm, am afraid of what will happen when i go up against Z's
|
I JUST lost to this, 6 lings in my base before my zealot was out. I'm def not laddering til this is addressed which will probably be soon.
|
I doubt it's a bug. But either way I really hope they'll see it should be changed back!
|
Of course this is a bug, there's no way that they wouldn't consider 12 lings in under two minutes as a good thing. If it was intentional then they would have completely disregarded the early game when making that decision.
|
On April 23 2010 16:22 Zelniq wrote:Show nested quote +On April 23 2010 16:11 Daniri wrote:On April 23 2010 15:27 Zelniq wrote:On April 23 2010 15:25 littlehearts wrote:This person believes it is an intentional change. click here uh ya what he posted is obviously an intentional change. damnit please think first before posting stuff like this. this exploit is an unintended result from this change, they did not intend people to abuse this to keep increasing larvae count, they just wanted to remove the penalty for canceling larvae What's so obvious about it being intentional that eggs revert to larva? from a programming/logical standpoint it's impossible for it to be an accidental change. from a programming standpoint it's analogous to unintentionally making breakfast when you tried to just sit in a chair and play some sc2.
I don't know anything about programming, but from what I've seen from Blizzard, other games and software in general that seems highly unlikely. I recall one WoW patch that made it so if you were a certain race, class and gender and used a certain ability in a certain subzone you would mount a kodo.
|
On April 23 2010 16:28 ShaperofDreams wrote: Of course this is a bug, there's no way that they wouldn't consider 12 lings in under two minutes as a good thing. If it was intentional then they would have completely disregarded the early game when making that decision. There is a good chance this isn't a bug. Its probably the case that blizzard wanted to decrease the amount of punishment that zerg received from canceling units, and bring that more in line with the other races, who can cancel production without a cost. The quick lings was an unintentional consequence of their fix, something they didnt see coming, much like the warp gate pvp.
|
On April 23 2010 16:28 ShaperofDreams wrote: Of course this is a bug, there's no way that they wouldn't consider 12 lings in under two minutes as a good thing. If it was intentional then they would have completely disregarded the early game when making that decision.
It doesn't need to be a bug... but more just a mistake... I doubt it's a programming error but more like just an oversight. Surely if it's that outrageous it will be fixed soon.
|
On April 23 2010 16:24 Ironclown wrote: I JUST lost to this, 6 lings in my base before my zealot was out. I'm def not laddering til this is addressed which will probably be soon.
If it was 6 lings they weren't using this exploit....
|
United States7166 Posts
On April 23 2010 16:24 Ironclown wrote: I JUST lost to this, 6 lings in my base before my zealot was out. I'm def not laddering til this is addressed which will probably be soon. lol 6pool always gave you 6 lings at the same speed. this exploit does not speed up the time of the rush, just the amount of units in it lol. as terrans/protosses have said, just find a build to properly wall off and scout early enough and you can easily defend.
|
On April 23 2010 16:22 Zelniq wrote:Show nested quote +On April 23 2010 16:11 Daniri wrote:On April 23 2010 15:27 Zelniq wrote:On April 23 2010 15:25 littlehearts wrote:This person believes it is an intentional change. click here uh ya what he posted is obviously an intentional change. damnit please think first before posting stuff like this. this exploit is an unintended result from this change, they did not intend people to abuse this to keep increasing larvae count, they just wanted to remove the penalty for canceling larvae What's so obvious about it being intentional that eggs revert to larva? from a programming/logical standpoint it's impossible for it to be an accidental change. from a programming standpoint it's analogous to unintentionally making breakfast when you tried to just sit in a chair and play some sc2. I like this analogy, but I've ended up unintentionally sitting in a chair and playing games all day when I tried to just make breakfast.
On April 23 2010 16:31 Daniri wrote: I don't know anything about programming, but from what I've seen from Blizzard, other games and software in general that seems highly unlikely. I recall one WoW patch that made it so if you were a certain race, class and gender and used a certain ability in a certain subzone you would mount a kodo. Was this ability named "Mount Kodo"?
|
On April 23 2010 16:40 Funchucks wrote:Show nested quote +On April 23 2010 16:22 Zelniq wrote:On April 23 2010 16:11 Daniri wrote:On April 23 2010 15:27 Zelniq wrote:On April 23 2010 15:25 littlehearts wrote:This person believes it is an intentional change. click here uh ya what he posted is obviously an intentional change. damnit please think first before posting stuff like this. this exploit is an unintended result from this change, they did not intend people to abuse this to keep increasing larvae count, they just wanted to remove the penalty for canceling larvae What's so obvious about it being intentional that eggs revert to larva? from a programming/logical standpoint it's impossible for it to be an accidental change. from a programming standpoint it's analogous to unintentionally making breakfast when you tried to just sit in a chair and play some sc2. I like this analogy, but I've ended up unintentionally sitting in a chair and playing games all day when I tried to just make breakfast. Show nested quote +On April 23 2010 16:31 Daniri wrote: I don't know anything about programming, but from what I've seen from Blizzard, other games and software in general that seems highly unlikely. I recall one WoW patch that made it so if you were a certain race, class and gender and used a certain ability in a certain subzone you would mount a kodo. Was this ability named "Mount Kodo"?
Every bug has an explanation and that's one of the easier ones to explain.
|
On April 23 2010 16:40 Funchucks wrote:Show nested quote +On April 23 2010 16:22 Zelniq wrote:On April 23 2010 16:11 Daniri wrote:On April 23 2010 15:27 Zelniq wrote:On April 23 2010 15:25 littlehearts wrote:This person believes it is an intentional change. click here uh ya what he posted is obviously an intentional change. damnit please think first before posting stuff like this. this exploit is an unintended result from this change, they did not intend people to abuse this to keep increasing larvae count, they just wanted to remove the penalty for canceling larvae What's so obvious about it being intentional that eggs revert to larva? from a programming/logical standpoint it's impossible for it to be an accidental change. from a programming standpoint it's analogous to unintentionally making breakfast when you tried to just sit in a chair and play some sc2. I like this analogy, but I've ended up unintentionally sitting in a chair and playing games all day when I tried to just make breakfast. Show nested quote +On April 23 2010 16:31 Daniri wrote: I don't know anything about programming, but from what I've seen from Blizzard, other games and software in general that seems highly unlikely. I recall one WoW patch that made it so if you were a certain race, class and gender and used a certain ability in a certain subzone you would mount a kodo. Was this ability named "Mount Kodo"? ROFL. Epic post :D
|
THE BUG IS THAT THE HATCH KEEPS MAKING LARVA WHILE YOU HAVE EGGS! and yes im shouting, the cancel and keep your larva thing is definitely intentional, the fact that you can get 5 larva before the pool finishes and gg anything but a terran wall in (with repairing scv's) is definatly a bug, Even if toss walls with forge pylon gate you can kill the pylon and forge and they cant stop it. I tested it out and watched orb do it several times and it's unstoppable. Especially if the z votes down all the 4 player and large rush distance maps. The 10 lings get to toss's base before the 1st zeolot is out! There is nothing they can do, youll kill almost all probes, even with chronoing zlots, If they do manage to survive their income is crippled, theyve lost there first 2 or 3 lots a pylon,a forge and are screwd if you expo and macro or go muta cuz they have no forge to make cannons,no cyber to make stalkers and no pylons at there minerals for cannons even if they did rebuild forge,have another 100 for a pylon and 150 for a cannon. It's definitely a huge oversight!
|
Just played against it and it's definitely stoppable.
However, you absolutely need to scout this coming and build a very good wall. Hold the wall with 1 zealot (chronoboosted) and have a forge before core and build a cannon. Pull probes if your zealot is in danger of falling.
You will be behind a regular build due to a delayed core but the Zerg will be somewhat behind as well (esp. if they did a fast pool).
|
On April 23 2010 17:02 Reborn8u wrote: THE BUG IS THAT THE HATCH KEEPS MAKING LARVA WHILE YOU HAVE EGGS! That's not new, though. You couldn't just change that alone. It would change zerg's whole production schedule.
The new thing is that eggs are recoverable for use as larvae. They can do the easy thing and change that back, or the hard thing and rebalance zerg production from the ground up.
|
On April 23 2010 17:10 Ryuu314 wrote: Just played against it and it's definitely stoppable.
However, you absolutely need to scout this coming and build a very good wall. Hold the wall with 1 zealot (chronoboosted) and have a forge before core and build a cannon. Pull probes if your zealot is in danger of falling.
You will be behind a regular build due to a delayed core but the Zerg will be somewhat behind as well (esp. if they did a fast pool). you stopped 10 lings with 1 zealot?
could you post replay?
|
haha this is so sick, how could they miss it? If they did in fact miss it, but thats just being cynical since this was a fing huge patch. Too bad it was such a game breaker
|
|
|
|