Game systems recipes

Every recipe follows the same contract:

State lives on the server in a service module; persistent parts go through the data layer (roblox-data-stores).
Clients send intents through validated, rate-limited remotes (roblox-security, roblox-networking) and render state they receive (attributes, snapshots/deltas).
Config is data: tunables in a shared/server config module (or live ConfigService configs).
Lifecycle-safe: handles late joiners, respawns, leaving mid-action, and server shutdown.

System	Reference
Leaderstats, currency service, XP/levels, daily rewards, obby checkpoints	references/progression.md
Round loop (intermission → match → results), teams, spawning	references/round-system.md
Melee and ranged combat with server validation, cooldowns, damage attribution	references/combat.md
Inventory, equipping tools, shop purchases (soft currency), pets that follow	references/inventory-shop.md

roblox-game-systems