Reading map / original course

Read the source.
Keep its limits.

The exercises and toy rules are original. These readings supply context; they do not certify the model or require a purchase.

Primary technical accounts

Glenn Fiedler: What Every Programmer Needs To Know About Game Networking explains client/server state, prediction and correction. Use it to compare a client claim with server authority; its examples do not specify this course's tick or sequence contract.

Riot Games: Demolishing Wallhacks with VALORANT's Fog of War is a historical first-party account of reducing unnecessary state and handling visibility, performance and repair. Study architecture and evidence limits, without reproducing third-party attack tools or assuming its measurements apply here.

Node's performance API describes the clock used for the timing investigation and retention measurements. Its zero belongs to the current process; raw readings from different process lifetimes cannot establish elapsed time across a restart. Node's memory reporting distinguishes memory categories; serialized JSON bytes are a different measure.

Microsoft's debugging overview introduces user/kernel mode, symbols and host/target terminology for optional later native study. No driver installation or OS change belongs to this software core.

Optional book context

The local library registry verified these book identities from title/copyright metadata. Most remain bibliographic pointers. Two short sections of System Programming in Linux were additionally read: chapter 1 “Processes” and chapter 2 “System Calls.” They ground the distinction between stored program bytes, a running instance, and an OS interface; they do not validate this course’s Node runtime or provide its game rules. Full chapters were not reviewed.

Use existing lawful access if helpful. No book purchase, chapter redistribution or employer material is needed. Exact passage-level assignments require an additional source check.

Original model assumptions

The 50 ms tick, 250 mm pickup, 400 mm repair radius, expiry, receipt capacity, scripted labels, hashes and local rollback scenarios are explicit teaching choices. They are tested as contracts; they are not attributed to the readings. The earlier browser-only movement model is a separate teaching aid. The full source register and original review evidence remain in the repository under docs/features/anti-cheat-engineering.