01
Playable CoreA complete match
A match can begin, develop and end through connected hero, combat, seed, lane, structure, resource and UI systems.
MUTERRA Roadmap
Build the match. Then make the world fight back.
The production sequence is organised by what must become true in the product — not by dates chosen to look good on a timeline.
Production sequence
Complete match → deep combat → living world → public product.
Each phase depends on the one before it. This is a production roadmap, not a quarterly token calendar.
02
Combat DepthDecisions gain weight
Movement, targeting, abilities, AI, bosses, territory and tactical consequences become richer and more tactile.
03
Living WorldLife joins the match
Ecology, parasites, dynamic territory, resources and environmental pressure begin changing the battlefield.
04
Soft LaunchA repeatable product
Progression, matchmaking, analytics, optimisation and public testing support players who return.
No public calendar dates are invented here. The current source defines production dependencies and phases. Delivery status must be verified against the approved current build.
Phase 1 / Playable Core
The first goal is not more content. It is a complete match.
Every later system becomes noise if the core match cannot already hold together.
Move and aim
Movement, camera, targeting, aim assistance, projectile combat and the initial ability framework.
Create during play
Inventory, planting, growth, hatching, creature spawning and AI participation.
Pressure has direction
Lane paths, creep combat, towers, base health and a clear victory condition.
Begin, read, finish
Start flow, timer, respawn, resource feedback, HP bars and functional HUD.
Movement + ballistics
The player should feel the difference before reading about it.
Range, angle, movement, terrain, timing and target body zones can change what a shot means. Hero movement, camera, projectiles, beams, area damage and hit feedback are core work, not late polish.
- Movement and camera need to support readable combat.
- Projectile behaviour needs to create spatial decisions.
- Unintegrated mechanics remain labelled in development.
Seeds in the core loop
Creation happens during the match.
Seeds are not a side crafting system. The reliable starting sequence is deliberately simple.
- Carry → Plant → Grow.
- Hatch → Command or release.
- The creature affects the match.
Phase 2 / Combat Depth
A working fight is not yet a good fight.
The player should start making strategic decisions because the combat system gives those decisions consequences.
2.1
Combat feel and targeting
Hit feedback, telegraphs, VFX, camera tuning, threat visualisation, target switching and improved aim assistance.
2.2
NPC intelligence and hero depth
Better movement, target priorities, differentiated roles, more abilities, combinations and passive behaviour.
2.3
Bosses, elites and danger zones
Neutral threats interrupt plans, force timing decisions and create contested risk inside the competitive match.
2.4
Territory and performance
Tree-control direction, capture, neutral reclaim, AI LOD tuning, large-battle stability and combat profiling.
Phase 3 / Living World
This is where life itself becomes a participant in the match.
The goal is not more NPCs. It is a battlefield whose ecology creates pressure, changes routes and remembers what players did.
Resources become alive
Animal systems, agrarian systems and resource creatures form interacting pressures.
Problems can follow you
Parasite entities, infection direction and combat states create systemic threats.
The battlefield changes
Growing zones, living territory, vision, routes and environmental pressure affect decisions.
Interpret the complexity
Battle suggestions, warnings and seed recommendations are planned to help read the world, not play for the user.
Phase 4 / Soft Launch
A playable build becomes a product people return to.
A retention system cannot compensate for a match people do not want to replay.
Return loop
- Player profile, match history and progression.
- Rewards, unlocks and cosmetics.
- Lobby, match start, matchmaking and reconnect.
- Public tests, showcases and playable exposure.
Operational foundation
- Telemetry, match statistics and balance evidence.
- Mobile performance and network stability.
- AI LOD and large-battle profiling.
- Quality that works beyond a development machine.
Status discipline
Roadmap status must come from the build, not marketing.
A prototype, document or finished design is not proof that a system works in the current approved build.
Use only after direct build review confirms the system supports the published claim.
Use for current production work without presenting it as public-ready functionality.
Use when the production direction exists but implementation is not yet approved as current.
Features can move. A mechanic can be cut. Performance can force redesign. Testing can reveal a more important problem.
The sequence should remain explainable: complete match → deep combat → living world → public product.
Production before promises
Founder funding expands work already underway.
Development, art, characters, environments, cinematics, infrastructure, testing and community operations must remain connected to the production sequence shown here.