Whitepaper
Fleet Skirmish
Join Blue or Red
When a lobby opens, captains join a fleet in chat with !join blue or !join red (team preference optional when auto-balance applies). Combat starts after the lobby window closes.
- Combat envelope
- 4 ticks/round · 3 rounds max · 22s ticks · fleet budget 120
- Week reset
- Thursday 16:00 UTC
- Week 1 launch
- 10 Sep 2026 16:00 UTC
Battle commands
During an open orders tick, submit one action. Same-tick replacements are limited; the last accepted action wins.
| Command | Aliases | Role |
|---|---|---|
| !fire | !shoot, !cannon | Deal damage to the opposing fleet |
| !brace | !block, !defend | Reduce incoming damage |
| !patch | !repair, !mend | Restore hull |
Fleet tick budget
Every fleet receives the same base 120-power budget each tick under standalone-1.6, regardless of crew size. Roster size itself does not multiply a fleet's base power. The budget belongs to the fleet, not to each player or each command.
More players provide additional tactical coordination and action coverage, not automatically more total damage, blocking, or repair. Their orders determine how the shared budget is distributed.
The fleet budget is allocated across Fire, Brace, and Patch according to the accepted actions submitted that tick. Players choosing the same action share that action's resolved contribution; adding another Fire command does not create another full 120-power volley.
Example: if a solo fleet only uses Fire, its full base tick budget goes toward Fire. If two players on the opposing fleet both use Fire, they share their fleet's Fire result rather than dealing two independent full-power attacks.
Randomness, critical hits, and possible action failures can still change the resolved damage, blocking, and repair. Listed power is the budget before those rolls, not a guaranteed result.
Individual website points use each captain's effective contribution and active ticks; they are not simply duplicated because more players joined. Impact on the site board is derived from effective contribution vs action power, not from wasted rolls or critical luck.
!parley
When anti-cheat is enabled for Skirmish, captains must complete the !parley challenge shown at the bottom-center of the stream before protected actions such as !join, !fire, !brace, and !patch are accepted. Parley is a participation / human-check gate — not a combat action.
What the website owns
- Ingest of completed match envelopes from the live bot
- Captain's Papers Twitch-link eligibility for website points
- Weekly scoring, standings, and match history on the site
- Config-versioned weekly reward pools and projected / final proportional shares
Play surfaces live under /play/skirmish. RUM settlement is manual after finalization; WAVES delivery runs through Twitch via ParrBot / ScurvyBot. Skirmish weekly rewards are RUM + WAVES only — not pack or other prize inventory from this chapter.
Papers eligibility
A Captain's Papers Twitch link must exist before battle end for website points to attach. Link Twitch through Captain's Papers before the fight resolves if you want standings credit on the site.
Timing
Linking after battle end does not retroactively score that match for website points.
Weekly scoring
Site scoring (v2) awards points only for eligible, active captains. Categories:
| Category | How it scores |
|---|---|
| Active | +5 when active ticks > 0 |
| Engagement | +2 per active tick |
| Impact | Capped by active ticks and effective contribution vs action power |
| Versatility | +4 / +2 / +0 for three / two / one action types |
| Victory | +5 if your fleet wins |
| Fleet Sunk | +3 when your fleet sinks the opposing fleet and survives, in addition to Victory |
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.
Bot-assisted battles
When no human joins the opposing fleet, Training Crew may fill in. Eligible captains earn 25% of normal site score for their first 50 Training Crew matches each week. Competitive human PvP remains full score. Training Crew is not a ranked captain and has no wallet or Papers.
Tie-break
Ties break on wins, total effective impact, active ticks, matches, then earliest score time.
Weeks run Thursday 16:00 UTC → next Thursday 16:00 UTC (Thursday 16:00 UTC). Week 1 starts 10 Sep 2026 16:00 UTC.
Weekly rewards
Each week allocates a config-versioned pool of 10,000 RUM and 100,000 WAVES proportionally to eligible points. There is no guaranteed minimum share. Total points include bot-assisted awards (25% · first 50 Training Crew matches/week) — same pools as competitive PvP.
- RUM
- Manual payout after the week finalizes
- WAVES
- Twitch delivery via ParrBot !tip / ScurvyBot after finalization
- Projection
- Live boards show Projected shares; Final locks after settlement
- Bot-assisted
- 25% of normal score · first 50 Training Crew matches/week
Scope
Weekly Skirmish pools are RUM and WAVES only. This chapter does not award pack inventory or other non-RUM/WAVES prizes from the Skirmish settlement path.
Public standings privacy
Public leaderboards show Twitch display names first (falling back to normalized Twitch login) as the primary identity, and the linked WAX account name as a secondary game identity. Score fields and projected or final reward shares remain public. Other Captain's Papers data — Twitch provider IDs, Discord identity, OAuth tokens, and internal IDs — stays private. Pagination cursors remain opaque.
Developer entries
Official developer accounts remain visible with a DEV mark and ordinary combat statistics. They are excluded from weekly RUM and WAVES denominators, allocations, and settlements so they do not take a prize share or shift eligible ranks.