Tag: positioning

Warcraft III base design: positioning requires awareness of Range.

Warcraft III pro Grubby recently streamed a guide covering base layouts for various match-ups. Regardless of game, good positioning of an asset relies on understanding the ranges of the attacks and abilities likely to see play, and this certainly holds when we look at Grubby’s building placement advice.

In the orc vs. undead (0:00-6:00) matchup Grubby stresses the importance of protecting key buildings (altar, higher tier unit production) deeper within, away from ranged pressure. Undead generally harnesses the crypt fiend unit, a bulky source of ranged damage. Orc should aim for an open design to permit their own units to kite into the base away from ranged attacks, forcing the crypt fiends to cycle inconclusively between multiple targets or else be drawn deeper into the base to secure kills.

Against human (9:01-12:12), early pressure comes from melee footman attacks. To protect structures, orc should place burrows behind such that the burrow range covers the buildings outer edge. A second early tool from human is a tower rush, where a worker constructs a tower in sight of the mining peasants or key structures. Orc should place burrows so as to cover the spots within tower range of the peon line, where human peasants would have to stand to build a relevant tower. Burrows should be grouped closely enough to protect one another, lest they be isolated and pushed down by footmen/militia/water elemental pressure.

The discussion about orc base layout vs. night elf (12:56-15:00) especially drives home how range impacts placement. The old norm for night elf centered around using the melee Demon Hunter hero. Orc responded by building a very tight base seeking to wall off their front and deny Demon Hunter penetration. The newer night elf approach leans on the ranged Keeper of the Grove hero early, creating a very different type of pressure. Orc has adapted by moving away from a wall-off in favor of a semi-open base. Buildings should be placed to cover up and make impassable the Keeper’s preferred spots for max range harass on the peons. Such placement gives Keeper with fewer and closer positioning options, inviting Keeper to overextend into the orc base. Further, orc uses a burrow extremely close to the peon line, such that peons targeted by Keeper can be microed to safety with minimal travel time, thus minimizing exposure to Keeper’s shots:

The orc mirror (15:06-end) match calls for a flexible start until the opponent’s first hero has been scouted and confirmed to be as the melee Blademaster or ranged Farseer. One wants an option to create a wall against blademaster, with outs to shift towards a more open base once and if a Farseer is spotted:

[All] Don’t position against a wall (without good reason)!

Today we return to the site’s roots, looking at a general strategic idea that exists across the gaming world: “Don’t position against a wall!” I’ve most recently remembered this idea from reviewing and playing Overwatch games, but it has cropped up many times before. Sometimes the wall is physical, sometimes it is metaphorical, but by definition it limits your available moves. This is a gift to the opponent! It makes their job easier. We want to do the opposite. As I’ve put it before, we want to “put the onus on the opponent.*” We want to make their job harder, to give them opportunities to misplay or guess wrong. Let’s look at some examples.

(11:54-12:18) First I’ll take a look at an Overwatch clip, though the ideas extend very naturally to games involving realtime movement prediction. It’s here that the concept of not positioning flush against a wall most recently returned to my thoughts. Here is a brief example that cropped up while I was reviewing and analyzing a set of replays from a player’s run to diamond rank. The Ana, by positioning right up against a wall, takes hits from all 3 of Genji’s shuriken. If she had a little more leeway to play with, she could force Genji to divine her movement, putting the onus on him to guess correctly in order to land his damage:

The example above has analogues in other FPS and also arena games, like League of Legends. For example, a Thresh chasing down a champion towards a wall will wait to hook until the enemy is up against the wall, reducing the directions they have for juking But you might be surprised to realize this idea comes up even outside of real time movement-prediction games. In chess they often say “A knight on the rim is dim,” referring to the weakness of the knight when on the edge of the board. A centralized knight could move to 8 squares, but on the edge will have only two options. It’s so bad that the rim knight can be completely “dominated” by a bishop, as presented by YouTube commentator MatoJelic in this clip:

(19:58-20:26) In the Overwatch example the wall was a physical wall. In the chess one, the wall is almost physical, consisting of the edge of the board. Now let’s look at a Magic: the Gathering example. In this clip from the recent Week 7 of Vintage Super League season 7, Rachel Agnes highlights a good example of a metaphorical wall restricting a player’s options. Rodrigo Togores has only 1 life left, making him unable to pay the alternate cost of Force of Will (card image below clip) without losing the game. Having even one more life would require his opponent to play around the possibility of a no-mana-cost counterspell, but as-is he’s against a wall. The opponent knows that if he does have the Force, he must pay the full 5 mana for it or not use it at all. Rachel goes on to share the amusing tale of a past an opponent of hers who threw away a winning game by needlessly paying their last point of life to counter a spell unnecessarily:


* Aside: In the past, I’ve used the phrase “put the onus on the opponent” to talk about minimizing risk while comfortably maintaining a gamestate where the opponent is disadvantaged, where if nothing changes the status quo will bring you more advantage or a win, forcing the opponent to take on risk in trying to “make something happen” that might upset this trajectory.