DUEL MASTERS LEAGUE

League Operations Core

Run the league.
Not the
spreadsheet.

Duel Masters League is more than a tournament website. It is the live reference implementation of a reusable operating platform for registrations, seasons, matches, standings and competitive history.

Explore the live leagueTalk to the operators
Reference tenantUT Duel / Season 04Core v0.1 · active development
Operating flowOne source of competition truth
  1. 01Application
  2. 02Entry
  3. 03Schedule
  4. 04Result
  5. 05Standing
  6. 06History
Reversible migration Versioned rules Public projections

One connected workflow

From first signup
to final record.

The platform connects the work that community organizers usually spread across forms, spreadsheets, bracket services, chat messages and hand-edited pages.

01Season operations

Define the season

Set regions, divisions, capacities, registration windows and competition rules without rebuilding the public site.

02Registration Desk

Intake and review

Collect applications, approve players, move entries between divisions and manage waitlists from one operational queue.

03Competition Center

Run every stage

Generate groups and schedules, publish results and progress qualified players from round-robin into playoffs.

04Public projections

Publish the record

Project standings, ratings, statistics and final placements into a stable public competition history.

Universal by design

One core.
Many competitions.

Game logic, tournament formats and visual identity are separate layers. Organizers can change the competition without forking the operational foundation.

01
CORE

League Operations Core

Organizations, participants, seasons, divisions, entries, registrations, matches, results, standings and audit events.

02
FORMAT

Tournament modules

Versioned round-robin, elimination, Swiss, ladder and group-to-playoff logic with deterministic progression.

03
RULES

Game rules modules

Game-specific scoring and validation stay modular, so one operating model can serve different competitive games.

04
BRAND

Presentation layer

Every league keeps its identity, content and public experience while the operational machinery remains reusable.

Built in public

UT Duel is the
proving ground.

Season 4 is the first full operational case being built: four branded leagues, two regions and one public arena. Every live requirement hardens the reusable Core instead of creating another isolated tournament site.

Open the Registration Desk
Current reference experience06 connected surfaces
  • 01Registration and administrator review
  • 02Regional divisions and capacity control
  • 03Group matrices and playoff stages
  • 04Published scores and result corrections
  • 05Season rating and player statistics
  • 06Hall of Fame and permanent history

Product principles

Operational first.
Safe to evolve.

01

No code edits on match night

Season operations belong in administrator workflows, not source files or ad-hoc JSON.

02

History stays reproducible

Rules and published results are versioned so archived seasons do not silently change.

03

Migration stays reversible

Each operational slice moves through parity checks and independent read/write cutovers.

Platform direction

Built for one league.
Designed for the next.

UT Duel remains the reference league while the Core becomes a reusable foundation for community seasons, cups and ladders across competitive games.

See it operatingDiscuss the platform