Guide
Game surrender and forfeit vote systems explained
Harbor Arena shipped ranked 5v5 with a surrender button available from the first round. A simple majority (3 of 5) ended the match immediately. Within two weeks, analytics tagged 52% of ranked sessions as “trapped” — players who wanted to leave but were held hostage by one holdout teammate, or who spammed surrender after a lost pistol round and tanked queue experience for everyone. Surrender-initiation rate hit 2.8 votes per match on losing streaks. Competitive integrity reviews flagged the system as worse than no surrender at all: it encouraged tilt without offering a fair escape when a teammate left mid-match.
Surrender and forfeit vote systems give teams a structured, server-authoritative path to end a match early — with timing gates, vote thresholds, cooldowns, and ranked economy rules that separate legitimate exits from grief. This guide covers the vote FSM, remake vs surrender vs disconnect forfeit, integration with match format and overtime rules, the Harbor Arena refactor, a technique decision table, pitfalls, and a production checklist.
Why surrender exists (and why it is dangerous)
Without a surrender path, players trapped in unwinnable 4v5s after a disconnect either alt+F4 (triggering leaver penalties) or idle-grief until the timer expires. A well-designed vote system:
- Converts rage-quits into a team decision with recorded consent.
- Ends matches that cannot be competitively salvaged within a bounded time.
- Reduces report volume for “griefing / not trying.”
- Preserves match integrity by requiring supermajority, not one angry click.
Poor surrender design does the opposite: early exits destroy comeback arcs, inflate match length when votes fail repeatedly, and let duos bully solo players into forfeiting wins. Treat surrender as a relief valve, not a default loss button.
Vote FSM: initiation, threshold, and resolution
Run surrender as a server-side finite-state machine tied to match phase:
- IDLE — no active vote; cooldown satisfied.
- OPEN — one player initiates; 15–30s window; teammates cast yes/no; initiator vote counts as yes.
- PASSED — threshold met; match transitions to
FORFEITend state. - FAILED — window expired without threshold; apply cooldown before next initiation.
Typical thresholds for 5v5 ranked:
| Vote type | Threshold | When available |
|---|---|---|
| Remake (ally never joined / early DC) | 4/5 unanimous minus absent | Minutes 0–5 |
| Early surrender | 4/5 supermajority | After round 4, before half |
| Standard surrender | 3/5 majority | After half / round 12+ |
| Overtime surrender | 4/5 supermajority | During OT |
Store each vote with initiator_id, yes_count,
no_count, match_minute, and
score_delta for anti-abuse tuning. Never resolve votes on
the client; UI is display-only.
can_initiate_surrender(player, match) =
match.phase >= SURRENDER_UNLOCK
AND match.minute >= MIN_MINUTES
AND player.team.surrender_cooldown_expired
AND NOT match.in_overtime OR match.ot_round >= 2
Timing gates and comeback protection
The Harbor Arena postmortem found most bad votes happened in the first three rounds — before economy and ultimates stabilized. Timing gates prevent surrender from replacing actual play:
- Hard lockout — no surrender votes before round N (often 4–6 in round-based shooters).
- Score-aware delay — if deficit < 3 rounds, require +1 vote (supermajority) until minute 15.
- Round-boundary resolution — passed votes take effect at round end, not mid-engagement, so a clutch cannot be cut off during a plant.
- Cooldown after failed vote — 90–180s before the same team can reopen; stops spam.
Pair gates with match format rules: Bo3 sets may allow surrender only within a single map, never between maps in a series.
Remake vs surrender vs disconnect forfeit
Three exit paths look similar to players but must stay separate in backend enums:
- Remake — match never reached competitive integrity (ally AFK at spawn, load failure). No LP/MMR change; optional small queue penalty for the absent player only.
- Surrender — team consented to loss. Full loss recorded; MMR/LP rules apply normally unless loss-shield from leaver applies.
- Disconnect forfeit — team drops below minimum players after grace expires; server auto-ends. Winning team gets reduced reward; losers flagged for leaver penalties.
Never share vote cooldowns between remake and surrender. Players in a 3v5 after minute 10 need surrender, not a remake that only works in minute 3.
Ranked economy: LP, MMR, and initiator friction
Ranked surrender should cost something — lightly — so it is not the fastest way to dodge a bad agent comp:
- Initiator flag — first surrender vote per match tagged; repeat initiators in 24h get longer cooldowns (not LP loss on first offense).
- No win credit inflation — winning team gets standard LP; optional 10–15% reduction if match ended before minute 12 to discourage bait-surrender agreements.
- Loss shield exception — if leaver flagged on your team before vote opens, surrendering team takes neutral LP (already covered in AFK guide).
- Party restrictions — premade stacks of 3+ require unanimous yes from party members before their votes count toward threshold (prevents duo bullying).
Casual modes can skip LP friction entirely but should still enforce supermajority after round 6 to protect solo players.
UX: clarity, audio, and anti-tilt
Vote UX drives perceived fairness as much as thresholds:
- Show who initiated and remaining seconds on a non-blocking banner — not a full-screen modal during combat.
- Play distinct audio for open / passed / failed; mute repeat prompts during the same cooldown window.
- Display why surrender is locked (“Available after round 5”) instead of a greyed-out button with no tooltip.
- After a failed vote, show cooldown timer to the team — reduces chat arguments.
- In lobby, never expose surrender; keep exit paths to dodge only.
Harbor Arena refactor walkthrough
Harbor Arena’s competitive patch shipped four changes:
- Split enums for remake, surrender, and DC forfeit with separate cooldown tables.
- Round-5 unlock for standard surrender; 4/5 threshold until half, then 3/5.
- 90s failed-vote cooldown per team; initiator-specific 3-minute cooldown on third failed vote in a match.
- Round-boundary resolution plus OT supermajority (4/5) from the first overtime round.
After three weeks: trapped-match survey tags fell from 52% → 14%, surrender spam dropped from 2.8 to 0.4 votes per match, and average match length on losing teams decreased by 3.2 minutes without changing round-win comeback rates. Remake usage rose 18% in minutes 0–5 — the intended path for early exits.
Technique decision table
| Scenario | Prefer | Avoid |
|---|---|---|
| Ally never loaded minute 2 | Remake vote (4/5) | Surrender with LP loss |
| 4v5 after leaver minute 8 | Surrender + loss shield | Force play to 40 min |
| Lost pistol round | No vote until round 5 | Majority surrender round 1 |
| OT first round | Supermajority surrender | Simple majority OT exit |
| Failed vote tilt | 90s team cooldown | Instant re-vote spam |
| Premade duo bullying solo | Party unanimity rule | 2/5 forced forfeit |
| Bo3 series map 1 | Surrender ends map only | Series forfeit on one vote |
Common pitfalls
- Surrender from round one — kills comeback design and ranked integrity.
- Same threshold for remake and surrender — players use wrong tool or get trapped.
- Mid-round instant end — feels arbitrary during clutches.
- No failed-vote cooldown — chat and UI spam every 30s.
- Client-authoritative votes — trivial to spoof; server must own state.
- Full LP punish for surrendered team with leaver — double penalty with leaver systems.
- Hidden lockout rules — players think the button is broken.
- Surrender in tournament rulesets — needs admin override or disabled entirely.
Production checklist
- Define remake, surrender, and DC-forfeit enums with separate cooldowns.
- Server-authoritative vote FSM with logged initiator and timestamps.
- Hard lockout before round N; score-aware supermajority early.
- Resolve passed votes at round boundary, not mid-engagement.
- 90–180s cooldown after failed team vote.
- Ranked LP rules for initiator friction and leaver loss-shield exceptions.
- Party unanimity rule for stacks of 3+.
- OT uses higher threshold than regulation second half.
- UI shows lockout reason, countdown, and cooldown clearly.
- Telemetry: votes per match, pass rate by minute, trapped-match surveys.
Key takeaways
- Surrender is a team consent mechanism — thresholds must reflect that.
- Timing gates protect comeback arcs more than any UI copy.
- Remake and surrender solve different problems — never merge their flows.
- Failed-vote cooldowns reduce tilt as much as passing votes reduces traps.
- Harbor Arena cut trapped-match churn from 52% to 14% with round-5 unlock and supermajority early surrender.
Related reading
- Game AFK and leaver penalty systems explained — disconnect grace, loss shields, and leaver classification
- Game match format and round systems explained — when rounds end and how Bo3 sets interact with forfeit
- Game overtime and sudden death systems explained — OT surrender thresholds and extension ladders
- Game match lobby and pregame systems explained — dodge vs in-match exit boundaries