{"id":663,"date":"2014-11-09T19:47:38","date_gmt":"2014-11-10T03:47:38","guid":{"rendered":"http:\/\/starcraft.kevinleung.com\/?p=663"},"modified":"2015-07-20T10:58:11","modified_gmt":"2015-07-20T17:58:11","slug":"legacy-of-the-void-throw-out-the-playbook","status":"publish","type":"post","link":"http:\/\/blog.spawningtool.com\/?p=663","title":{"rendered":"Legacy of the Void: throw out the playbook"},"content":{"rendered":"

(This is part 1 in a series<\/a> on the multiplayer changes announced for\u00a0Legacy of the Void at BlizzCon)<\/i><\/p>\n

I am kind of obsessed with build orders. Since I’m not actually good enough at StarCraft to give real advice and analysis, it is much easier to create content by transcribing builds from professional games. That turned into a much larger endeavor in Spawning Tool, a website dedicated to build orders. And with Legacy of the Void (LotV), I can now throw away everything because players now start with 12 workers.<\/p>\n

The worker change isn’t the splashiest part of announcement, but it does disrupt the meta-game in a far bigger way than the new units. With all of the LotV changes, there are 3 different ways that build orders will change:<\/p>\n

    \n
  1. Some build orders will no longer be possible<\/li>\n
  2. New build orders will be possible<\/li>\n
  3. All build orders will have to adapt to the meta-game<\/li>\n<\/ol>\n

    Eliminating build orders is straightforward. Zerg cannot 10 Pool because they start with 12 workers. Proxy 2 Rax at 12 supply is probably gone because you should have more SCVs by the time you start your proxy.<\/p>\n

    Adding build orders is also straightforward. As seen in the showmatches, both the Herc and the Ravager\u00a0can play a huge role in the early game. These build orders were previously impossible because we didn’t have those units.<\/p>\n

    How the build orders interact, I think, is the most interesting effect because when other build orders are added or eliminated, all build orders must change to remain optimal. Some build orders had safety strategies built in for eliminated build orders, so these can be streamlined. Some\u00a0build orders are unprepared for new strategies and have to adapt for those.<\/p>\n

    It’s hard to overstate how meta-game specific builds are. The Forge fast expand is a strange build, and yet, it (and other fast expand variants) is relatively standard because of the threat of Zergling rushes. As Zergling rushes waned, the 1 Gate expand gained popularity. Through several iterations of meta-game shifts, we can arrive in places where “outdated” builds could actually work better against current builds, but modern builds are adjusted for the current context. With a sudden change in possible builds, every build will have to change to react.<\/p>\n

    I do think most of this thought process will be more natural than it sounds. The radical change in the game will cause players to start from the ground-up rather than tweaking existing builds, and even in tweaking, the reactions should be clear. The general point, however, is that early game looks very different from before. Old school cheese is basically gone. Instead, every build order versus Zerg knows that it has to handle a 12 Pool at the fastest and work from there. The jumpstart means that a player doesn’t even have enough time to scout some of these openings before they have already arrived with a rush.<\/p>\n

    Despite all of the negativity above, I am actually really excited to get the global reset on build orders. HotS changed some openings, but not a lot. The Reaper Expand became standard, but it is still a 1 Rax Expand. Protoss had to figure out where to add the Mothership Core. Zerg didn’t really need to change much. LotV is a chance to cast away years of strategies and start over again in a fresh world with a lot to explore.<\/p>\n

    Refining builds is interesting, but I think we have the most fun being surprised and trying to work on completely new build orders. I will try to do my best to provide content and tools to help the community as much as possible, but don’t be surprised if things change very quickly.<\/p>\n","protected":false},"excerpt":{"rendered":"

    (This is part 1 in a series on the multiplayer changes announced for\u00a0Legacy of the Void at BlizzCon) I am kind of obsessed with build orders. Since I’m not actually good enough at StarCraft to give real advice and analysis, … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,66,74],"tags":[67],"class_list":["post-663","post","type-post","status-publish","format-standard","hentry","category-build-orders","category-game-design","category-legacy-of-the-void","tag-lotv"],"_links":{"self":[{"href":"http:\/\/blog.spawningtool.com\/index.php?rest_route=\/wp\/v2\/posts\/663","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/blog.spawningtool.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.spawningtool.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.spawningtool.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.spawningtool.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=663"}],"version-history":[{"count":5,"href":"http:\/\/blog.spawningtool.com\/index.php?rest_route=\/wp\/v2\/posts\/663\/revisions"}],"predecessor-version":[{"id":669,"href":"http:\/\/blog.spawningtool.com\/index.php?rest_route=\/wp\/v2\/posts\/663\/revisions\/669"}],"wp:attachment":[{"href":"http:\/\/blog.spawningtool.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=663"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.spawningtool.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=663"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.spawningtool.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=663"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}