MATCH TICKER
HLLCS // HOW IT WORKS
← Back to League
[03] INTEGRITY

Match Verification & Integrity

How matches are confirmed, what gets checked, and how flags are reviewed.

//

How a Match Gets Confirmed

Standings, ratings, and medals only update after an official confirms the match. Every scheduled match has a set kickoff time, a Vietnam map and midpoint (one of 3 per map), opposite factions (US and NVA), and a registered match server.

At kickoff the match shows as live, and after 2 hours it moves to in review so delayed streams are not spoiled. An official then pulls the completed scoreboard from the match's CRCON server—or enters the match stats link for a Bifrost server—reviews the score and automated checks, and confirms the result.

//

What Gets Checked

Every player in the match is checked by their 32-character EOS ID and console platform before the result can be confirmed.

CheckWhat it catchesNeeds a log key?Result
Unrostered player (ringer)A player whose EOS ID is not on an active league roster.NoHolds the match
Wrong roster (multi-team)A player whose EOS ID is on a different team's active roster than the side they played for.NoHolds the match
PC platformA player whose platform on the scoreboard is not Xbox Series or PS5.NoHolds the match
Mid-match side swapA player who played on both sides during the match (from scoreboard unit history).NoHolds the match
Admin or spectator cameraAnyone entering admin camera during the match window who is not an approved caster assigned to that match.Yes (or log upload)Holds the match
Map mismatchPlayed map does not match the scheduled map.NoWarning
Missing platform dataScoreboard data did not include platform information for one or more players, so the platform check did not run for them.NoWarning
Missing logsNo server logs were available for the match window, so the admin camera check did not run.—Warning (blocks confirm until logs attached or signed off)

Roster, ringer, platform, and side-swap checks read EOS IDs, platform tags, and unit history directly from the public scoreboard and do not need a server log key. Approved casters are exempt from ringer, wrong-roster, platform, and camera checks only on matches they have claimed and been assigned to cast.

//

Missing Logs

When server logs are missing, the match cannot be confirmed until an official either attaches a log file or signs off with a written reason on the public match record.

Without server logs, the roster, ringer, platform, and side-swap checks still run normally, while only the admin camera check does not run. Bifrost match links include full public scoreboards (including unit history for side-swap detection) but do not include raw server event logs, so Bifrost captures show the missing logs warning unless a compatible log file is uploaded.

//

Server Keys

Providing a server key is optional. On CRCON servers, hosts grant one CRCON permission: “Can view historical logs”.

The league never connects with admin permissions: Scoreboards and live stats are read from public endpoints, the key is used only to read historical match logs, and the league cannot kick, ban, message players, or change server settings. Server owners can rotate or remove their key at any time without affecting past matches.

//

When a Match Is Flagged

If a match triggers a check that holds the result, it is marked disputed and does not count toward standings or ratings until an official resolves every flag.

For each flag, an official reviews the evidence and records a written decision on the match page—either upholding a penalty or dismissing the flag (for example, if a late roster submission was already in the queue). Once every flag is resolved, the match is confirmed and all standings, ratings, and medals update.