Skip to content
Athena User Guide
Esc
↑↓navigate↵open⌘Jpreview
On this page

Designing your scoring

Choosing scoring methods, attempt limits, cooldowns, and hint penalties for a fair event.

Scoring is the incentive structure of your event: it decides what a solve is worth, whether speed matters, and how much risk a guess or a hint carries. The challenge editor reference documents each control; this page is about choosing between them.

Pick a scoring method per challenge

Static (Fixed Points) is the simplest contract: the challenge is worth what it says, first solver and last. It’s the right default for beginner-friendly events, training sessions, and any event where you want the scoreboard to read as “challenges solved” rather than “challenges solved early.” Its weakness is calibration: you have to price difficulty yourself, and a mispriced challenge stays mispriced.

Solve Rate Based (Decay per solve) lets difficulty price itself. Every solve multiplies the value by 1 − decay/100, so a challenge everyone cracks slides toward its minimum while a hard one keeps its value, even if you guessed its difficulty wrong when authoring. This self-calibration makes it the usual choice for competitive events. The trade-off: players solving early watch “their” challenge lose value for later solvers, so the scoreboard rewards both solving and solving popular challenges early. The Player Guide explains this dynamic from your players’ side.

Time Based (Decay over time) decays by days elapsed instead of solves, continuously, whether or not anyone solves. Use it when you want urgency itself rewarded. Two cautions from how it actually behaves:

  • An untouched challenge decays too; in a long event a hard challenge can be near its minimum before anyone cracks it, muting the reward for the eventual breakthrough.
  • The decay clock starts when the challenge is created, not when the event starts or the challenge releases. Author time-based challenges close to their moment, or use solve-rate decay for anything prepared in advance.

Whichever decay you choose, set Minimum Points deliberately: it’s the floor that keeps a swarmed challenge from becoming worthless, and the gap between initial and minimum is the total amount of “earliness” you’re rewarding. A gentle setup keeps the minimum at half the initial value; a cutthroat one lets it fall to a token amount.

Bloods are the cheap incentive

The first, second, and third solves of each challenge are marked on its page for everyone to see, and the bot can announce first bloods to your Discord server the moment they land (/setup with First blood feed in the channel you want; see Discord bot commands). Bloods cost you nothing and don’t touch the math, but they create the race: teams push on fresh challenges for the public credit, not just the points. Pair decay scoring with visible solves (Show user solves) and the incentive compounds: players can see a challenge being solved down in value.

When to cap attempts

Unlimited attempts is the right default: most flags are effectively unguessable strings, and a wrong submission already costs time. Turn on an Attempt Limit when the answer space is small enough to brute-force: flags that are a date, a name, a short number, or one-of-N formats. The limit is enforced per team, so it can’t be reset by rotating submitters; players see their shared count as “Team attempt N / M”.

Keep limits generous (typo room included); a tight limit turns one fat-fingered paste into a locked-out team, and there’s no way to reset attempts for them mid-event. Separately from the wrong-answer cooldown you configure, the platform enforces a rate limit on rapid-fire submissions: a player hammering the flag input is paused with “Too many attempts. Try again in N seconds.” So raw brute-force is throttled on every challenge regardless of your settings.

Pricing hints

A hint’s Penalty is deducted when it’s revealed, so it’s really the price of a partial solution, and players confirm a dialog before paying it, so nobody stumbles into the cost. Three pricing patterns work well:

  • Free (0 points) for clarifications and scope notes, the things you’d otherwise answer in tickets all night.
  • Cheap (5–15% of the challenge’s value) for a nudge on approach.
  • Expensive (25%+) for a hint that meaningfully unlocks the solve, where the player trades standing for progress.

Order hints from vague to specific: players reveal them in sequence, and the escalating cost lets a stuck team buy exactly as much help as they need. Price against the challenge’s minimum value under decay, not the initial value; otherwise a late hint on a decayed challenge can cost more than the solve pays.

A starting recipe

For a typical competitive event: solve-rate decay on everything, decay factor tuned so your expected solve count lands challenges near ⅔ of initial value, minimums at 25–50%, attempt limits only on guessable formats, one free clarification hint plus one or two priced ones on the hardest tier, and Show user solves on. Then let the freeze settle the argument.

Was this page helpful?