Match Score, MVP, and Leaders¶

Quick Start: Pick your goal.

• Every participant earns an integer match score: kills, objectives, survival, movement, and teamwork add to it, while deaths, idling, and friendly fire subtract.
• At match end two titles are decided from it: MVP goes to the top scorer match-wide, and leaders are picked per team for actually leading. This page explains both, plus every scoring category.

MVP vs Leader in One Minute¶

• MVP (one per match at most) rewards doing the most. Highest final match score at or above 120 wins, hunters and runners competing together. Kills, objectives, survival, rescues: all of it counts the same way, through the score total.
• Leader (one per team at most, so zero, one, or two per match) rewards leading. It ignores the score total and measures the trail instead: how many meters of your route teammates walked after you. A scout who blazes the path the team follows can be leader with a modest score, while the top fragger who never led anyone cannot.

The differences that matter:

• Scope: MVP is match-wide; leaders are one hunter and one speedrunner. The summary panel shows the winning team's leader.
• Metric: MVP reads the final score; leader reads followed meters.
• Count: MVP needs 120+ points and may be nobody; each side may independently have no leader.
• Reward: MVP is a title and pays no points. Leader pays +150 on the winning side or +75 on the losing side, added before the MVP pick, so leading can tip the MVP race.
• Presence: MVP can go to someone offline at the end (their score stands). Leaders must have been there the whole match and be active at the end, or nearly (see below).

How the Score Adds Up¶

• Scores start at 0 and add up per category below; several kill, death, and damage awards can land on the same event (a first-blood elimination pays both).
• At runtime totals can dip negative, but saved snapshots, career folds, and placeholders floor at 0.
• At match end the engine applies leader awards first, then the end of match categories, and picks the MVP last over final totals.

Kills¶

Deaths¶

Damage¶

Doom marks the attacker who drops a player below 3 hearts, lasts 15 seconds, and never clears on healing; killing that attacker while the teammate lives pays the save.

Blocks¶

Objectives¶

Movement and Behavior¶

Sampled every 5 seconds for online participants:

Match Flow¶

Quitters who never come back keep both the disconnect mark and the rage quit penalty.

End of Match¶

• The win award and the strength adjustments go to the winning side only; the never-damaged and never-killed penalties hit every participant who earned them.

How MVP Is Picked¶

1. Totals finalize: leader awards and end categories land first.
2. Every participant with 120+ points qualifies, online or not.
3. Highest total wins. Ties break toward speedrunners, then more eliminations, then fewer deaths, then the alphabetically first name, so every ranking is deterministic.

4. Nobody at 120+ means no MVP and no bullet.

5. The pick (player plus score) stores in match history, so later scoring tweaks never rewrite who won it. The title itself pays no points.

6. Mid-match views differ on purpose: the match_mvp placeholder names the live top scorer from 1 point up with no threshold, while the <mvp> tag needs the full 120 and an in-game player, falling back to the runner-up and then null (see Tags: Basics).

How Leaders Are Picked¶

Each side awards at most one leader: the hunter leader and the speedrunner leader are decided independently, and either side may have none. Teams whose peak size stayed at one never award one.

Eligibility¶

• On the team the whole match: joined before it began and never left mid-match. Late joiners and leavers are out.
• Active at the end, or alive for at least 90% of the match duration (alive time accrues per 5 s poll while online as a participant).

The Trail Metric¶

Positions sample every 5 seconds into an 8 m grid per team and dimension:

• The first teammate to walk a cell while genuinely progressing claims it with their position, time, and heading.
• Teammates who walk the same ground later credit the owner with the meters they followed.

• The lead score sums those meters over followers, capped at 500 m per follower so one shadow cannot carry the score:

• A follow needs lag between 5 seconds (side-by-side walking is cooperation, not leading) and 10 minutes, with full credit to 3 minutes and linear decay after.

• Headings must roughly agree (dot product 0.5+), which throws out crossing paths and hunters converging from all sides.
• The follower must land within 10 m (3D) of the claimed spot, and each follower, owner, and cell triple credits once, so revisits never farm.
• Portal routes and dimension changes credit double.

Anti-farming keeps the honest cases: cells claimed standing still (12 idle samples), within 40 m of the start or a respawn, or without 20 m of net displacement in the previous 60 seconds never become claims. Teleport jumps cap at 150 m per sample.

The Award¶

• The eligible candidate with the top lead score wins when the score reaches 400 followed meters with enough distinct followers: at least one, or two on teams that peaked at four or more.
• Ties break toward more distinct followers, then the better follow ratio (followed meters over own travelled meters), then whoever reached 400 m first. Winners pay +150, losers +75, added before the MVP pick.

Tuning¶

Every number on this page ships in the internal match-score.yml bundle: awards, thresholds, windows, radii, and caps. The file lives in the jar, never copies to the data folder, and stays out of the settings GUI. Invalid values repair to their defaults with a warning on load.