Advanced variables

Show another lobby, a single match, an earlier stage, or a specific slot on the same slide.

Plain variables follow the run you generated. To point somewhere else, add a prefix in front of the variable. Everything on the Variables page still works after a prefix, and slides without prefixes keep working exactly as before.

Three prefixes

Each prefix is optional. When you use more than one, keep them in this order: stage → lobby → match.

{{stage.S.lobby.L.match.M.rank.N.name}}

Prefix	Points at	Leave it out and it uses
`stage.S`	Stage S (the first stage is 1)	The stage you generated
`lobby.L`	Lobby L, all matches added up	The lobby you generated
`match.M`	Only match M (1–16)	The match you generated, or all matches when you picked a lobby

Build it up

Each line adds one piece to the one before it.

Variable	Shows
`{{rank.1.name}}`	1st place in the run you generated
`{{match.2.rank.1.name}}`	Match 2’s winner, same lobby
`{{lobby.2.rank.1.name}}`	Lobby 2’s leader across all matches
`{{lobby.2.match.3.rank.1.name}}`	Lobby 2, Match 3 winner
`{{stage.1.lobby.1.rank.1.name}}`	Stage 1, Lobby 1 leader across all matches
`{{stage.1.lobby.2.match.3.slot.4.player.1.kills}}`	P1’s kills for the team in slot 4, Stage 1, Lobby 2, Match 3

Three rules worth knowing

1. Picking a lobby means all matches

Even if you generated Match 3, {{lobby.2.rank.1.name}} ranks Lobby 2 across every match. Add match.3 after the lobby if you want only that match.

2. A stage needs a lobby

A stage can have several lobbies, so {{stage.1.rank.1.name}} is an error. Name the lobby: {{stage.1.lobby.1.rank.1.name}}. Stage details such as {{stage.1.name}} do not need a lobby.

3. Every scope is ranked on its own

rank.1 always means 1st place within the prefix. {{match.2.rank.1.name}} is whoever scored the most points in Match 2, which may not be the overall leader. MVP rank works the same way.

Place or slot: rank vs slot

rank.N means the team in Nth place. It changes as scores change. slot.N means the team that sat in slot N, wherever it finished.

Use slot for layouts where each card belongs to a fixed team, such as one tile per slot. It takes the same fields as rank, including players, logos, and flags.

Variable	Shows
`{{slot.4.name}}`	Team in slot 4
`{{slot.4.rank}}`	Where slot 4 finished
`{{slot.4.player.1.name}}`	Slot 4’s P1
`{{slot.4.logo}}`	Slot 4’s logo (images only)

Slot numbers

Slot numbers match the slots in your lobby list. If the stage’s slots start at 3, the first team is slot.3, not slot.1.

Details about other stages, lobbies, and matches

The stage, lobby, and match variables also take prefixes, so labels on your slide can match the data beside them.

Variable	Shows
`{{stage.1.name}}`	Stage 1’s name
`{{stage.2.lobby_count}}`	How many lobbies Stage 2 has
`{{lobby.3.name}}`	Lobby 3’s label
`{{lobby.3.team_count}}`	Teams on Lobby 3’s scoring tab
`{{stage.1.lobby.2.name}}`	Stage 1, Lobby 2’s label
`{{match.2.label}}`	`Match 2`

Pair them with scores

Axis Manager only reads the lobbies your slide pulls scores from. A label like {{lobby.3.name}} works when the same slide also shows something like {{lobby.3.rank.1.name}}. On its own, it can fail with “results are not loaded.” The stage and lobby you generated always work.

Tables with prefixes

In a table, the prefix goes on the row source, the second piece. The fields stay plain.

Lobby 2 standings, whatever lobby you generated:

{{data_row.2 | lobby.2.rank.1 | rank | name | total_points}}

A slot-order table, where each row is the next slot:

{{data_row.2 | slot.1 | slot | name | rank | total_points}}

Match 1 MVPs:

{{data_row.2 | match.1.mvp.1 | rank | name | kills | team.name}}

Table rules still apply

The row source is rank.N, slot.N, or mvp.N, with any prefix in front. One field per column, and no player, logo, or flag fields.

Images with prefixes

Images still take exactly one variable. Add the prefix in front:

{{lobby.2.rank.1.logo}}
{{match.2.mvp.1.flag}}
{{stage.1.lobby.1.slot.4.player.2.flag}}

Prefixes in Discord messages

Prefixed text variables also work in the dashboard’s attached message:

Lobby 1: {{lobby.1.rank.1.name}} · Lobby 2: {{lobby.2.rank.1.name}}

Ideas to start from

Finals recap with every lobby’s leader

{{lobby.1.name}}: {{lobby.1.rank.1.name}} ({{lobby.1.rank.1.total_points}} pts)

Duplicate the text box and change 1 to 2, 3, and so on.

Match-by-match winners

{{match.1.label}} — {{match.1.rank.1.name}}, MVP {{match.1.mvp.1.name}}

A look back at an earlier stage

{{stage.1.name}} winner: {{stage.1.lobby.1.rank.1.name}}

Before you generate

Every lobby you point at needs a synced scoring tab. Run /sheets update if one is missing.
Each extra lobby is one more sheet to read, so generating can take a few seconds longer.
Missing teams, players, or MVPs render blank, the same as plain variables.

Need every field in one place? See the variable reference.