Policy: leaving a match after accepting (two-tier consequences)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- backend
Research direction
Start by reading the referenced match-acceptance issue, Balatro-Multiplayer/BalatroMultiplayer#493, and trace how leaving is currently handled after acceptance. No files, tests, or entry points are named here. Done requires agreement on the run-start boundary, ban-phase MMR loss, and queue-time penalty before implementation can be scoped.
Written by the indexing model from the issue text.
Description
Status: needs triage (policy / enhancement)
Summary
Once a player accepts a match (Balatro-Multiplayer/BalatroMultiplayer#493), they may still need to leave. Consequences should depend on when:
- Leaving after the run has started → treated as a normal loss (full game loss + MMR loss), same as any forfeit mid-game.
- Leaving during the ban phase (before the run starts) → some MMR loss but no game loss, plus possibly a queue-time penalty. Bailing during bans is lighter than abandoning a live game, but shouldn't be free.
Open questions
- How much MMR the ban-phase leave costs (fixed amount vs fraction of a loss).
- Size of the queue-time penalty, and whether it escalates on repeat.
- Exact boundary for "run started" (first blind? deck locked in?).
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 21
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 6
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Balatro-Multiplayer/BalatroMultiplayerAPI-Server
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Balatro-Multiplayer/BalatroMultiplayerAPI-Server#32 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
In Game Telemetry Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in Balatro-Multiplayer/BalatroMultiplayerAPI-Server
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
bcgov/bc-wallet-mobile#4761 · 1 comment ·
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100