Skip to content

guide: the rejoin-dirty trap for render-on-change games #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BCook98 merged 1 commit into from
Jun 7, 2026
Merged

guide: the rejoin-dirty trap for render-on-change games #29

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -426,6 +426,11 @@ viewports:
- at typical input rates expect only ~10–30% of viewports dirty per tick —
a 3–10× cut in wake cost.

One trap: mark a player dirty on REJOIN (same account re-seating, including
after a hibernation resume) — their frame baselines were invalidated, and a
render-on-change game that skips them leaves the resumed session staring at
nothing until something happens to move.

The frame-delta layer already makes CLEAN-but-resent frames cheap on the
wire; dirty tracking makes them free in CPU too. Allocation discipline
matters as much as ever under `-gc=leaking`: compose into a reused
Expand Down
Loading