---
title: Scoring
description: How attack, defence and SLA points are earned in an attack/defence event.
---

Scores are committed at the end of every tick, separately for every flag store of every service. Your total is the sum over every service, store and tick. The **Scoreboard** shows each team's total and, per service, its latest status and three point streams, with a history per service.

The numbers below are the defaults; organizers can change the weights before the game starts. The organizer guide's [scoring reference](/organizers/attack-defence/reference/scoring) has the full formulas.

## SLA

Each tick a store is **Up**, you earn 3 points. **Recovering** earns 1.5. **Down**, **Faulty** and **Flag missing** earn nothing.

## Defence

A store earns defence for a tick when the checker placed this tick's flag in it, the store earned SLA, and nobody stole that store's live flags during the tick. The points are `2 + 1 / d`, where `d` is the number of teams that earned defence on the same service and store that tick.

A service that's down earns no defence, so switching a service off never protects you.

## Offence

The scoreboard calls attack points **Offence**. Each distinct flag you steal and submit earns `1 + 1 / f + 1` points, where `f` is the number of teams that submitted that same flag during the tick. Being the only team to steal a flag pays the most.

Some events reduce the points for stealing from teams ranked below you. When that's on, the reduction grows with the distance between the two teams on the scoreboard at the end of the previous tick.

## When a flag counts

A flag counts in the tick you submit it, not the tick it was placed in. Submitting the same flag twice scores once. A capture never changes a tick that has already been scored.

## Status precedence

When several checks ran on a store in one tick, the worst current result decides its status: Down, then Faulty, then Flag missing, then Up. A store whose current checks pass but that failed a check about an earlier, still-valid flag is **Recovering**.

A service caught answering the checker on one of its ports while refusing every other player there scores **Down** in every flag store for that tick.

While your box is being restored, every flag store on it earns no SLA and no defence in each tick the restore overlaps, until the box is healthy again. Captures are unaffected. See [Defend your box](/players/attack-defence/how-to/defend-your-box#restore-from-the-snapshot).

## Pauses

The organizers can pause the game, and the platform pauses it on its own when it can't check services fairly, for example when it loses contact with the event host. While the game is paused no tick runs, nothing is scored, and flags are answered `Game not running, try again later`. The paused time doesn't count against your services when the game resumes.
