game-server-security
Review multiplayer authority, RPCs, sessions, authorization, replication, inventory, economy, purchases, retries, and replay. Use when server or backend state is the security boundary.
Game server and backend security
Trace one consequential operation across client, transport, server, backend, provider, and durable state. Authentication is an input to authorization, not a substitute for it.
Topic routing
- Review guide for authority maps, attack objectives, authorization, economy state, network failure, and verification.
- Time, ordering, and replay for clocks, retries, idempotency, prediction, and reconciliation.
- Repository resources for framework and transport selection.
Use anti-cheat-systems for detector enforcement, game-engine-resources for engine replication models, and game-supply-chain-security for released server or plugin artifacts.
- Repository
gmh5225/awesome-game-security
- Revision
b439093
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.