So, JangBi against NaDa. Should be an obvious favourite here. JangBi is a monster right now and his PvT is his best matchup. I know I was critical of him last week when I described his victory over his teammate FrOzean as plain... and it was... extremely so.... but JangBi is still JangBi. When it's PvT he's a favourite over any Terran and NaDa isn't top level anymore.

---

I like 2 gate goon openings on Byzantium. While the rush distances are long so a quick victory isn't likely they give the Protoss dominance over the Terran, stopping him from playing a FE into macro game like they'd like and instead making them work for the ramp. High nats favour P imo. We've seen this before and we've seen NaDa transition very easily into highly effective drop play. But JangBi has proven himself uniquely competent at dealing with that kind of play. It's not the special tricks that mark JangBi out, rather it's his flawless solidity at the basics that make him unique as a player. His pylons will be spread around his main scouting drops early. He won't take a stupid risk or misread his opponent. Fancy vulture play will not catch him off guard. And that's why this opening is good here, not because it's imbalanced or Protoss favoured but simply because it plays perfectly into JangBi's hands. It limits the options of the Terran and forces them to play in a way which will lead to JangBi winning.

His micro in the first fight could have been better. You could see what he was trying to do and if NaDa had been moving or in any way flanked then it would have been effective. But NaDa knew what he was doing and his defensive micro against tank sniping attempts was perfect. JangBi expected NaDa to follow with a quick expansion covered by mines, as indeed he did, and therefore went semi-allin with a robo/reaver himself. I say semi-allin because it didn't have to kill NaDa, just do a lot of damage or kill the expansion. Letting T finish their exp before P even starts theirs is risky but JangBi knew what NaDa had and hoped he could kill it rather than play out the macro war. He denied NaDa's scouting with a cute goon wall near his nat so NaDa didn't know he was doing this and then started his own expansion so that, as long as some damage was done, he wouldn't be too behind.

NaDa's defence was impeccable. Not a single weak point in his defence. Reavers were unable to land close enough to get a shot at the tanks, nor enter NaDa's main to try and spread out his defence and get a shot at scvs. NaDa would have been severely behind if JangBi had double expanded in that time (although he had a vulture at 3 which didn't see any kind of expansion attempt so he could be reasonably sure JangBi wasn't) but JangBi didn't. NaDa's read was spot on and his defence was faultless. It reached that point that JangBi knew he had to attack because he knew he was allin but after checking out NaDa's defence decided it wasn't worth it and that it was better to accept the minute chance that he could pull back the mid game through some epic mistake by NaDa than go through with his original plan.

JangBi double expands because although he can't hold them he also can't hold up NaDa's army without the money they provide. Then, desperate to validate my high opinion of him, he shuts down a vulture drop in his main with the loss of just 2 probes and another vult raid at 3 with his ever reliable walls. I'd like to clarify here that I haven't seen these games, I'm writing this as I watch, JangBi really is that predictable.

NaDa uses his defensive unit advantage to expand all over his corner, defended by a big mass of tanks, high ground and turrets. I'm not sure whether I like this or not. If there's anybody I'd trust to dismantle a tornado then it's JangBi and they are cross positions so pushing is hard. Equally if there's anyone I'd trust to abuse arbiters to the absolute limit and recover a big deficit late game it's JangBi. So I don't know exactly how NaDa should be exploiting his opponent here, maybe just sitting back, expanding and double grading is the best option.

JangBi casually ups it to 11 gates, 2 stargates and a fuckload of scary Protoss units in classic JangBi late game style. The arbiters are late because he's opted for storm, speedlots and all sorts of other midgame dominance units but I don't know if I can fault that or not. His dilemma is that if he had rushed to arbs then he couldn't have held the expansions he needs to win against a midgame push. However he needs the arbs to deal with NaDa's 200/200 3-3 lategame. I guess this kind of catch 22 is the cost of a big early game disadvantage, I can't argue that he's made a mistake since then, I can point out NaDa didn't attack so he should have expanded and rushed arbs but we don't know if NaDa would have done the same in that situation.

JangBi's counterattack at 6 was the only move he could do. He correctly judged that he didn't have the stasis to take NaDa on head on but he had to slow the push. It cost him a lot of units but he had the gates to replace those. It didn't buy him enough time though, his stasis were less than perfect and he repeatedly fell victim to EMP. NaDa knocked out his two expansions near 12 and took the game.

GG

Perhaps JangBi would have been better off taking no risks in an early game build which simply had to work. NaDa is certainly an experienced player with finely attuned game senses and despite JangBi denying him scouting he hard countered the fuck out of that goon/reaver/ob rush. He took a risk and it turned out NaDa is just that good. Not sure though. It's impossible to play while taking no risks. Draw your own conclusions about whether he should have gone for the execution of NaDa's FE (which is also safe against 2 facts) or double expanded himself with a late robo.

---

Game 2 JangBi opened with an unusual (for him) rush. One well hidden proxy gate with a gas steal and probes pumping as normal (after the initial delay). While NaDa reacted with a bunker the zealots killed several marines and scvs and delayed the gas and factory, as well as messing with mining a bit. NaDa was perhaps too cautious, but given the number of Terrans losing to proxy 99 and the lack of scouting information he had no way of knowing that JangBi's opening was just offensive, rather than actually allin. His scv scouted nothing in JangBi's main so he had no way of knowing whether it was one gate or two and, if I'm judging the minimap correctly, JangBi actually sent 2 probes after it to kill it which NaDa didn't notice while microing marines. In the mean time JangBi was expanding and following up with a quick core and second gate. Amusingly enough NaDa actually prisoned his factory leaving his first tank very vulnerable but JangBi didn't notice.

JangBi's 2 gate faced off against NaDa's 2 fact, 4 dragoons and 3 zealots against 3 tanks, 3 vultures and 6 marines. But NaDa hadn't even started his expansion whereas JangBi's economy was surging ahead off 2 bases. In trying to stay safe against a fake allin from JangBi NaDa had in fact forced himself allin with no expansion, nor any hope of recovering the game if he waited to take one. He was forced to attempt a tornado into a wide concave position without any entrenched support (turrets, mines, other sieged tanks). The result was extremely predictable and very painful for any terrans watching it. JangBi got obs out and flattened it with barely a loss.

GG

This was a very smooth game by JangBi. His build looked very scary, especially given the number of proxy 99s we've seen so far in the MSL, and NaDa wasn't a bad player to overreact to it. But he overcompensated to the extent that he was allin in a position where he simply couldn't execute an effective allin build. I liked it, he just took control and dominated the game from start to finish. Oddly enough the pivotal moment in this game was given no attention by the observer. If you watch NaDa's scout scv on the minimap it leaves JangBi's base, scouts for proxies and then returns whereupon 2 white dots approach it. Then JangBi's expansion probe is clicked and has 1 kill. NaDa didn't know JangBi was expanding and macroing up because he let his scv die (while saving himself from zealots). That decided the game.

---

So, game 3 on Neo Harmony. JangBi at 7, NaDa at 11. We've seen JangBi take firm control of the game flow early on in the first 2 games and I must admit I like it. This is rather more assertive than his normal play style and if he keeps it up I might actually become a fan (instead of just sullenly admitting he isn't bad). JangBi scouted on 8 and scouted correctly which made life much harder for NaDa who had to deal with a very annoying harassing probe. A second probe scouted the middle for proxies (as well as being seen by NaDa's scv) and then went to 12 to hide. JangBi made a fast zealot, I assume hoping to wall the ramp before the scv arrived to notice minerals were missing but it was too late and promptly went to chase the scv.

The inevitable proxy robo at 12 was placed down and I have to admit I like this new JangBi with his aggressive dominant game style. That said I'd question how appropriate it is when NaDa scouted your second probe heading out early (I'm not sure whether NaDa actually noticed but you can't rely on that crap) and noticed that your main is missing a 2nd gate, any tech and an expansion. NaDa knew what JangBi wasn't doing and should really have known there was a proxy going down at 12.

NaDa's fast expanded, defended by tanks and mines off 1 factory. What happened next was simply rape. I don't know wtf NaDa was thinking. Any half decent player knows to turn the tank away as the reaver fires to take half damage and not to clump their units against reavers. Instead the first scarab shot killed 2 marines and left a tank dead as a dragoon finished it off seconds later. The second one almost finished a second tank while the dragoon killed a vult, forcing NaDa to back his army off and just let JangBi have a party in his main. Eventually NaDa got some units together and took back his main min line only to have a group of dragoons trash up his natural. With the first reaver still alive the addition of a second made NaDa's position untenable and he surrendered the game to a proxy reaver rush that he really had to know was coming.

GG

NaDa was inexcusable this game. Scouting the second probe heading to 12 should have tipped him off. Scouting the lack of tech or a 2nd gate or an expansion limited JangBi's range to proxy dark rush with tech hide or proxy robo. While he did eventually send a vulture to 12 it was intercepted by a dragoon also going there and backed off. Why was a dragoon going to 12 NaDa?!?! Why would JangBi do that?!?! What could there be at 12 that would require the use of just one dragoon?!?! Jesus. A C rank terran should be ashamed at not covering half his main with mines.

---

So, that's three games in three that JangBi has taken by the balls and forced his game plan upon. Admittedly one of them NaDa saw through him and shut him down completely (and not the one where NaDa actually saw what he was doing three different times) but whatever, I'm liking it. JangBi spawned at 11 and NaDa at 5. JangBi scouted on 8 and NaDa sent out a scv on 8 to commit petty animal cruelty at 3. Using another scv to hold the wall at his ramp and prevent JangBi's scout probe getting in he successfully kept his proxy factory at 3 hidden. JangBi opted for a soft contain while expanding and then realised that somehow NaDa hadn't got any mech nits anywhere near his ramp and broke in for some ownage. He successfully took NaDa's ramp but then realised something was up and that it wasn't worth trying to break in. NaDa had gone 2 fact at 3 and his fast expansion off 1 gate was incredibly vulnerable. Credit where it's due, JangBi brought his army back immediately, before NaDa's rush even hit. He microed well against the mines and sniped the tanks quickly. However 2 fact double graded vults against 1 gate goons without obs is just not going to happen. Ever. NaDa sacrificed his tanks for the ramp and once he was in there was no way JangBi was going to be able to micro well enough to stop his gates from being mined up. His unit production was shut down by mines and then vults smashed his min line.

GG

That said, JangBi could have stayed in this (and possibly come out ahead) with a single simple trick. One that to be honest it is inexcusable that he didn't use. Sure it would have required some incredibly sexy on the spot thinking but he's a top level progamer, I expect that. He sold his nexus for 300 minerals, that's enough to wall the ramp with pylons. Doing so stops the vults from getting to the gates and allows the 2 dragoons he already has out to stop the pylons being attacked. It's the mines that make speedvults dangerous against goons, a wall makes them impotent. There are no two ways about it, JangBi knew what he was up against, he had the money, he had the probes nearby, he had the time. What he lacked was the inspiration. I really would have loved it if he had. I'd have loved the look on NaDa's face. The "Oh.... I didn't think of that.... That was actually quite good.... I might be fucked here." But it wasn't to be.

---

So, JangBi, we're down to game 5. Game 4, the one game you don't do an aggressive dominant game, NaDa does and he takes it from you. And now we're back where we started, a game on Byzantium, this time for the series.

JangBi spawns at 7 and NaDa at 11. Close positions with NaDa's main exposed to JangBi, perfect for JangBi to go into drop play and very poor for NaDa. JangBi scouts correctly again while NaDa scouts the wrong way, as in game 3. He opens zealot first and then attacks with zeeprobe off 1 gate while getting a goon and a second gate. We've seen this build before from JangBi earlier in the tournament and it absolutely raped, excellent micro humiliating Iris. However it seems that NaDa has been keeping up with the MSL and refused to fight, backing off his marines and waiting until he had a stronger count to fight. NaDa pushed out to take his nat with 5 marines and a tank and JangBi moved in with 3 dragoons and a zealot. The inevitable tank snipe attempt happened, and it almost worked, bringing the tank within 2 hits of death. However it backed off to safety and faced with the risk of losing goons as in game 1 JangBi was forced to back off. A vulture with mines arrived to secure the area and NaDa took his expansion. JangBi, unwilling to let his rush fail, outmicroed a mine and started sniping the barracks, more out of spite than of any real attempt to break through. In the mean time he expanded, unwilling to repeat the risks of the first game and confident he could take it from NaDa in a macrowar.

NaDa looked physically shocked when his barracks died but started a new one slightly further back to maintain the wall. However the wall was broken and JangBi was out for blood, sacrificing a dragoon to clear a mine and moving in to harass NaDa. This was not an attempt to win, there was no way he could outmicro all the mines and he knew it. This was psychological warfare, pointless attacks to throw NaDa off his comfortable footing while keeping him blind. A scv, a vulture, 2 more mines and the building barracks all died before siege forced JangBi back. He hadn't lost a goon, but the one he had suicided. NaDa was still on one factory and more importantly, JangBi knew he was. That kind of scouting information doesn't normally come until obs are out but killing their barracks twice does the trick. JangBi swiftly took his third off just 1 gateway while grabbing a reaver and staying safe with a wall against any kind of proxy play a la game 4.

As in game 1, NaDa made a dozen turrets all round his perimeter and left enough sieged tanks about to make any reaver play impossible. However unlike in game 1, JangBi was already on 3 base with 3 gas and was doing his JangBi thing. And he's good at that. His reaver harass was more threat based than intending to do any damage and JangBi took no risks with the reaver itself, the loss of a single zealot was negligible.

I think NaDa realised he was behind because whereas in game 1 he camped mass tanks on a single corner, taking 4 base before becoming aggressive, in game 5 he went to 6 fact very early with mass tank and goliath forcing a path to his 3rd. The depth of his tank formation was physically scary as a protoss player but JangBi was taking over the map while buying time. Not interested in killing NaDa's expansion he just took another two of his own while flying a pair of speedshuttles in to set shit of fire in NaDa's main. This wasn't an attack, it was just arson. It was sabotage. Even though it didn't kill any scvs (scarab bugged on them as they slid out) it killed a few tanks, stopped mining for a long time and generally fucked shit up. This is actually described in Legs guide, just annoying the Terran with drop play and threat while you do your taking over the map thing. Words cannot describe how bad JangBi's scarabs are. A total of 7 scarabs, fired directly at scvs from point blank range killed 2 scvs. A bad thing can only continue for so long though and eventually his luck turned and he killed a dozen or so. Realising he'd maxed out and still had a ridiculous amount of money he decided to keep up the theme and went in for some terrorism. With some speedlots drawing fire a group of stormers threw storms all over NaDa's army as it sat in his 3rd base. JangBi wasn't willing to attack NaDa's tanks head on but he was more than content to set fire to shit and storm all over stuff. In the mean time he did what all protoss players do when the terran has too many tanks for you to be legitimately expected to attack it. He went carriers. I don't think there's any carrier imba thing going on here. JangBi was legitimately a mile ahead. It's just terrans can be a bitch to clean up when they don't want to lose and NaDa was camping in the hope that eventually JangBi would get bored and suicide his army, allowing NaDa to win.

Eventually NaDa decided things were looking as good as they ever would and moved out. JangBi did his JangBi thing and poured storms all over NaDa's goliaths while his carriers sniped the tanks that had been massing all game. A counter attack of JangBi's main army hit 9 but was cleaned up and NaDa went for the expansions at 6 and 5 that JangBi needed. However with Byzantium being covered with cliffs the group of carriers harrying NaDa's main army took its toll. Yet another ground attack killed the now undefended 9 and left JangBi with 2 bases to NaDa's one, map control and a much larger army. Realising he couldn't hold his only expansions and that it simply wouldn't matter even if he could NaDa gged out.

GG

This game was more like it. JangBi didn't use an unorthadox build but was still as dominant as I'd like. His entire early and midgame, from the goon suicide to sniping into dual speedshuttle arsonist toss into suicide storm attacks on NaDa's army were built around maintaining aggression and threat while not actually committing his main army. NaDa was on the back foot all game and couldn't stop JangBi from taking the map and the win.

Stork vs fOrGG. Another clear favourite, another Samsung PvT. I almost pity the Samsung terran lineup for having to get raped but then I remember it's FBH and FrOzean and I just don't care. We saw these two play in the ro32 and I was very impressed by Stork's technical rush, a well executed and very clever build. While it turned out to be a close game I still expect Stork to win. And so do the fans with 79% favouring Stork.

---

Stork spawned at 11 and fOrGG at 7. However lacking JangBi's luck he scouted the wrong way while fOrGG scouted correctly. This took some of the wind out of 10/15 gate goon rush build which was countered easily by a bunker. Stork knew that once scouted it was unlikely to work so rapidly transitioned into economy and proxy robo attempt, making just 3 dragoons. fOrGG made a bunker and then repaired it until a siege tank arrived to secure the natural for him. His proxy pylon was scouted but Stork simply switched to a robo in main. fOrGG, still worried about a goon break decided to come out of the closet and made a wall of a rax, ebay and bunker in front of his nat with tanks behind it. Stork then revealed his secret build, the same one as he used in the ro16. If you read my ro32 report you'll see me giving a whole lot of love for the build. Subsequently I've been using it every game I can and extremely happy to see a Byzantium variation of it. He elevatored down an army and tore shit up in fOrGG's main. By the time fOrGG finally had a tank line set up the reaver arrived and Stork ripped it to pieces before moving on to rape the scv line. While all this was going on Stork was double expanding and just generally being a much better player than his opponent.

fOrGG scouted how far behind he was and decided he was eager for the next game so tried moving out. Stork was happy to oblige and flattened him with absolutely no regard for micro or strategy.

GG

Fucking loved it. I loved this build when I saw it the first time round, I love it the second time round and I really love the balls to use the exact same build vs the same opponent twice in a row. Even when he scouts it the second time. Stork gets bonus points for his perfect execution with that reaver micro.

---

So, game 2 on Neo Harmony. If there's a map that's good for him to do the exact same build again it's this one. However after JangBi did a proxy robo last week and Stork did a proxy robo every game so far I guess fOrGG is expecting it. Still, we can hope. Stork at 11, fOrGG at 7.

Stork opens macro tech in a "I don't care what you do" build. Standard 1 gate fast core with a very late scout because he's powering his economy. He scouts the wrong way but still scouts faster than fOrGG who doesn't scout at all, eventually scouting correctly after his second depot finishes. Rather amusingly, before fOrGG even scouts a single base site he checks the expo next to his cliff to see if he's being proxy roboed. Now that is mind fuckery right there. You know you've got into their head when they don't care where you are, all they care about is whether you're going to beat them in the same way again. After checking every proxy site he could think of fOrGG placed the cc in his main for a 1 fact expansion build. However he was a little too ambitious trying to push back Storks dragoons. What happened next was, in my opinion, hilarious. Stork pushed in with 3 dragoons and a zealot taking the mine damage. A mine killed 2 marines and hurt the tank allowing Stork to push in and kill the tank. Stork then outmicroed a few mines and forced the cc to fly out. Deciding that 4 dragoons and no observers, or even a robo, was enough to take the kill Stork then sniped a vulture on the ramp and pushed up with his dragoons into the mines, blowing up 2 more vultures along with half his dragoons. Stork kept up these utterly ridiculous attacks which were somehow doing more damage to fOrGG than they were him, despite the fact that his goons were walking corpses and he still had no robo. Eventually fOrGG got enough mines down that Stork would risk losing all his goons if he just moved into them, rather than the previously acceptable loss of 3/4 of his goons. The observer then panned back to Stork's base where he's going 2 base carrier without bothering with a robo. It's glorious.

Stork tries to take a 3rd base and wall it in but vultures get there too early and it is mined off from him. Eventually Stork gets his critical mass of carriers (3) and moves in for the kill. fOrGG realises he's been pimped and moves his entire tank force to camp the choke by Stork's nat where he knows Stork can't engage him in a fair fight. Stork sacrifices his expansion as his carriers (4 now) take out fOrGG's. Then carrier micro destroys groups of goliaths while Stork's main army holds his main against the tank push. The armoury goes down and fOrGG realises he's been defeated.

GG

I loved it. The goon rushes were ridiculous. You just don't normal move a group of dragoons up a ramp you know has mines on it. It's not done, and not done for very good reasons. But he was in a rare moment where fOrGG had absolutely nothing and if he kept attacking then fOrGG couldn't establish the foundations of a solid defence. Terran defences get exponentially stronger as you add units and by constantly attacking Stork created the amusing sight of a single red hp goon tearing shit up. The 2 base carrier rush was just funny. I don't know if he's taking the piss or not but I really hope he is and fOrGG must be fuming.

---

Stork 11, fOrGG 5 on Destination, the site of Stork's first victory in the ro32. Stork scouted on 7, as in the ro32, while fOrGG went for a very fast rax at his wall, perhaps fearing some kind of cheese rush from Stork given that he was 2-0 up. Stork got his probe in and threatened to take the gas. This is actually a form of harass because often the T will cancel a scv to get the minerals for an immediate refinery. Even if you have no intention of taking their gas you should threaten it. fOrGG was cutting serious scvs. A quick count of them while he took his gas revealed nine, presumably with one building. Given his barracks was half done at this point that means that he must have fucked his own economy over fairly hard just to play safe against a potential rush. Being forced to make the refinery early can't have helped his situation, and nor would the manner pylon that Stork placed, trapping 2 scvs fOrGG simply couldn't afford to have trapped. Stork opted for a zealot to into 1 gate goons with range into robo and a 2nd gate while fOrGG went for 2 fact with both addons. Conscious of JangBi's loss Stork carefully scouted all proxy sites but was ill prepared for fOrGG's push of pure rines and tanks with fast siege. He eventually killed the marines and a standoff ensued. Then Stork decided to do something progamers never do and went for a tank break with 5 dragoons against 3 tanks. It was a bad time for it and mines fucked him up a fair bit but whatever, it's the thought (and the pure aggression) that counts. fOrGG's build, a contain rush, trying to establish position on the twin bridges at his nat, seemed to have worked. Stork FEed to his mineral only because his nat was very vulnerable and tried to break out. His usually perfect reaver micro let him down and his goon suicides which were so amusing to me in game 2 were very costly to him in game 3. However as fOrGG played safe, securing his main against any possible drop play and taking his expansion, Stork was able to force the bridges from him and expand to his nat.

fOrGG's retreat is fine in theory because he's done all he needs to, delaying Stork's expansion while getting his own. Unfortunately for him Stork took his mineral only early so it didn't actually work but the thought was there. I guess Stork then felt he had something to prove after wasting his first reaver so he went on a killing spree. A serious killing spree. He raped fOrGG's nat, not only stopping mining but also killing 2 tanks and a turret, as well as the usual scvs of course. Then he moved on to the main where he stopped mining, killed scvs, killed a turret and claimed 3 tanks. I'm not entirely sure how he did all this with just one reaver (it was the same one, it just didn't die). fOrGG decided to take his huge mob of tanks on the offence and pushed towards the high ground at 2, hoping to take out the expansion attempts. While he was successful against Stork's main army he hadn't bargained on the mighty shuttle (this time armed with a zealot and a few mines) which promptly took out 3 more tanks and injured many more, causing fOrGG to retreat once again. Stork attempted to push the advantage with mass goon into mass tank and wasted a dozen more goons, as well as losing his hero reaver. fOrGG again tank pushed to 2 and again the shuttle moved in with zeebombs which claimed another 3 tanks while his main army (now with speedlots instead of just pure goon vs pure tank) flattened fOrGG's. Then Stork wasted another group of dragoons allowing fOrGG to rush up onto the high ground at 2 with 3 tanks, 8 vultures and an awful lot of mines. The vultures slaughtered probes at his mineral only while Stork forced the high ground off him by wasting units (and the hero shuttle). Deciding he hadn't quite wasted enough goons yet Stork suicided a few more into mines (wtf are you doing man? It was funny game 2 where I thought you were being all awesome but this is just sad) and again had trouble holding 2. fOrGG lifted the cc from his mined out main to 5 and started mining there while Stork attempted to take 10 but was delayed by a mine. The push against 2 turned into a stalemate with neither side earning anything but losses as both the no mans land between them proved unholdable. fOrGG got a group of tanks dug in on the high ground at 3 and then pushed a wall of tanks forwards, eventually taking 2 off Stork who evaced the probes to 10.

Stork realised he might actually be in trouble so made another of his ultimate unit, the shuttle, to destroy fOrGG at 5. Faced with a reaver fOrGG countered the only way he knew how, by stacking his scvs. When reinforcements moved in it 2 darks also emerged from the shuttle and racked up some kills before jumping back in away from the scan. Stork suicided 4 more dragoons into mines, probably because he was winning again and then moved his main army down the left hand side of the map which was largely tank free. Defeating fOrGG's main army (and suiciding another 8 dragoons into mines) fOrGG was forced to move his army from his base at 5 which was promptly raped by the shuttle which was still there.

GG

This game was really scrappy. Stork was all over the place, his refusal to use observers, his inability to use speedlots for half the game, his unwillingness to go above tier one tech. It wasn't a good display of Brood War. It was just a mess. fOrGG stayed at 0-0 all game but I'm not sure I can blame him for that because he was against the wall for most the game. What I can blame him for is being raped by reavers over and over all game. Jeez. Also he obsessed way too much about taking 2 to the point that his entire force was committed to an unstoppable slow push which Stork promptly went round while abandoning the top right in favour of new bases on the left. And he kept walking his army over mines. It was just a complete mess from both players. Stork should be ashamed of how many dragoons he threw away that game, especially when he had observer tech throughout.