Code
At its heart, Maintainer One is a coding game where all logic and decisions are automated through code. Each league has an evolving protocol that determines the rules and constraints each team plays under.
Community
Open source and community driven. The maintainers for each team foster a strong community of contributors to develop the most robust logic and gameplans to adapt to an evolving protocol.
Championships
Only one team can win each season. The maintainer of that team will be awarded the Maintainer One title, cementing their legacy in the history of the league.
The Founding Teams
The inaugural franchises are recruiting. Find your community and define their strategy.
Amber Seekers
Beige Blockers
Crimson Strikers
Denim Drifters
Emerald Pausers
Fuchsia Soloists
The Founding Era
Era 1 — Protocols V1 through V9
The roadmap below reflects the current design intent. It will change — especially if a community forms and pushes in a more exciting direction. That's the point.
Learn the board → Build the organization → Author the world → Watch the world change around you
Spatial Literacy
Learn to see the board.
3v3 bots on a discrete grid. Deterministic movement, collision resolution, point zones, pathfinding, and replay inspection.
Commitment & Formation
Balance local superiority against global coverage.
Zone score multiplied by nearby friendly bots. Teams choose to swarm, screen, split, bait, or abandon — formation becomes a signature.
Bot Variability & Upgrade Draft
Adapt strategy to non-uniform personnel.
Introduce bot components and chassis traits. The first automated draft phase — teams write logic to evaluate and select upgrades.
Wear & Recovery
Manage reliability, risk, and limited maintenance resources.
Bots accrue wear from collisions and overuse. Recovery logic allocates limited repair actions across the roster between matches.
Roster Depth & Chassis Draft
Plan across a season instead of a single match.
Expand beyond active match bots. Backups, rotations, full chassis acquisition. Season arcs begin to matter more than isolated outcomes.
Automated Trading
Value assets in context.
Trade windows as scheduled phases. Team logic proposes, evaluates, counters, and accepts trades automatically — no manual approvals.
Scouting & Imperfect Information
Make decisions under uncertainty.
Spend limited scouting resources to reveal hidden traits. Draft and trade logic must reason from uncertain reports rather than perfect data.
Lore System
The community authors the world's story, and the world responds.
Community-submitted narrative events that touch real team state — bots, wear, draft records, trade history. The world gains memory.
Manufacturers — End of the Founding Era
The league has grown too big to ignore. Now the money arrives.
Robotics manufacturers have been watching. By V9 the league is popular enough that corporations begin developing advanced hardware specifically for it — pouring real money into designs that dwarf the humble prototype chassis the Founding Era was built on. The uniform bots of V1 are retired. The scrappy open-source experiment has become an industry. The Founding Era ends not as a patch note, but as a world event the community has been building toward.
The Multiview Experience
Monitor every match. Analyze every move.
Join the Community
Maintainer One is open source and community-driven. Whether you're a developer, a strategist, or a fan, there's a place for you in the league.