Documentation

How To Use

Team: Pairing Engine
← Back to Command Centre

Purpose

The app is a team pairing workspace for Warhammer 40,000 events. It centralizes players, lists, force dispositions, opponent data, matchup matrices, pairing decisions, schedules, and reports.

Priority assets Recon Take and hold Purge the foes Disruption

Standard Workflow

Set up team access. Sign in, join or create a team, then work inside that team context.
Prepare players. Add players, maintain their lists, choose default lists, and record force dispositions.
Log individual games. Use Matchup Data to add standalone games with date, score, turn order, deployment, faction, force dispositions, and notes.
Prepare role options. Define player archetypes for defense, attack, and blunt roles, optionally with a force disposition.
Create the opponent game. Enter opponent players, factions, lists, and force dispositions.
Lock your roster. Pick 1 to 8 players for that game, freezing their default list information into the game snapshot.
Fill the matrix. Rate every player versus every opponent army before pairing.
Run the fight page. Assign games, terrain maps, expected scores, and real scores as the round progresses.
Review reports. Use saved scores and match history to evaluate performance over time.

Players & Lists

Use this area to manage the team roster and the information attached to each player.

  • Create managed players for testing or team preparation.
  • Add, edit, rename, delete, and view army lists.
  • Assign one of the five force dispositions to each list.
  • Choose a default list used when locking a game roster.
  • Open a player profile to review lists and match history.
  • Add detailed individual game history from Matchup Data, or from a player profile when already viewing that player.
  • Captains can delete players; player access can use the team tools except player deletion.
Players & ListsRoster and list management Matchup DataIndividual game logging

Matchup Data

Use this page when you want to add a single game quickly without opening a player profile.

  • Choose the player from a dropdown, then select their list when known.
  • Select opponent faction from the controlled faction list.
  • Record game date, 0-20 score, whether you had turn 1, deployment, opponent level, and both force dispositions.
  • Add optional opponent name, event context, and notes for later review.
  • Filter the recap table by player, faction, result, score range, turn 1, deployment, and force dispositions.
  • Use the filtered summary to compare average score, winrate, and turn-order impact before deeper matchup stats are built.
Matchup DataManual MU data capture

Roles & Archetypes

Use archetypes to prepare roster proposals before a game is created or before final player selection.

  • Each player can define up to 3 archetypes.
  • Each archetype has a faction and a role: defense, attack, or blunt.
  • A force disposition can be proposed on each archetype.
  • Drag archetypes into the 8 roster slots to build a lineup proposal.
  • Save the proposal locally in the browser.
  • Send the proposal to Discord when a webhook is configured.
Roles & ArchetypesRole deck and proposal board

Create Game

Create a game when you know the opponent team or opponent player group.

  • Set the opponent or team name.
  • Add between 1 and 8 opponent armies.
  • For each opponent army, enter player name, faction, force disposition, and list text.
  • Factions must be unique inside the same game.
  • The game becomes available in Saved Games for matrix and fight work.
Create GameOpponent setup Saved GamesOpen existing games

Matrix

The matrix is where the team rates every matchup before selecting pairings.

  • Lock 1 to 8 players into the game roster before matrix work. Smaller rosters are supported for testing.
  • The roster snapshot stores player name, default list, list text, and force disposition.
  • Rate each matchup with the available states: HELP, LOOSE, S_LOOSE, GAMBLE, UNKNOWN, S_WIN, WIN, EASY.
  • Save matchup notes for the game.
  • Terrain maps are no longer chosen from a scenario layout list; they are selected during Fight pairing from the two force dispositions in each matchup.
  • Use the optimizer endpoint to evaluate ideal assignments when the matrix is complete.

Fight Pairing

The Fight page is used during the pairing process and when recording final results.

  • Assign defenders, attackers, refused attackers, and leftover pairings through the 8 game slots.
  • After each matchup is selected, choose one of the 3 terrain map options generated from your force disposition versus the opponent force disposition.
  • Until real terrain images are uploaded, the app displays deliberate placeholders for those 3 map options.
  • Use saved matrix states to show expected scores for every pairing.
  • Use the assistant to generate pairing suggestions from the current round state.
  • Record real scores, compare expected versus real, and keep a complete round summary.
  • Fight changes auto-save after edits, with a manual save control still available.

Reports

Reports turn completed game results into player-level performance tracking.

  • Review games played by each player.
  • Compare real score against expected matrix score.
  • Track average score and average delta.
  • Inspect details by opponent, faction, force disposition, terrain, state, and score.
  • Use Matchup Data for standalone game history outside formal team games.
ReportsPerformance analysis Matchup DataFiltered standalone games

Calendar

The calendar tracks preparation windows and team availability.

  • Create availability entries for players.
  • Track scheduled sessions or game-related events.
  • Attach calendar items to players or games where relevant.
  • Use the calendar view to coordinate prep over the next planning window.
CalendarAvailability and sessions

Team & Integrations

Team settings control shared access and communication tools.

  • Join an existing team by password or create a new team as captain.
  • Switch active team when your account belongs to multiple teams.
  • Configure the Discord webhook used for roster proposals and team notifications.
  • Test webhook delivery before relying on Discord notifications.
  • Site admins can manage users, teams, and memberships from the admin panel.
Team AccessJoin, create, switch Team SettingsWebhook and team tools

Important Notes

Authentication

Most operational pages require an authenticated account and an active team. This documentation page is available before login.

Snapshots

When a roster is locked for a game, player list data is copied into the game. Later list edits do not rewrite that game snapshot.

Force Dispositions

Force dispositions exist on player lists, opponent armies, archetype proposals, and match history. Keep them updated before roster lock.

Terrain Images

The Fight page reads 3 maps per force-disposition matchup from data/terrain using names like Take-and-Hold_vs_Reconnaissance_Layout-A.png.