-
Notifications
You must be signed in to change notification settings - Fork 0
Data Driven Design
PlatanoGames edited this page Aug 8, 2026
·
4 revisions
PGX uses Unreal Data Assets and project settings for policy that designers and programmers need to review together.
- define domain data in a typed asset;
- reference the asset through settings, a profile or another asset;
- validate required fields and dependencies;
- let the owning subsystem resolve the active policy;
- expose the resolved state through logs, observables and editor inspection.
This pattern is used by Core profiles/registry and by Audio, GameFlow, Loading, PSO and Save domain configuration. Assets remain ordinary Unreal assets under source control; PGX does not introduce a separate opaque configuration store.
- Development Preview
- Getting Started
- Release branch catalog
- Public Plugin Matrix
- Early Preview Plugins
- Known Issues
- Architecture Overview
- Plugin Topology
- Module Reference
- Configuration and Registry
- Data-Driven Design
- Profiles and Budgets
- Gameplay Tag Architecture
- Initialization Pipeline
- Cross-Plugin Communication
- Message System
- Event Handlers
- Logging and Trace
- Runtime Flows
- Blueprint API Design
- Editor Integration
- Editor Visual System