Wednesday, March 14, 2012

Scheduling Timings

Schedules (The "I'm venting" section)
Probably the biggest problem I have been having in my attempts to climb in views is having a set schedule. I am an out-of-state college student studying Information Technology (using computer systems to improve business, mainly), and well as a vocal performer, exercise enthusiast, and would-be outdoorsman. My schedule is constantly changing based on deadlines for classes, weekends spent at home, and things as simple as a nice day to go rock climbing. For those of you who have stuck around since the beginning in November of 2011, you know my schedule has changed a lot. There was even a couple weeks where I was streaming 6 days straight! Unfortunately, time just does not permit such anymore, and even with cutting back to two, my days are always on the verge of chaos. Without a set schedule, it is difficult to pull consistent viewers, aka ones who keep coming back. Just a thought to keep in mind.


The following concept of Dynamic Timings, rather than Static (based on supply) is mainly based for the younger players out there. You more experienced players, prepare to bring on the "duh" factor, but calm your jets, I'm trying to look out for everyone!

What are Dynamic Timings?
When going through build orders, you will normally find your timings based on supply. At 9/10 supply build your Pylon. 13/18, your Gateway, etc... But what do you do when that build is thrown off. Let's say you're a Terran player do a 1 Rax Factory expansion and when you lift your Barracks and Factory off to get the Reactor for the Hellions, 8 Zerglings stream into your base. Not the biggest deal in the world, but you had to make a couple extra Marines and Hellions to clean up the mess. Look up at your supply and you are 10 supply ahead of where you are supposed to be. You're probably thinking, crap! I am so far behind right now! I can't imagine where my opponent must be!
Well quit your worrying! Your supply is thrown off, but it doesn't mean your timings have to be. Day[9] has been moving away from expressing timings solely in supply (which I consider a "static" timing), and alternatively has been looking at comparisons ("dynamic" timings). Let's take another example, this time from WhiteRa's Carrier rush I analyzed a few weeks ago (1).

Extended Example of Dynamic Timings
This build is anything but standard and safe. It requires a minimalistic ground army and virtually no defense until 11:00 when your Carriers are finished. If we look at the static timing for the opening, the Gateway should come around 17/18, and your first two Assimilaters around 22. Let's say you are Forge Fast Expanding and your Zerg opponent 10 Pool's you. In response, you throw down a couple of extra Cannons and keep pumping out Probes. Pretty quickly that 10 Pool is defeated and you get ready to go back to your strategy when you notice, crap! I'm already at 20 supply and everything is shot to hell! Time to go Dark Tem- STOP! Seriously, f*** Dark Templar... just no. No. Go back and look at the way I summarized the build order;

- 2 gas after Gateway
- 3rd gas @ ~50% Cybernetics Core completion.

These are based on Dynamic Timings. Those Zerglings got into your base? No problem! Just build the 2 gases after the Gateway. They hit with a second attack and delay your Cybernetics Core? Don't worry! When the Cyber Core is halfway finished, lay your next gas.

Alternate Examples
Other examples of Dynamic Timings could be, When I have 2 Siege Tanks, I'm going to push or, Once I have 10 Mutalisks, I'll start harassing. These are better than saying, I will attack at 8 minutes, regardless, because if you only have one Tank and no Siege Mode, you could find yourself in a world of hurt.

As stated above, this may seem obvious to you higher level players. The reason why this is an important point for lower level players is the mental aspect to the game. Lower level players are going to be less refined in their play, and thus be flustered more easily. They are not going to understand as well what to do when their build is thrown off. That is the reason I wanted to write about this- I was there at one point, and I understand.

  1. WhiteRa's Carrier Rush Analysis 

No comments:

Post a Comment