Roblox Architecture

When to Load

Load when code ownership is unclear, a feature crosses client and server, startup order matters, or a module is being split. Do not load merely to add a service/controller framework to a small feature.

Quick Reference

Start from one owner

For each behavior, name:

• authoritative state and who may mutate it;
• public operations and callers;
• Roblox instances, connections, and tasks it owns;
• persistence or network boundary;
• startup and teardown conditions.

Group by feature when that keeps one change together. Split server, client, and shared code only where the runtime boundary requires it. Shared code contains no secrets or authoritative mutable state because replicated code is readable by clients.