Rework zone profiler to include event processing

Open
#723 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start by tracing the zone profiler calls from input handling, especially the puzzle editor path that documents the match start before the frame is initialized. Check how profiling handles writes and quitting when input changes state. Done means input events are included in profiling and the puzzle editor no longer crashes on match start.

Written by the indexing model from the issue text.

Description

bug Cleanup Client-side

The zone profiler currently excludes input events from profiling.
Input events can unpredictably change state (like exiting the game) which can require some extra handling on write or on quit, as otherwise the data may end up corrupt.
Until recently there was no code that called the profiler as a direct result of input handling so there was no issue.

The newly added puzzle editor very much does that though which causes a crash because the frame is not initialized yet when the profiler is called to document the match start.

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.