Come new feature - captain math inside the contest card

Feature · 03 Aug 2026

The contest card now shows captain pick and vice-captain multipliers before entry. Contest math is shown next to the prize pool so the settlement rule is not a guess.

What changed

Verification

Why the captain math moved onto the contest card

The captain pick and vice-captain multipliers used to live on a separate help screen that the user opened only after picking a captain. Verified: that flow hid the settlement rule behind a tap, and the user discovered the multiplier only at the end of the contest. Unverified: third-party contest cards that show the captain math differently from the settlement rule are not part of the verified surface; the contest math on the Come app is the same as the settlement rule on the verified surface.

Three reasons the captain math moved onto the contest card:

1. Settlement rule visible. The captain × 2 and vice-captain × 1.5 multipliers are visible before the user locks the contest. The settlement rule on the contest card matches the rule the settlement engine reads at the end of the match.
2. Roster context. The roster view surfaces last-five form and role fit beside the player. The captain and vice-captain picks on the contest card are the same players the roster view returns for the same match window.
3. One source of truth. The contest card, the roster view and the settlement engine read the same fields. A captain pick that disagrees between the contest card and the roster view is a backend error and the support desk can resolve it against the same snapshot.

What the captain math looks like at settlement

The captain and vice-captain multipliers apply to the player's run points, not to the player's wicket points or catch points. Verified: the multiplier is applied at the player-row level, then summed across the roster. Unverified: a multiplier applied to wicket points or catch points is a backend error and the support desk will revert it to the player-row level on the verified surface.

How the captain math settles:

• Captain × 2. The captain's run points are doubled. Wicket points and catch points are unchanged.
• Vice-captain × 1.5. The vice-captain's run points are multiplied by 1.5. Wicket points and catch points are unchanged.
• Other roster players × 1. The rest of the roster is read at face value, with no multiplier.
• Sum. The settlement engine sums the adjusted run points across the roster, then publishes the total on the settlement row.

Roster view - what "form" and "role fit" mean on the card

The roster view surfaces last-five form and role fit beside the player. Verified: the last-five form number is the average of the player's last five settled match points, and the role fit number is the share of recent innings in the player's primary role. Unverified: a number on the roster that disagrees with the settlement engine is a backend error and the support desk can resolve it against the same snapshot.

How the two numbers are read on the roster card:

• Last-five form. The average of the player's last five settled match points, read at the snapshot timestamp on the contest card. The number is rounded to one decimal place; a number with more decimal places is a backend display error and the support desk will round it to one decimal on the next refresh.
• Role fit. The share of recent innings in the player's primary role, read at the snapshot timestamp on the contest card. Role fit is shown as a percentage; a percentage outside 0-100% is a backend display error.
• Primary role. The role the player is listed in on the squad. The primary role is set by the squad and is not editable on the contest card; a role change requires a squad update on the squad page.
• Snapshot timestamp. The timestamp the roster view was generated at. Live values may differ after the snapshot, but the timestamp is the source of truth at request time.

What changes for users who already had a roster

Users who already had a roster on a contest card see the captain and vice-captain multipliers on the existing roster, not on a new contest card. Verified: the multiplier is applied to the existing roster, not to a new roster, so the captain pick and vice-captain pick remain the same. Unverified: a multiplier applied to a new roster is a backend error and the support desk will revert the captain and vice-captain picks to the values on the existing roster.

How the multiplier is applied to an existing roster:

1. Read the existing roster. The contest card reads the existing roster at the snapshot timestamp. The captain and vice-captain picks are the same picks the user made before the new feature.
2. Apply the multiplier. The captain's run points are doubled and the vice-captain's run points are multiplied by 1.5. Wicket points and catch points are unchanged.
3. Publish the settlement row. The settlement engine sums the adjusted run points across the roster and publishes the total on the settlement row. The settlement row uses the same multipliers the contest card shows.
4. Reconcile on the wallet. The wallet reconciles the settlement row against the deposit that funded the entry. The reconcile is non-destructive; no bonus balance is cleared and no withdraw route is detached.