[Beta v3 PvP] "Enemy hands left" HUD shows stale/default value at PvP blind start
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start with action_start_blind in networking/action_handlers.lua and compare its state resets with the enemy hands fields used by objects/blinds/nemesis.lua. Read the HUD rendering in ui/game/blind_hud.lua, then verify that each PvP blind begins with a current enemy-hands value rather than the previous or default value.
Written by the indexing model from the issue text.
Description
Status: root cause confirmed
Affects: MultiplayerPvP Closed Beta v3 (mqtt branch)
Symptom
Tester report (with screenshot): "initial hand shows incorrectly." At the start of every PvP blind, the "Enemy hands left:" counter shows a wrong number — the hardcoded default (4) on the first PvP blind of a match, or the previous blind's leftover count (e.g. 0/1) on later ones — until the opponent's first play/skip syncs.
Root cause
The old framework's server pushed enemyInfo (score/hands/skips/lives) every ~3s, continuously correcting the display. The MQTT conversion removed that stream (tombstone comment at networking/action_handlers.lua:417-418); opponent display state now syncs only via the nemesis blind's on_sync (objects/blinds/nemesis.lua:35-132), which fires solely on the opponent's playHand/skip.
action_start_blind (networking/action_handlers.lua:398-415) resets enemy.score and info_received at blind start but never resets MP.GAME.enemy.hands/hands_text, so the stale value renders. The "?" mask in ui/game/blind_hud.lua:203-211 only applies when the separate hide_score_until_played option is on, so with it off the raw wrong number shows.
- Dominant language
- Lua
- Stars
- 338
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Contributor 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/BalatroMultiplayer
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Balatro-Multiplayer/BalatroMultiplayer#534 · 4 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in Balatro-Multiplayer/BalatroMultiplayer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
api7/lua-resty-saml#62 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nvim-tree/nvim-tree.lua#3357 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
codymikol/multiverse.nvim#320 ·
-
Data Correction tbc
Difficulty 2/5 1-3 hours Newbie friendliness 68/100