Unreal Engine SDK
Store/thunk runtime for Unreal Engine 5.7
The current Unreal Engine plugin mirrors @forbocai/core and @forbocai/node: a shared store, slice state, selectors, and thunks. The public runtime is centered on FSDKState, createSDKStore(), SDKOps, and rtk::*Thunk APIs.
This page reflects the current sdk-ue-5.7.3 source. It does not describe the older factory-style integration examples that still exist in parts of the historical demo project.
What Ships
RuntimeStore.h:FSDKState,createSDKStore(),ConfigureSDKStore()NPC/NPCSlice.h: NPC entity state, selectors, history, block stateProtocol/ProtocolThunks.h:rtk::processNPC(...)multi-turn protocol executionMemory/MemoryThunks.h: remote memory and local node-backed memoryCortex/CortexThunks.h: local llama.cpp and remote cortex helpersBridge/BridgeThunks.h: validation, presets, and rulesetsSoul/SoulThunks.h: local export, remote export/import, list, verifyGhost/GhostThunks.h: Ghost session start/status/results/historyCLI/CliOperations.h: synchronousSDKOps::*wrappers over the same thunksRuntimeBlueprintLibrary.h: Blueprint-callable wrappers for a smaller subset
Canonical Runtime Pattern
Use createSDKStore() when you want your own store instance in C++. The synchronous SDKOps helpers are thin adapters over store dispatch and match the CLI/test workflow in the plugin.
Important Protocol Behavior
SDKOps::ProcessNpc(...)andrtk::processNPC(...)run the API-directed multi-turn protocol, not a single completion call.rtk::LocalProtocolRuntime()is the default runtime used by the synchronous helpers.- If the API asks for memory recall/store and local memory is not initialized, processing fails fast.
- If the API asks for inference and local cortex is not initialized, processing fails fast.
- A successful finalize step updates NPC state, last action, history, and any returned memory instructions.
Access Layers
Direct store/thunks
Best when you want parity with packages/core and packages/node.
SDKOps
Best for commandlets, tests, and synchronous tooling.
Blueprints
Best for simple wrapper calls such as CreateNpc, ProcessNpc, ExportSoul, and config access.
Next Pages
Install the plugin, wire module dependencies, and configure runtime settings.
See how FSDKState, slices, middleware, and thunks fit together.
Register NPCs, inspect selectors, and run the protocol loop.
Work with remote NPC memory and local node-backed recall.
Validate actions, load presets, and manage rulesets.
Export, import, list, and verify portable Souls.
