Scoring and Falcon Tickets
Leaderboard Looters treats the server as the authority for scoring. The browser can display an attempt and a provisional result, but leaderboard totals come from accepted server-side scoring records.
Challenge results come first
Tickets are a consequence of completing a challenge under its scoring rules. A page view, login, advertisement impression or advertisement click is not a scoring event and must not directly increase the ticket total.
Append-only ticket history
Accepted ticket changes are represented as new ledger entries. This makes it possible to reconstruct how a total was reached instead of relying on a single editable number with no history behind it.
Unlimited totals
There is no artificial per-player ticket ceiling in the scoring model. If a player continues earning accepted scoring entries, their total can continue to increase.
Duplicate protection
A properly recorded challenge attempt has its own source identity. The backend can use that identity to prevent the same accepted result from being counted repeatedly simply because a request was retried or a page was refreshed.
Leaderboard ranking
The leaderboard is built from server-side totals. Where players are tied, the game can apply defined tie-break information rather than randomly choosing who appears first.
Administrative adjustments
If an administrator needs to correct a genuine scoring issue, the safer model is to append an adjustment with an audit reason rather than overwrite history. That preserves visibility into what changed and why.
What event score is not
Falcon Tickets are not legal tender, cryptocurrency, stored value, a cash balance or a redeemable prize. They exist only as scoring units inside Leaderboard Looters.