The Legend of Mala Tokmachka Walkthrough: First Days

This preview walkthrough outlines how to approach the first days of The Legend of Mala Tokmachka without inventing hidden damage numbers or wave timers we cannot verify pre-launch. Treat each step as a priority checklist — adapt when your run introduces threats earlier or later than expected. After Steam release, we will annotate confirmed values in Updates and adjust Weapons tier list links inline.

Prerequisites: Getting Started, skim Fortress Building and Anti-Air Defense.

Preview scope label

Label	Meaning
Confirmed	Matches Steam marketing or trailer footage
Likely	Standard tower-defense pacing inference
Verify at launch	Must confirm in-game

We avoid fabricated stats. When a cell says Verify at launch, screenshot your results and compare community notes on Steam & Community.

Day 0 — before the first wave

Goal: Stable foundation + menu familiarity.

1. Complete any tutorial prompts (Likely on first boot).
2. Place core walls forming a compact rectangle — not a skyscraper yet.
3. Install one ground gun covering the primary approach (Confirmed weapon class: machine gun or cannon).
4. Install one anti-air piece on an upper or forward cell before wave two if drones appear in your tutorial (Confirmed threat type: drones/aircraft).
5. Open Module Reference to learn role icons.

Do not spend expansion money on height until repairs feel boring — per Repair and Resources.

Day 1 — waves 1 through ~3 (preview arc)

Goal: Learn triage and threat split.

After wave 1

• Repair breach paths, not chip damage on rear walls.
• Upgrade the gun that fired most shots if money allows (Verify at launch for stats).
• Do not add a third weapon type yet — stabilize economy.

After wave 2

• If aircraft appeared: add second AA or upgrade first AA (Confirmed that air threats exist alongside ground).
• If armor appeared: consider cannon or missile slot (Confirmed weapon classes).
• Read Anti-Air Defense if sky damage exceeded ground damage.

After wave 3

• Choose a layout path: stay compact or begin controlled height (Likely escalation).
• Install first power module before lasers/missiles (Confirmed module type: power systems).
• Skim Best Builds compact bunker template for comparison.

Day 2 — mid-early escalation (preview arc)

Goal: Overlapping fire zones and repair routing.

Likely enemy mix per Steam: artillery, armored vehicles, assault groups, continuing air pressure.

1. Add overlap — second gun covering same lane from offset angle (Fortress Building).
2. Place radar if available before adding a fourth weapon (Confirmed module: radar).
3. Add repair block near power/AA core (Modules tier list).
4. Practice sacrifice call — write off an outer deck if artillery focuses it.

If money stalls, pause expansion and upgrade one S-tier preview weapon from Weapons tier list.

Day 3 — specialization fork (preview arc)

Goal: Pick a strategy instead of generalism.

If struggling with…	Specialize toward…	Guide
Air	Tall AA ceiling + power	Anti-Air Defense
Armor	Cannons + missiles	Weapons tier list
Structure loss	Repair + wide redundancy	Repair and Resources
Overwhelm	Compact reset using Best Builds

Verify at launch: whether runs are endless-only or include milestone “days.” Steam copy uses day language thematically — mechanics may still be endless waves.

Metrics to track manually

Until datamining exists, keep a notebook:

• Wave number when aircraft first appeared.
• Money left after repairs each wave.
• Which deck broke first.
• Weapons with highest kill share (visual estimate).

Share patterns on Steam forums; wiki tier updates follow verified consensus in Updates hub.

When to leave this walkthrough

Transition to advanced content when:

• You survive five+ waves without core breaches (Likely skill check).
• You can articulate ground vs air budget split verbally.
• You are ready to copy a Best Builds template with modifications.

Related launch prep

• Launch Day Checklist
• Controls once binds are confirmed
• Review & Preview for tone expectations

Preview disclaimer

This is not a datamined speedrun route. Numbers will differ. Use priorities, not memorized timers.