Appearance
Scopes and lifetimes
Every scope owns an independent registry. A registration in World is not visible to a GameInstance query, even when both calls come from the same actor.
Choose the scope
| Scope | Owner | Typical use | Lifetime |
|---|---|---|---|
| World | UAuralisRegisterWorldSubsystem | Level actors, targets, interactables | One Game, PIE, or GamePreview world. |
| GameInstance | UAuralisRegisterGameInstanceSubsystem | Session data and quest structs | The current game instance, including level travel that retains it. |
| LocalPlayer | UAuralisRegisterLocalPlayerSubsystem | Per-player widgets and local UI | One local player, separate for split-screen players. |
| Engine | UAuralisRegisterEngineSubsystem | Process-wide services | The engine process; it can outlive PIE sessions. |
Use World as the starting choice for gameplay actors. An ordinary editor world does not create a World registry; start PIE to test a gameplay registration.
Objects are weak references
Registering an actor, component, or UObject does not retain it. Keep services you create with NewObject in an appropriate reflected owner property while they are needed. A wider registry scope cannot extend an actor's lifetime across level travel.
Queries skip destroyed objects but do not remove their slots. Use Unregister on a saved generation-matching handle, or Compact Invalid Objects on the registry, to remove stale entries.
Structs are owned copies
Register Struct stores a copy of an FInstancedStruct. Modifying the original variable or a result copy does not modify that stored payload. Register a replacement when the payload changes; metadata setters change key/tags/priority, not the struct value.
GameInstance struct entries can survive a level change within that game instance. They are not automatically saved to disk and disappear when the owning scope shuts down.
Handles identify registrations
A handle tracks its registry, slot, and generation. Unregistering and reusing a slot does not make an old handle point to the new entry. Is Handle Valid also becomes false when the registered object is destroyed or the registry shuts down.
Keep one handle for each registration you create manually. An object can have multiple entries; Unregister Object removes all of that object's entries in the selected scope.
LocalPlayer context
Pass the intended Local Player explicitly for split-screen integrations. Otherwise the resolver attempts to infer it from a local player, controller, widget, component owner/pawn controller, or local-player outer. An AI actor with no local player cannot resolve this scope.
Engine scope and world boundaries
By default, Engine scope rejects world-owned objects. Allow Engine Scope World Objects changes that behavior, but does not make those objects persistent. World registries also reject objects belonging to a different world; related ownership checks apply to game instances and local players.
PROCESS-LOCAL STATE
The plugin does not replicate entries between server and clients. Register the appropriate objects on each machine and choose the same intended scope for registration and lookup.
Continue to Queries and duplicates or Project settings.