Appearance
Troubleshooting
Start with the smallest reproducible case: one actor, World scope, one named key, and a query triggered after registration.
Plugin or nodes are missing
Confirm the package matches your engine minor version, enable AuralisRegisterSystem, and restart the editor if required. Search for Auralis Register Participant or Find Object by Key. For source-only installation, check the C++ build output and the runtime-module dependency described in Installation and C++ integration.
A lookup returns null or an empty array
- Start PIE; an ordinary editor world has no World registry.
- Confirm registration succeeded with Is Handle Valid or Is Object Registered.
- Use the same scope and, for LocalPlayer, the same player for registration and lookup.
- Check that the consumer runs after registration. Avoid assuming unrelated BeginPlay order.
- Compare the exact key and class/interface filter. Check required/excluded tags and exact-match options.
- Confirm the object is still alive. Registration does not retain it.
An empty by-Key input or invalid by-Tag input deliberately returns no result. For a broad query, use the full query node instead.
Only one actor remains under a shared key
The participant defaults to Replace. Use Allow Many for a group of actors under the same key, then use a plural lookup helper. See duplicate identity.
The same object appears more than once
The result-based Find All and typed C++ FindAll return registration-derived matches. Use Find Objects or the actor helpers for unique objects. Count Matches and Count Objects intentionally answer different questions.
Metadata changed, but an old result still has old tags
Results are snapshots. After a setter or Update Registration, call Try Get Result with the handle to read current metadata. Metadata updates do not replace a struct payload.
A LocalPlayer or Engine registration fails
Pass an explicit local player when the context cannot resolve one; NPCs usually belong in World. Engine scope rejects world-owned objects by default. Template objects are also rejected by default. Read relevant warnings on LogAuralisRegisterSystem.
An object disappears after garbage collection
The registry stores weak object references. Keep a manually created service in a reflected owner property while it is needed. Queries skip stale objects; remove their slots with a saved generation-matching handle or explicit compaction.
A radius query works, but an overlap does not
Origin searches and collision searches answer different questions. Check query collision, the chosen channel response, the shape, ignored actors, and simple/complex collision support. Line traces stop at the first blocker even when that blocker is not registered.
Events do not arrive, or callbacks repeat
Enable Broadcast Blueprint Events and bind to the correct scope registry. Handle Updated separately from Removed. Callbacks run synchronously; avoid registering and unregistering in an uncontrolled feedback loop.
A game-thread warning appears
Move the registry operation to the game thread. The API refuses off-thread operations; it is not a concurrent background-data store.
Still blocked? Use Support and include the exact reproduction and relevant log lines.