> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.forboc.ai/ue/demo/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.forboc.ai/_mcp/server.

# Demo Project

> Current status of the UE demo project and how to use it safely

The repository includes a demo project at `Forboc.AI/demo-ue-5.7.3`. It is useful for project layout, build settings, and packaging reference, but parts of its sample gameplay code still reflect an older integration style than the current `sdk-ue-5.7.3` plugin.

> **Warning**
>
> Treat the current SDK source and these docs as the source of truth for API shape. Do not assume every sample in the demo project reflects the current store/thunk runtime.

## What The Demo Is Still Good For

* `.uproject` and target file setup
* module dependency layout
* plugin copy/layout inside a UE project
* reference actor and test harness organization
* UE 5.7 build settings

## What To Follow Instead For Runtime Integration

For the current plugin API, follow:

* [Welcome](/ue/welcome)
* [Architecture](/ue/architecture)
* [NPC](/ue/npc)
* [Blueprint](/ue/blueprint)

The current runtime model is:

1. create a store with `createSDKStore()`
2. register NPC state in `NPCSlice`
3. initialize local memory/cortex when needed
4. dispatch thunks or use `SDKOps::*`

## Recommended Demo Refresh Checklist

If you update the demo project itself, align it to the current runtime by:

* replacing older factory-style NPC creation with `NPCSlice::Actions::SetNPCInfo`
* replacing older process wrappers with `rtk::processNPC(...)` or `SDKOps::ProcessNpc(...)`
* initializing local cortex and node memory explicitly
* using `RuntimeBlueprintLibrary` only for the subset it actually exposes
* keeping commandlet examples aligned with the current whitelist in `RuntimeCommandlet.cpp`

> Current status of the UE demo project and how to use it safely