The Strong Side / Weak Side Concept Explained
The Strong Side / Weak Side Concept Explained. Role-agnostic map theory used by both sides to read layouts, build win conditions, and adapt in real time.
At-a-Glance
- Track: Shared
- Category: Shared Map Macro
- Primary objective: Turn map structure into clearer role decisions for both sides.
Decision Rules
- Identify the strongest and weakest sectors before first full commit.
- Tie every major decision to objective tempo, not convenience.
- Re-evaluate route quality after each resource trade.
- Pivot plans when the map state changes twice in a row.
- Keep one fallback lane unspent for unstable moments.
- Avoid repeating solved routes unless you gain immediate value.
- Use hook-state economy as a map control signal, not a separate system.
- Simplify decisions when tempo is unstable: stability first, upside second.
Common Mistakes
- Reading map state once, then never updating.
- Confusing comfort pathing with high-value pathing.
- Treating strong side/weak side as static all match.
- Overreacting to one event instead of board trend.
- Forcing textbook lines when layout disagrees.
- Skipping contingency planning for endgame shape.
Quick Checklist
- Read map shape before full commit.
- Choose a primary plan and a fallback plan.
- Track strong side / weak side changes over time.
- Tie chase decisions to objective state.
- Spend premium resources only when it changes outcome.
- Adjust for map type rather than forcing one script.
- Protect endgame positioning early, not at gates.
- Reassess after every major hook or gen event.