Lobby screen stays drawn behind the run after the game starts
維護者通常 1 天內回覆
評估
研究方向
Start at G.FUNCS.start_run and Game:delete_run, then at MPAPI.refresh_current_view() and its G.STAGE check, to see how a lobby update can rebuild G.MAIN_MENU_UI during the gap before the run starts. The work is already under way: open PR #45 is linked. Check that PR's approach first, and a fix is done when the lobby UI is gone after a delayed delete_run in a three-client Royale lobby.
由索引模型根據 Issue 內容生成。
描述
Reported in #bugs-and-issues with a screenshot: in a Battle Royale, one player had the pre-match lobby screen (Ready, the deck/stake chip, View Code, Leave Lobby) drawn behind the game for the whole run.
Why: G.FUNCS.start_run runs delete_run (which removes the menu) and then, a tick later, start_run. In that gap G.STAGE is still MAIN_MENU, so a lobby update arriving then (e.g. the host writing lobby metadata at the start) calls MPAPI.refresh_current_view(), which passes its G.STAGE check and rebuilds the lobby page as a new G.MAIN_MENU_UI. Nothing removes it when the run starts. It's more likely on a slower PC (a longer gap) and in Royale (more lobby updates around the start).
To reproduce: 3 players in a private Royale lobby, opened from the PvP menu. Make one guest slow to start (e.g. delay its Game:delete_run by 0.5s) and have the host change lobby metadata repeatedly while starting. That guest has G.MAIN_MENU_UI ~= nil during the run, and the lobby cards and buttons show behind the blind select.
Reproduced with three clients on a local server.
- 主要語言
- Lua
- 星號
- 9
- 分支
- 4
- 平均合併
- 14 小時 46 分鐘
- 30 天內合併 PR
- 10
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
Balatro-Multiplayer/BalatroMultiplayerAPI 的其他 Issue
-
Hovering a deck in a speedrun draft crashes (1.0.4)可能已有人在做 @Jr-JoshS 於 2 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 76/100
Balatro-Multiplayer/BalatroMultiplayerAPI#40 ·
維護者通常 1 天內回覆
-
Replay skips booster packs opened with the shop OPEN button可能已有人在做 @Jr-JoshS 於 1 天前認領。 未關閉
難度 3/5 1-2 天 新手友好度 35/100
Balatro-Multiplayer/BalatroMultiplayerAPI#49 ·
維護者通常 1 天內回覆
-
Chat says it's only available in a lobby while you're in one (late leave answer tears down the new lobby)可能已有人在做 @Jr-JoshS 於 1 天前認領。 未關閉
難度 3/5 1-2 天 新手友好度 25/100
Balatro-Multiplayer/BalatroMultiplayerAPI#47 ·
維護者通常 1 天內回覆
-
Match History doesn't show the rating change per match可能已有人在做 @Jr-JoshS 於 2 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 30/100
Balatro-Multiplayer/BalatroMultiplayerAPI#42 ·
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 35/100
Balatro-Multiplayer/BalatroMultiplayerAPI#14 ·
維護者通常 1 天內回覆
查看 Balatro-Multiplayer/BalatroMultiplayerAPI 的全部 Issue
相似的 Issue
-
luaebpf: the by-example page's intro names two outcomes of a lowering and omits the stop with the default verdict可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉documentation severity: low
難度 1/5 1 小時以內 新手友好度 88/100
luainkernel/lunatik#2231 ·
維護者通常 1 天內回覆
-
v3: Lua m.setvar() returns -1 on errors, so the script gets stack garbage可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉3.x bug
難度 2/5 1-3 小時 新手友好度 72/100
owasp-modsecurity/ModSecurity#3731 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
good first issue redis-compat
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
LSP: Invalid buffer id in previous_result_ids during workspace/diagnostic/refresh可能已有人在做 @sharky720 於 1 天前認領。 未關閉diagnostic lsp
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆