-
Notifications
You must be signed in to change notification settings - Fork 0
GameplayTag Architecture
PlatanoGames edited this page Aug 8, 2026
·
3 revisions
Gameplay Tags are used as hierarchical identifiers across PGX.
- message channels;
- GameFlow states and channels;
- save domains;
- registry keys;
- event-handler selection;
- PSO contexts;
- loading and observability categories.
Each domain owns its branch and payload semantics. A shared prefix does not mean that arbitrary payloads are interchangeable. Tags should be declared in the owning module and documented with the contract that consumes them.
Tag counts vary by release. Consult the source for the selected tag.
- 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