Tower War looks like a numbers game. More towers, more units, more color on the map. But the hidden variable is path geometry—how your captured towers connect, not how many you hold. A player with six poorly linked towers loses to someone with four that form clean diagonal highways. The tutorial teaches tapping and sending. It does not teach that overlapping paths multiply your effective army size without multiplying your tower count. This guide fixes that gap.
The Path-First Priority List
Your first hour should feel less like conquest and more like urban planning. Every tower you take must answer one question: does this make my paths straighter or my network more redundant?
Early towers have tiny capacity. One path, a handful of units, long recharge. The instinct is to grab everything nearby. Resist. A tower isolated behind a zigzag of captured points is a resource sink—it defends nothing, attacks nothing efficiently, and splits your capacity across dead-end routes.
Instead, prioritize fortified corridors. The source material notes that layered paths become possible as you gain control points, but the critical early move is identifying which two or three towers form a natural diagonal or straight line toward the map's center or toward a cluster of unoccupied high-value towers. Capture those. Ignore the tempting one-off tower that breaks your line.
The trade-off is immediate map presence versus sustainable pressure. A scattered empire looks impressive. It also means each tower spends half its cycle idle because units are still marching. A tight corridor means units arrive faster, die less to attrition, and allow you to stack multiple paths once capacity increases. You gain tempo. You lose the illusion of dominance.
Hidden variable: tower health as throughput. Damaged towers send fewer units. The tutorial implies health matters for defense. It matters more for offense—every chip of damage on your forward tower is a permanent reduction in your attack rate until you invest time and resources to heal it. Early fights that "win" but leave your corridor tower at 30% health are net losses. You now own a bottleneck that cannot push.
Decision shortcut: Before attacking, trace the return path. If your new tower cannot receive reinforcing units from your backline without crossing enemy territory or making a three-turn detour, you are building a salient, not a corridor. Salients get cut off. Corridors get reinforced.
What the Tutorial Under-Explains
Capacity is shared, not per-path. This is the single most expensive misunderstanding. When you unlock enough control points to run two paths from one tower, both paths draw from the same pool. The UI does not scream this. New players see "two paths available" and assume "two armies." They get one army split in half, arriving in staggered waves that the defender picks off.
The asymmetry: a single thick path breaks defenses; two thin paths feed the enemy experience and waste your recharge cycle. Unless you have excess capacity—rare before mid-game—one path is correct almost always. The exception is pincer situations where timing forces the enemy to split attention, but this requires coordination you likely lack in hour one.
Unit types and tower bonuses interact silently. The source mentions "units and vehicles doing the work," but does not detail that certain towers modify specific unit speeds or health pools. Without access to internal mechanics documentation, the safe principle is: match fast units to long paths (they close distance before attrition) and durable units to contested corridors (they survive the tower-to-tower gauntlet). The wrong pairing does not fail obviously. It fails slowly, as you wonder why your "superior" numbers stall.
Healing is opportunity cost, not free. Towers heal automatically when not sending units. This creates a perverse incentive: the tower you just captured, damaged and isolated, needs healing before it contributes. But every second it heals, it is not sending units to the next target. Early-game, this downtime is where matches are lost. The fix is not "heal better" but "take less damage" through the corridor strategy above—arriving with more units means the tower swaps color before significant damage accumulates.
Mistake that wastes time: retreating to defend a rear tower under light pressure. Unless it is a corridor break that splits your network, a damaged rear tower is cheaper to rebuild than the tempo you lose pulling units back. The exception is your starting fortification—losing that ends the run. Everything else is expendable in the first hour.
The Three Decisions That Shape Your Run
Decision one, roughly ten minutes in: corridor commitment. You have four towers, maybe five. Do you extend toward the map center, toward a dense enemy cluster, or shore up a defensive flank? The correct answer depends on spawn density you observed in the opening. High unoccupied tower density in one direction means map control snowballs there. But if two enemies are already fighting over that cluster, the flank may be uncontested expansion. The hidden variable is attention economy—enemies focused on each other have units committed and slow reaction time. A flank stab into their rear corridor forces them to either abandon their fight or lose their network. Most new players take the obvious center. Better players take the flank that makes the center fight irrelevant.
Decision two, roughly twenty minutes in: capacity investment versus tower acquisition. Control points from new towers expand your network. Control points spent on existing towers increase their capacity. The tutorial pushes acquisition. The correct ratio shifts based on map state. If you have clean corridors and unclaimed targets within two tower jumps, acquire. If you are bumping into fortified enemy positions, capacity lets you stack paths and overwhelm. The asymmetry: capacity helps everywhere; acquisition helps only where you can reach. A common waste is taking a tower at the edge of your network that cannot be reinforced quickly. It becomes a gift to the enemy when they counterattack.
Decision three, the mid-game pivot: when to shift from linear corridors to layered paths. This is not a timer. It is a network geometry check. When you can trace three independent routes between any two of your towers, you have redundancy. At that point, capacity upgrades and multi-pathing become powerful because losses in one corridor do not stall your entire map. Before that redundancy, multi-pathing is thin soup. After, it is overwhelming pressure from multiple angles.
The trap: players see the "layer paths" tip and implement it early because it feels advanced. It is advanced. It is also wrong without the infrastructure. Premature multi-pathing is how you lose to a player with fewer towers but one thick, well-timed push.
The One Thing to Do Differently
Stop counting towers. Start tracing lines. Before every capture, draw the path your units will take—not to the target, but through the target to whatever comes after. If that next step does not exist, you are not expanding. You are ending. The players who last past the first hour are the ones who built networks that attack in multiple directions without thinking, because their corridors do the thinking for them.
