|
For whatever reason players have named a Terran one-base all-in vs. Protoss the 1/1/1 build, because it often opens with rax to fax to port.
This is 90% of Terran tech builds. If you open cloaked Banshee, you did 1/1/1. If you open reactored hellions, you did 1/1/1. Almost all TvTs open with a 1/1/1.
What Protosses are having so much trouble with is a one-base all-in involving a variety of Terran units. Sometimes there's a Raven, sometimes cloaked Banshees. Sometimes Thors, sometimes Tanks. Sometimes 2 rax are built before the factory. Sometimes the Starport is omitted entirely. Sometimes stim is researched, often not. Sometimes SCVs are pulled, sometimes for auto-repair, sometimes for extra attackers.
This should simply be called a one-base all-in. 1/1/1 is too vague, inaccurate and really means something totally different.
|
Reactor hellion is not 1/1/1
|
Or what about the "all-in fist"?
|
Does it really bother you that much? Why cant we call a build using a barracks, a factory, and a starport 1/1/1? If they do a different variation without a starport, dont call it 1/1/1...
|
The terran all in that protoss is having trouble with right now is a 1/1/1 build, not a 2 rax, not stim, not thors, which are not 1/1/1 builds...
|
Cuba122 Posts
one-base all-in is FAR vaguer imo. also, the build afaik is called the "1/1/1 ALL-IN" as opposed to any other old 1/1/1
offtopic but wasn't 1/1/1 called Destiny Cloud Fist build for awhile? xD
|
On September 08 2011 11:09 slicknav wrote:
The terran all in that protoss is having trouble with right now is a 1/1/1 build, not a 2 rax, not stim, not thors, which are not 1/1/1 builds...
...is A 1/1/1 build. One that is a one base all-in. There are MANY 1/1/1 builds that have nothing to do with the Protoss all-in.
On September 08 2011 11:09 Atila wrote:
offtopic but wasn't 1/1/1 called Destiny Cloud Fist build for awhile? xD
Husky calls it that because he found 1/1/1 too unexciting.
|
cool story bro
User was temp banned for this post.
|
cloaked banshee is cloaked banshee
nobody calls it 1/1/1
why is this concept for hard for you to understand?
|
Hyrule19178 Posts
2 rax before factory is not 1/1/1
reactor hellions is not 1/1/1
fast thors is not 1/1/1
omitting a starport is not 1/1/1
1/1/1 is very specific: you get up 1 of each manufacturing building before expanding or producing an army. After that point the build transitions into something else.
|
Let's call it the Destiny Cloudfist build, in honor of the inventor of this build, Husky. Without his strategic brilliance we never would've developed this amazing build that many koreans even regard as imbalanced, so it's only fair we call it that.
|
On September 08 2011 11:10 pbjsandwich wrote:
cloaked banshee is cloaked banshee
nobody calls it 1/1/1
why is this concept for hard for you to understand?
Because cloaked Banshee is a 1/1/1 build. It has as much of a claim to the name as the TvP all-in.
|
yeah, really liked this story.
|
On September 08 2011 11:09 _Search_ wrote:Show nested quote +On September 08 2011 11:09 slicknav wrote:
The terran all in that protoss is having trouble with right now is a 1/1/1 build, not a 2 rax, not stim, not thors, which are not 1/1/1 builds... ...is A 1/1/1 build. One that is a one base all-in. There are MANY 1/1/1 builds that have nothing to do with the Protoss all-in. Show nested quote +On September 08 2011 11:09 Atila wrote:
offtopic but wasn't 1/1/1 called Destiny Cloud Fist build for awhile? xD Husky calls it that because he found 1/1/1 too unexciting.
No, the 1/1/1 is the name of a specific build given by the community. Any other builds that open rax/fact/port are just builds that open rax/fact/port with their own names that aren't 1/1/1.
|
Duly noted. I'll come to you whenever I need a trivial argument concerning semantics.
Bonjwa, I can understand there being a reason to dispute its use, but for the 1/1/1? This is getting a tad ridiculous (assuming this isn't an outright troll).
|
One base all in is not vague at all lol
|
I think it's up to the casters to work on it properly. The 1/1/1 is an "opening", however it comes out with a large variety of actual build orders.
At the very least, I think it's Doa that's trying to do it, but when the infamous TvP 1/1/1 comes out he's trying to call it the marine/tank/banshee all-in, which is what it really is. I mean, for example I once saw LR explode into 1/1/1 when a terran did a marine tank medivac push whilst expanding behind it. It would be like shouting "x gate all-in!" every time a protoss attacks, ignoring tech, expansions and the fact that it's not even an all-in.
Anyway, as I said, the onus is on the casters to properly inform the viewers to the builds. The reason 'everyone' calls the "1/1/1" the "1/1/1" is because the casters started and continued it, regardless of variations.
|
On September 08 2011 11:09 _Search_ wrote:Show nested quote +On September 08 2011 11:09 slicknav wrote:
The terran all in that protoss is having trouble with right now is a 1/1/1 build, not a 2 rax, not stim, not thors, which are not 1/1/1 builds... ...is A 1/1/1 build. One that is a one base all-in. There are MANY 1/1/1 builds that have nothing to do with the Protoss all-in.
This is true. But in its current state, when referring the 1/1/1 build against protoss, it is generally known that the build under discussion is the all in build. That's just the way it is, you just have to accept it.
|
Calgary25990 Posts
I agree but it isn't appropriate for you to push yout agenda via a tl thread.
|
|
|
|
|
|
EPT
