> For the complete documentation index, see [llms.txt](https://theluckyducks.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://theluckyducks.gitbook.io/docs/competition/tournaments.md).
# Tournaments
A scheduled event where teams compete for one pot. What counts, how it is scored, and who gets paid.
A scheduled event where **teams** compete over a fixed window for a single pot. No sign-up, no entry fee: you race as usual, and the races your [team](/docs/competition/teams.md) runs inside the window count toward its standing.
One runs at a time, and its page shows the window, the rule it is scored on, the pot and the live standings. While it is running, a countdown headed **Ends in** shows the days, hours, minutes and seconds left.
{% columns %}
{% column width="70%" %}
The window, the rule and the pot, all on one page.
{% endcolumn %}
{% column width="30%" %}
On a phone
{% endcolumn %}
{% endcolumns %}
## What counts
A race counts when it finishes inside the window and meets that tournament's conditions, which its page lists:
* The race has to start after the tournament does. One created earlier does not count even if it settles during the window.
* If the pot is in a token, only races using that token count.
* A team may need a minimum number of members to qualify at all.
* Sponsored races are either included or excluded.
{% hint style="info" %}
Only races finalized on chain count. One still in its lobby, waiting on randomness or mid-run counts for nothing until it settles.
{% endhint %}
## Scoring
Every rule is a **per-player average**, so size alone wins nothing: 10 members racing once each score exactly what 1 member racing 10 times scores.
| Family | Scored on |
| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Wins, races, XP, SOL volume, token volume, podium finishes | The average per member, one rule per metric |
| Weighted | Average wins at 60 percent plus average races at 40 percent |
| Duels | Points from 1v1 rematches, doubled against another team or a solo racer |
| Worst results | Two rules: races not won, or last places, at 60 percent plus races run at 40 percent. Losing counts, and so does taking part |
| Creators | Most completed races created per member |
| Biggest races | Bigger lobbies score more, with a bonus for a mixed lobby |
| NFT and token rules | Races per member, where races using a Boost, a Cosmetic, or the tournament's paired collection or token count twice |
The first family carries a **diversity bonus**: 10 percent per outside team or solo racer you meet, averaged across your races, so racing only your own members scores least. The other rules already account for outside play and take no bonus.
A tie on the score is broken by the rule's second figure per member, the higher first: races run under the rules about wins, losses, last places, duels, creators, biggest races and the NFT and token rules, and wins under the others. Teams level on both are separated by which team was created first, then by a fixed seed. No shared places.
A tournament can also carry a third worst-results rule, most last places per member with nothing for the races run. No new tournament is created with it.
The [jackpot](/docs/competition/jackpot.md#what-you-are-ranked-by) ranks single players by the same rules.
## The pot and who gets it
The platform funds the pot when it creates the tournament, in SOL or a [supported token](/docs/economy/spl-tokens.md), and nothing is added later.
The **winning team takes all of it**, split equally between its members. No second or third place. A pot that will not divide exactly leaves a tiny remainder, and the first winner in the list gets it.
A platform fee comes off the pot before the split, set per tournament and never above 10 percent. A tournament pot pays no [jackpot fee](/docs/economy/fees-and-prizes.md#the-jackpot-fee). The races played in it do, like any other.
{% hint style="success" %}
Standings are computed off chain, which is what lets a rule change between tournaments without touching the program. The platform writes the team at the top of those standings as the winner, scored on the tournament's rule and counting only teams that meet its minimum size, and refuses to write any other. From that point the payout is the program's to make and nobody can alter the list.
{% endhint %}
## Claiming
One claim pays every winner, so the first of you to press Claim settles it for the whole team. With [playing without signing every action](/docs/races/delegated-play.md) on, the platform can send it for you, and the confirmation says what that takes from your vault before you agree. See [What it costs](/docs/races/delegated-play.md#what-it-costs).
Whoever sends it, the money goes to the winners and to nobody else. Paying the fee entitles the sender to nothing.
The button shows your share and what it is worth. While the tournament runs that dollar figure follows the market; once it ends the figure is fixed at the rate when it ended, so what you won does not appear to drift afterwards. A tournament that ended with no usable price shows the amount alone.
One claim pays the whole team, whoever sends it.
### A large team is paid over several transactions
When the winning team is too large for one transaction, the claim pays it in several, each covering the next group of winners in list order. Your share can therefore land a little before or after a teammate's, and every share is the same amount it would be in one go, remainder included.
If the claim stops part way, because a transaction failed or you closed the page, its progress stays on chain. The next claim, from you, a teammate or the platform acting for one of you, picks up at the first winner not yet paid. Nobody can be paid twice: a transaction resent after it landed is refused, and once a claim has started paging, only continuing it can pay anyone.
The first transaction opens a small account that tracks the progress. Whoever sends it pays that account's rent, the small SOL deposit Solana requires to keep an account open, and gets all of it back when the last transaction closes it.
On a SOL pot, the winners still waiting sometimes have to be paid together in one last transaction: Solana will not leave the pot's account holding a leftover smaller than that deposit, and paying everyone left empties it instead. If your wallet cannot sign a transaction that large, the claim stops before you are asked to sign anything more and says so. Nothing is lost: a teammate whose wallet supports larger transactions can finish it, and so can the platform acting for one of you.
{% hint style="success" %}
The platform fee comes out on the last transaction, after every winner has been paid. A claim that stalls part way never leaves the platform paid and the team waiting.
{% endhint %}
Each winner's share goes where that winner chose to receive winnings: their wallet, or their [vault](/docs/economy/player-vault.md#where-your-winnings-land). The choice is per player, so a team can be paid to both in one claim, and nobody starting the claim can change it for a teammate.
On a SOL pot, a share too small for Solana to credit to a wallet holding no SOL at all is held back rather than sent. See [Refunds and rent](/docs/economy/refunds-and-rent.md#very-small-sol-payouts) for what happens to it.
## Your team is frozen while a tournament runs
{% hint style="warning" %}
From the start to the end of a tournament, no team can change. See [Teams](/docs/competition/teams.md#teams-are-frozen-while-a-tournament-runs) for what that covers and why.
{% endhint %}
So build or join your team beforehand. While one is running those buttons stay disabled.
{% content-ref url="/pages/riAtRcbVGvV4DYJmHetR" %}
[Teams](/docs/competition/teams.md)
{% endcontent-ref %}
