Reconnecting can leave game speed stuck at 64x

Aberta
  • Algo errado?
#58 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
57/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
lua
Domínio
backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Lua
Estrelas
10
Forks
8
Merge médio
1d 18h
PRs com merge (30d)
20

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Balatro-Multiplayer/BalatroMultiplayerAPI

Todas as issues de Balatro-Multiplayer/BalatroMultiplayerAPI

Issues semelhantes

Mais issues de Lua

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.