Balatro-Multiplayer / Balatro-Multiplayer/BalatroMultiplayerAPI-Server

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

未关闭
#38 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
TypeScript
星标
13
派生
20
平均合并
3 天 7 小时
30 天内合并 PR
7

描述

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

贡献指南

这个仓库没有索引到贡献指南

调研方向

先阅读引用的对局接受 issue:Balatro-Multiplayer/BalatroMultiplayer#493,并追踪接受后当前是如何处理退出的。这里没有指定文件、测试或入口点。在确定实现范围之前,需要先就 run 开始的边界、ban 阶段的 MMR 损失以及排队时间惩罚达成一致,才算完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
typescript
领域
backend
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
冷清
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。