Scoring reference
Counter-Battery Challenge: how does the leaderboard score work?
Counter-Battery Challenge scores kills by target star rating, so leaderboard points can be higher than your kill count.
Quick answer
Leaderboard score is not a flat kill count: an unstarred kill gives +1, then each star adds one point up to +6 for a 5★ kill. Requisition is a separate combat-resource calculation and is not the leaderboard score. Destroying an FDC suspends the Counter-Battery Timer and can create planning time, but it is not documented here as a direct leaderboard-point award.
Use the scoring model in a run
Step 1 — Plan before the first impact
The structured Challenge briefing says counter-battery pressure begins once the first shell lands. Identify initial targets, prepare firing data, and decide on the first firing sequence before that impact to preserve your untimed preparation window.
Step 2 — Think in score value, not kill count alone
Use the Challenge star-weighted table when comparing targets: a higher-star kill contributes more leaderboard points than an unstarred kill. This does not mean low-star targets should always be ignored.
Why did 20 kills give 27 points?
Because Challenge kills are weighted by star rating, kill count and leaderboard score do not have to match. The long-running Steam discussion began with a Demo-era 20-kill / 27-point result, which is consistent with non-flat scoring. That historical observation does not verify the current exact star table; the values on this page come from the current structured Challenge snapshot.
Step 3 — Keep leaderboard score and requisition separate
Leaderboard points are used for Challenge scoring and ranking. Requisition belongs to the combat resource economy used to obtain assets. The structured mission data lists them separately, so do not assume target requisition rewards equal leaderboard points or that saving requisition directly raises the leaderboard score.
Step 4 — Use FDCs as planning pauses
Current structured Challenge data specifies AP for the underground Fire Direction Centers and says destroying an FDC suspends the Counter-Battery Timer. Treat an FDC as planning-time control: use the pause to regroup and prepare the next firing sequence. An FDC is not documented here as a direct leaderboard-point award.
Step 5 — Re-plan instead of promising one fixed score
Community high-score strategies discuss target clusters, keeping both guns working, reconnaissance choices, efficient volleys, and FDC pauses. These are community-observed planning ideas rather than the scoring contract, a fixed optimal route, or a guarantee of 50 points.
Counter-Battery Challenge leaderboard points
This table applies to Counter-Battery Challenge leaderboard scoring only. Exact timer values, time-sensitive leaderboard placements or top scores, spawn patterns, coordinates, medal thresholds, and fixed high-score recipes are intentionally not published. The current star table comes from a current independent fan-run structured Challenge snapshot, not official developer documentation, and still needs independent full-release human reproduction.
Avoid these scoring mistakes
- Treating leaderboard score as a flat kill count.
- Mixing leaderboard points with requisition income or spending.
- Treating an FDC pause as a direct leaderboard-point bonus.
- Copying one community firing sequence, loadout, reconnaissance choice, or target layout as universally optimal.
- Reading a 50-point search phrase or a historical leaderboard example as a guaranteed current result.
Why score and kills diverge
The current independent structured Challenge snapshot directly lists the six star-weighted leaderboard values and separately lists requisition rewards. It also documents first-impact counter-battery activation and FDC timer suspension. The active Steam thread establishes continuing demand and supplies a Demo-era 20-kill / 27-point example that is historically consistent with weighted scoring; it is not independent full-release verification of the exact current table. Community players also report that target layout can make some high-score runs easier than others, but this page does not quantify that variation or publish a maximum score.
Challenge scoring table documentedCurrent-build limitsChecked Aug 14, 2026
Current structured Challenge data lists star-weighted leaderboard points from +1 for unstarred kills through +6 for 5★ kills and separately defines requisition rewards. The mission briefing also documents first-impact counter-battery activation and FDC timer suspension. The exact scoring table has not been independently reproduced in a full-release human test.
Version context: Current independent structured Counter-Battery Challenge snapshot reviewed Aug 14; exact leaderboard table is structured-data derived, while full-release independent human verification and optimal high-score strategy remain unresolved
Still uncertain
- Independent full-release reproduction of every star-value entry
- Optimal target-selection strategy
- Run-to-run target layout impact on attainable score
- Maximum practical score in the current version
- Whether future balance changes alter the table
- Exact timer values, which are intentionally not republished
Evidence and verification context
- Current structured Counter-Battery Challenge data: The independent current Challenge snapshot directly lists leaderboard points per kill as +1 unstarred, +2 at 1★, +3 at 2★, +4 at 3★, +5 at 4★, and +6 at 5★. It separately lists requisition rewards and records that the first shell landing begins counter-battery pressure and FDC destruction suspends the timer. The source is fan-run rather than official.
- Active Counter-Battery Challenge score discussion: The long-running Steam thread continues to surface current demand around leaderboard scoring and high-score strategy. Its original 20-kill / 27-point example was posted during the Demo period, so it is retained as historical consistency and user-intent evidence rather than full-release verification of the exact score table.