Editor Integration

Editor Integration

Each PGX editor module owns the authoring and inspection tools for its system.

Layers

• Feature editor modules provide domain-specific panels and asset support.
• PGXEditorTools aggregates inspectors for Core, Registry, VersionControl and the six runtime systems.
• PGXDocs provides documentation browsing and validation.
• PGXScaffold provides template/build-plan workflows.
• PGXTutorials provides guided overlays and actions.
• PGXVersionControl builds on Unreal Source Control rather than replacing its provider model.

Editor tools may read runtime/configuration state and help authors diagnose it. They are not runtime authority and are excluded from packaged execution according to their module types.

Extension rules

• register tabs, categories or templates through the owning public registry;
• keep runtime types in runtime modules and Slate/tooling in editor modules;
• avoid adding a feature-to-feature runtime dependency for an editor convenience;
• report validation failures with enough context to fix the underlying asset.