Balatro-Multiplayer / Balatro-Multiplayer/BalatroMultiplayerAPI-Server

Policy: leaving a match after accepting (two-tier consequences)

Open
#38 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
13
Forks
20
Avg merge
3d 7h
Merged PRs (30d)
7

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?).

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.