Usage
Blueprint Workflow Examples
Pseudocode showing typical Blueprint node flows. Every node is a static function — no subsystem reference needed.
// Blueprint: Save a player's inventory to a domain PGX Save | Data | Write SetDomainValue( DomainTag: "PGX.Save.Domain.Player", Key: "Health", Value: 100 ) SetDomainValue( DomainTag: "PGX.Save.Domain.Player", Key: "Gold", Value: 5400 ) PGX Save | Core QuickSaveAsync( SlotTag: "PGX.Save.Slot.Auto" ) → OnComplete(bSuccess) // OnComplete fires when disk write finishes // Checksum sidecar written automatically
// Blueprint: Play background music + sound effect PGX Audio | Core PlayMusic( MusicTag: "PGX.Audio.Music.MainTheme", FadeIn: 2.0 ) PlaySound( SoundTag: "PGX.Audio.SFX.UIConfirm" ) PGX Audio | Query SetChannelVolume( ChannelTag: "PGX.Audio.Channel.Music", Volume: 0.7 ) GetChannelVolume( ChannelTag: "PGX.Audio.Channel.SFX" ) → float CurrentVolume
// Blueprint: Register a handler, then fire an event PGX EventHandler | Core RegisterHandler( EventTag: "PGX.Event.Ability.Cast", Priority: 100, Callback: OnAbilityCast ) FirePGXEvent( EventTag: "PGX.Event.Ability.Cast", Context: AbilityContext ← morphing pin, any struct ) // Resolution: handlers sorted by priority // Handler at P:100 runs first // If it returns Handled, lower-priority handlers are skipped // ConflictPolicy controls this behavior per event tag
Save System
PGX|Save — The Convention in Practice
The 4-level pattern above isn’t theory. Here it is in the actual editor: Data, Data|Read, Data|Write, Query, Advanced, Debug. 27 nodes organized so you find the right one without scrolling a flat list.
27 nodes · 6 sub-categories · Zero ambiguity
EventHandler
PGX|EventHandler — Same Pattern, Every System
Fire events, register handlers, query execution history. The same Core/Query/Advanced/Debug pattern you already know from Save. Learn one, know them all.
Consistent convention · 11 systems · Predictable discovery
