Clean up obsolete messages better

Open
#536 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua

Research direction

Start by reviewing the attached crash log and tracing how a match_start message is handled after leaving and joining rooms. Check where messages are queued or cleared during room changes; done means an obsolete message cannot be evaluated in the next room or crash a local player without input configuration.

Written by the indexing model from the issue text.

Description

bug Client-side priority: 1 - middle

If you manage to leave a room with a perfect time to still receive a match_start message afterwards, it lingers and will immediately get evaluated once you enter the next room.
If you're joining the next room as a local player that results in an instant crash because no input configuration has been set yet.
crash (Kopie 1).log

Dominant language
Lua
Stars
30
Forks
20
Avg merge
3d 15h
Merged PRs (30d)
17

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from panel-attack/panel-game

All issues in panel-attack/panel-game

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.