1. 1

   Watch live

   Open the Captain's Helm Twitch channel when Skirmish is running.

2. 2

   Connect wallet

   Sign in on the site so weekly standings can attach to your captain.

3. 3

   Link Twitch in Papers

   Link Twitch through Captain's Papers before battle end to earn website points.

4. 4

   Join a fleet

   In chat lobby, join Blue or Red before combat starts.

5. 5

   Pick Fire, Brace, or Patch

   Each tick lasts 22s — submit one command for that window.

6. 6

   Replace if you must

   Up to 2 same-tick replacements; the last accepted action wins.

7. 7

   Battle resolves on stream

   Up to 3 rounds × 4 ticks; victory by hull or max rounds.

8. 8

   Climb the weekly board

   Eligible battles score into the week; seasons reset Thursday 16:00 UTC.

The website never hosts the live match. Join fleets and issue commands in Twitch chat.

Fire

Deal damage to the opposing fleet

Aliases: shoot, cannon

Brace

Reduce incoming damage

Aliases: block, defend

Patch

Restore hull

Aliases: repair, mend

You may replace your action up to 2 times on the same tick; the last accepted action wins. Replacements do not add extra active ticks.

• Lobby lasts about 120s — join Blue or Red before combat starts.
• Combat runs up to 3 rounds × 4 ticks. Each tick is one volley.
• Each fleet shares 1000 hull and the same base 120-power tick budget across Fire, Brace, and Patch, regardless of crew size.
• A fleet at 0 hull sinks. An undefended fleet can be sunk, so Brace and Patch are what keep a fleet in the fight.
• Victory comes from hull advantage or hitting the max-round limit.
• If the opposing fleet has no human, Training Crew may answer — bot-assisted scoring at 25% for the first 50 Training Crew matches/week.

That 120 is shared fleet power, not 120 per player or per command. More viewers do not multiply the budget; their orders decide how it is split. Players who choose the same action share that action's resolved contribution — another Fire is not another full 120-power volley. A solo fleet that only Fires spends its full base budget on Fire; two Fire commands on the other fleet share one Fire result.

Match week is determined by battle end time (UTC), not when the site receives the payload.

• Each match selects Storm, Powder Barrels, or Salvage when the battle lasts long enough.
• The first two volleys are ordinary combat.
• Volley 3 warns both fleets.
• Volley 4 receives the effect, for that volley only.
• Both fleets face the same event.
• Use !fire, !brace, or !patch. There is no extra event command.
• If the battle ends before that volley, the event does not happen.

A percentage raises that order's power. It does not guarantee extra hull damage or healing. Randomness, critical hits, and action failures still apply.

• +5 Active
• +2 per active tick (Engagement)
• Impact capped by active ticks and effective contribution vs action power
• +4 / +2 / +0 Versatility for three / two / one action types
• +5 Victory if your team wins
• Fleet Sunk: +3 points when your fleet sinks the opposing fleet and survives. Awarded to eligible, active players on the winning fleet in human PvP, in addition to +5 Victory points.

Impact is capped by active ticks and effective contribution vs action power.

Wasted rolls, critical luck, and replacements do not add direct points.

No Fleet Sunk points for a remaining-hull or round-limit win, a simultaneous sink decided by tie-break, or a Training Crew battle.

Fleet Sunk is a fleet result. Eligible active players on the winning fleet qualify, including Brace and Patch. A storm sink qualifies the same way, and storm damage is not player damage.

Current scoring rules apply to new match awards. Earlier match scores stay unchanged.

Human PvP awards full score. Bot-assisted battles (Training Crew when no human joins) award 25% of that score for the first 50 scoring Training Crew matches each week — still eligible for the weekly board.

Link Twitch through Captain's Papers before battle end to earn weekly points. Identity uses your stable Twitch provider ID — never display names typed in chat.

Unlinked captains can still play in chat. They simply do not appear on the weekly site board.

• Pool: 10,000 RUM + 100,000 WAVES (config-versioned)
• Share scales with your eligible points vs the week's eligible total — no guaranteed minimum
• Total points include bot-assisted awards (25% · first 50 Training Crew matches/week); same RUM/WAVES pools as PvP
• RUM is paid manually after the week finalizes (not auto-transferred while projected)
• WAVES arrive on Twitch via ParrBot !tip / ScurvyBot after finalization

Projected shares update during the week; final shares lock after settlement. Leaderboards label Projected vs Final from the API.

Link Captain's Papers before battle end to earn eligible points. Unlinked play still works in chat — it simply does not earn site rewards. Official developer accounts remain on the board with a DEV mark and do not receive RUM or WAVES.

Ties break on wins, total effective impact, active ticks, matches, then earliest score time.

Boards list Twitch display names as the primary identity and the linked WAX account as a quieter secondary game identity. Other Captain's Papers data stays private. Official developer entries stay visible with a DEV mark and are excluded from the weekly RUM and WAVES pool. Choose any official week from the leaderboard or battle archive dropdowns. Personal standing, Training Crew counters, and your log follow the selected week. Final rewards appear after that week is settled.