Roblox House Stack — Config and Flags

Overview

In the house stack every switch is a plain Luau constant or a YAML entry — there is no remote config, no per-player rollout, no dashboard. Configuration lives on five axes: the FeatureFlags class, file-local debug constants, Studio/dev conditionals, the rblxsync monetization manifest, and tuning data modules. This skill explains each axis, how to build and re-verify a per-project catalog of it, and the checklists for adding new entries.

When to use

• You need to know what a flag/constant does, or why a feature is on/off.
• You are adding a feature flag, a developer product, a game pass, or a badge.
• A monetization ID lookup warns and returns 0, or purchases silently no-op.
• Studio behaves differently from what you expect (seeding, saving, loading screens).
• You are building or refreshing the project's config catalog.

When NOT to use