Skip to content

Blueprint API Design

PlatanoGames edited this page Aug 8, 2026 · 3 revisions

Blueprint API Design

PGX exposes Blueprint operations through domain libraries, async action objects, Blueprintable bases and selected graph nodes while keeping system state in subsystems and authored policy in Data Assets.

Current API rules

  • A Blueprint node delegates to the same domain operation used by native code.
  • Long-running operations use async actions or delegates rather than blocking.
  • Gameplay Tags represent states, channels and domains where a closed enum would make extension difficult.
  • Configuration is referenced through Unreal assets/settings, not hidden global files.
  • Error and status outputs are explicit enough to diagnose a failed operation.
  • Graph-only helpers live in UncookedOnly modules.

Core includes message graph support; Save includes a save-domain node in PGXSaveNodes. These nodes are preview APIs and may change between 0.x releases.

Clone this wiki locally