CASE STUDY 02 — Germans vs Medium Athenians: The Boom-and-Punish

CONTEXT The Setup FROM 4 LOSSES TO 1 WIN

This is documentation of the *first Medium AI win* by NoobScience. After 4 losses on Medium with Ptolemies and Romans, switching to *Germans vs Athenians* produced a decisive victory. This case study reverse-engineers the win from the replay.

"I won. I attacked his CC, it fell. I constructed my CC immediately in place of it, then attacked the second CC and I found the last of his villagers and I won.

— NOOBSCIENCE · POST-GAME REPORT

Element	Value
You	Germans (cheap mass units, mobile CCs, maceman anti-building)
Enemy	Medium AI Athenians (balanced, ranged-heavy, predictable scripts)
Difficulty	Medium — previously unbeaten by player
Result	Decisive win — both enemy CCs razed, last villagers swept

WHY GERMANS The Civ Match WHY THIS CIV FOR THIS PLAYER

This wasn't a random civ pick. Germans match the *human meta* — the realization that humans can't out-orchestrate Medium AI's parallel execution, so they need a civ that *trades orchestration depth for raw simplicity*.

Cheap units → no precision needed, just volume
Easy population boom → solves the "AI booms exponentially" problem head-on
Mobile CCs → forward base is built-in, no Roman Military Camp coordination needed
Macemen self-destruct buildings → no Phase III siege required to crack walls
No upgrades required → fewer tech-tree decisions = less cognitive load

The principle: When you can't out-execute the AI, change the game so execution matters less. Germans remove three decision points (composition, siege timing, forward production) that Romans/Ptolemies require constant attention on.

TIMELINE What Actually Happened RECONSTRUCTED FROM REPLAY

0:00 — START

Pure boom focus. No early military priority.

Player went hard on economic expansion from second zero. Two horsemen sent for light harassment but the focus was unambiguously: boom first, fight later.

WHY: Germans' civ identity is volume. Wasting Phase I on tactical harass dilutes the boom. The horsemen were a *probe*, not a strategy — barely cost a thing, gave map intel, drew light AI attention.

3:00 — 5:00 — VILLAGER FLOOD

Hyper-boom in motion. Houses preempted pop cap.

By the time the enemy had built their *second barracks*, the player had built their second CC. Replay-confirmed.

WHY: This is the *defining move of the entire game*. A second CC at minute 5-8 is the single highest-ROI compounding action in 0 A.D. Two CCs = double villager production = double rate of every subsequent thing. The Germans civ bonus made this affordable; the player's decision to prioritize it made it decisive.

7:00 — FORWARD TOWER

One tower at the enemy's resource line.

Dropped a single archer tower near the enemy's wood/metal collection point. The AI panicked and committed its entire first wave to break it.

WHY: *Over-extension bait.* One tower (cost: 100 stone) triggered the AI's full first wave. Their wave hit a stone tower instead of a soft eco. Their main wave was therefore blunted against a target that gave them nothing. Cheapest disruption play in the game.

8:00 — WAVE 1 ABSORBED

Survived with 150 troops to spare.

The forward tower fell — but it cost the AI heavily. By the time the wave reached the German base, the player's overwhelming population (boomed all the while) easily mopped up the remainder.

WHY: *Population beats precision.* The player didn't need tactical brilliance because they had 3x the army. The wave that would have crushed Ptolemies or Romans bounced off the German mass.

10:00 — WAVE 2 ABSORBED + SIEGE BUILD

Active production never stops. Two siege machines under construction.

Wave 2 clashed with the rebuilt army. The player kept production running through both waves. Two siege machines (likely Onager-equivalents) built during the interlude.

WHY: *The interlude is where wave 2 is won.* The discipline of "production never stops" — internalized from the Defense Strategies manual — meant reinforcements arrived during the fight, not after. The siege machines were preparation for the strike phase.

14:00 — "SOMETHING IN ME TRIGGERED"

The strategic instinct fired. Pivot from defense to attack.

The player recognized the moment — enemy army committed forward, their base inferred to be thinly defended. "This is my chance."

The plan was a *feint*: attack a few towers, retreat, draw their army into a kill zone at home.

WHY: *This is the Counter-Commit play, executed.* Recognizing enemy over-extension and pivoting to offense is the hardest psychological move in RTS — every instinct says "stay home and defend." The player overrode that instinct. Strategic maturity.

15:00 — THE PIVOT WITHIN THE PIVOT

Found the base empty. Abandoned the feint plan, went straight for the CC.

Arrived to attack the first tower expecting resistance. There was none. The player abandoned the prepared feint and committed fully: siege + army straight at the enemy CC.

WHY: *Plan adjustment under live information.* The original plan was a safe feint; reality offered a better option. The player read the new information and changed plans in flight. This is the play that separates competent from instinctive players.

16:00 — CC RAZED + REPLACED

Enemy CC falls. Player builds a new Mobile CC on top of the ruins.

The macemen + siege flattened the enemy CC. Immediately, the player dropped a fresh German Mobile CC on the same spot. The enemy could no longer rebuild on their original location.

WHY: Pure Germans signature move. Mobile CCs aren't just for forward expansion — they're for *denial*. Razing + immediately claiming the territory locks the enemy out of the spot permanently.

17:00 — SECOND CC + SWEEP

Marched on the second CC, found the last villagers, won.

The enemy had a secondary CC. Same treatment. With both production sources gone and the army already lost, the AI had no path to recover. Sweep of remaining villagers ended the game.

WHY: *No half-measures.* The decision to continue after the first CC fell — to not retreat for a "safe" outcome — closed the game permanently. The opposite of trickle. A full commitment with infrastructure to match.

PRINCIPLES What This Win Exploits PATTERNS WORTH KEEPING

Principle	From manual	How it appeared in this game
Choose the civ that matches your strengths	This case study	Switched from Ptolemies/Romans to Germans — civ matched player's strategic style.
Linear vs exponential boom	VOL.05 Economy	2nd CC at minute 5-8 was the compounding decision that won the game.
Forward Tower disruption	VOL.02 Attack	Single tower at enemy resource line triggered their full first wave for free.
Production never stops	Wave 2 doctrine	Both waves absorbed with army growing, not shrinking.
Counter-commit / over-extension punish	VOL.02 Attack	Saw enemy army committed forward, marched on their base.
No half-measures	VOL.02 Doctrine	Continued past the first CC kill to finish the game.
Plan adjustment under live info	NEW LESSON	Original feint plan abandoned when reality offered something better.
Raze + replace with mobile CC	VOL.09 Germans	Denied enemy rebuild on original CC location.

META The Real Lesson BIGGER THAN THIS GAME

// Civ choice is not aesthetic

Four losses with Ptolemies/Romans, one decisive win with Germans, against the same difficulty. The civ was the difference, not the skill. *The right civ removes the part of the game you're worst at and amplifies the part you're best at.*

For the player who developed this manual:

Worst at: parallel orchestration, precise composition, micro-management
Best at: single decisive decisions, reading openings, committing fully

Germans rewards exactly those strengths and forgives the weaknesses.

// The "I'm quitting" → win arc

The night before this win, the player declared they were quitting 0 A.D. — too stressful, not fun anymore. Within 24 hours they tried one more game, with a different civ, and won decisively. *Sometimes the answer to a losing streak isn't more grinding — it's a system change.*

The lesson: When something stops working, the answer is rarely more effort. It's usually a different angle. Switch the variable that's locked.

// "Something in me triggered"

The pivot moment — recognizing the enemy was over-committed and going for their base — wasn't from the manual. It was instinct, fired correctly. This is the goal of all the strategy work: not to memorize plays, but to develop the instinct that knows which play to call. The player got there.

FRAMEWORK Updated 6-Question Framework REFINED FROM CASE.01

The 6-question framework from Case Study 01 still applies. One refinement based on this game:

Q	Old version (CASE.01)	New version (CASE.02)
00	(implicit)	Does my civ match my strengths? If not, switch.
01	What is the map archetype?	(same)
02	What's the enemy civ's signature comp?	(same)
03	What's your civ's signature counter?	(same)
04	Where can the first attack come from?	(same)
05	What's the minimum army I need by minute 9?	(same)
06	How do I leave Wave 1 with units AND eco intact?	(same)

New zeroth question: Civ match. *Add this to every pre-game checklist.* The right civ is the most consequential decision in the game.

ENDPLATE The Three Sentences from This Game MEMORIZE

The right civ matches your strengths. Switch if you're losing the same way repeatedly.
Population beats precision. With enough mass, tactical mistakes get absorbed.
When the enemy commits, march on their base. Trust the instinct.