BroBlox Documentation¶
This repository will become a reusable, multi-game Roblox-TS platform optimized for:
- Building multiple games from shared packages (framework, networking, security, UI, live ops)
- Competitive-capable PvP (server-authoritative outcomes, strict remote validation, anti-abuse)
- CI-driven releases (Open Cloud publishing + environment promotion)
- A multi-game web dashboard for game management, moderation, config/feature flags, and operational control across all registered games
Non-negotiable principles¶
- Clients are untrusted. The server decides outcomes (damage, cooldowns, inventory, MMR, rewards).
- Networking is an API. Every remote is versioned, schema-validated, rate-limited, and monitored.
- Everything is reusable. Game-specific code composes shared packages; shared packages never depend on games.
- Operational excellence is built-in. Audit logs, kill-switches, staged rollouts, and runbooks exist before launch.
Where to start¶
- Getting started: Getting started → Overview
- Architecture overview: Architecture → Platform
- The security posture: Architecture → Networking and Architecture → State & data
- Milestones: Roadmap → Overview
- Decision log: Architecture → Decisions (ADRs)
Target outcomes (v1)¶
- A stable set of platform packages that any new game can adopt in <1 day
- A CI pipeline that publishes dev builds automatically and promotes to prod with approvals
- A multi-game control plane dashboard that can:
- register and manage multiple Roblox experiences (per-env universe IDs + place IDs)
- change feature flags globally or per-game, with environment scoping and approvals
- manage bans/mutes with evidence and audit logs, scoped per game
- view match history + anti-abuse signals across all games