Reconnecting can leave game speed stuck at 64x
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
Research direction
Start by tracing the reconnect catch-up flow and how it changes and restores the saved Game Speed setting; the issue does not name files or tests. Reproduce a reconnect and check the speed after catch-up ends and after starting a later game. Done means reconnecting restores the player's chosen speed without changing the saved setting.
Written by the indexing model from the issue text.
Description
Difficulty: Medium
What
After reconnecting to a match, the game sometimes stays stuck at a very fast game speed (64x) instead of going back to the player's own Game Speed setting.
- When a player reconnects, the game replays the match at high speed to catch them up. That part is expected.
- Sometimes, once the catch-up ends, the speed is never put back. The rest of the match plays with every animation far too fast.
- Changing the setting by hand is the only fix. Because Game Speed is a saved setting, the wrong value can carry over to later games.
Why
- Players can't follow what's happening at 64x: scoring, joker triggers and the opponent's actions fly past.
- It hits players who just had connection trouble, mid-match, which is already a bad moment.
- It's easy to miss that the setting changed, so players may think something else is broken.
Impact
- Reconnecting puts the player back exactly as they were, at their own speed.
- No hidden setting change that follows them into later games.
If we don't
Some reconnects leave players in an unplayable, sped-up match. They have to work out the fix themselves, or the match is effectively lost.
- Dominant language
- Lua
- Stars
- 10
- Forks
- 8
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Balatro-Multiplayer/BalatroMultiplayerAPI#55 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Balatro-Multiplayer/BalatroMultiplayerAPI#61 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Balatro-Multiplayer/BalatroMultiplayerAPI#59 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Balatro-Multiplayer/BalatroMultiplayerAPI#57 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Balatro-Multiplayer/BalatroMultiplayerAPI#56 ·
Maintainers usually reply within 2 days
All issues in Balatro-Multiplayer/BalatroMultiplayerAPI
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nvim-tree/nvim-tree.lua#3383 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Balatro-Multiplayer/BalatroMultiplayerPvP#620 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
silverbulletmd/silverbullet#2231 ·
Maintainers usually reply within 2 days