Gameplay in C++, tuning in Blueprints, assets named by convention, a budget per system.
Constitution — Unreal Engine 5 game
Version 1.0.0 · Ratified 2026-11-10
These principles hold for every spec, plan and task of the game. A spec may add rules; it never weakens these.
-
Gameplay in C++. Core systems, replication and anything that runs every tick are written in C++. Blueprints call into that code; they do not reimplement it, and a Blueprint graph with loops over actors every tick fails the review.
-
Tuning in Blueprints. Designers tune through
UPROPERTY(EditDefaultsOnly, BlueprintReadOnly)values, Data Assets and Data Tables exposed from C++. A value a designer needs to change is never hard-coded in a.cppfile. -
Assets named by convention. Every asset uses the agreed prefix (
BP_,SM_,SK_,M_,MI_,T_,ABP_,WBP_) and lives in its feature folder. A validator in the editor rejects misnamed or misplaced assets on save and in CI. -
A budget per system. Each system (AI, animation, physics, UI, rendering) has a millisecond budget on the minimum spec target. Unreal Insights traces of the reference levels run in CI, and a system over budget blocks the merge.
-
Ticking is opt-in. Actors and components start with
bCanEverTick = false; ticking is turned on only with a reason and at the lowest rate that works. Timers and events replace polling. -
Replication is designed, not added. Each replicated property and RPC is listed in the plan with its owner, its relevance and its frequency. The server validates every RPC from a client; an unvalidated
ServerRPC fails the review. -
Hard references are kept small. Blueprints and Data Assets use soft object references for content that is not always needed, and the Size Map of every gameplay Blueprint stays under the agreed memory limit.
-
Automated tests run headless. Gameplay rules have Automation Spec tests and key maps have functional tests, run headless with
-nullrhiin CI. A red test blocks the merge. -
Builds come from BuildGraph. Packaged builds for every platform are made by BuildGraph or UAT scripts on the build machine with a pinned engine version. No shipped build is cooked by hand from an editor.