Appearance
Your first registered checkpoint
Goal: place a checkpoint Actor in a level, register it automatically, and find that same Actor from another Blueprint. This exercise uses World scope and a named key, so it needs no Gameplay Tags or C++.
1. Prepare the checkpoint
- Create an Actor Blueprint named
BP_Checkpoint. Add a visible mesh if you want a marker in the level. - Add Auralis Register Participant.
- Select the component and configure:
| Property | Value |
|---|---|
| Scope | World |
| Register Owner | Enabled |
| Register This Component | Disabled |
| Owner Descriptor > Key | Checkpoint.Active |
| Owner Descriptor > Priority | 0 |
| Owner Descriptor > Duplicate Policy | Replace |
Place one instance in the level. The participant registers its owner on BeginPlay and unregisters its own handles on EndPlay.
KEY, NOT GAMEPLAY TAG
Checkpoint.Active is an FName key in this exercise. Type it into Key; do not add it to Tags. Keys do not require a Gameplay Tags definition.
2. Query it from another Blueprint
Use a Player Controller Blueprint, another placed Actor, or the Level Blueprint. For the first test, run the query from a key press after Play has started, so the checkpoint's BeginPlay has already run.
Create this execution path:
text
Your test input event
→ Find Object by Key
Key: Checkpoint.Active
Object Class: BP_Checkpoint
Scope: World (default; expand advanced pins if needed)
→ Is Valid
Valid: Get Display Name → Print String
Invalid: Print String "Checkpoint not registered"The World Context is supplied by a normal Actor/Controller/Level Blueprint. The class pin gives the output its checkpoint type. No result-struct break is needed for this helper.
3. Check the result
Start PIE, trigger your test input, and confirm the printed name belongs to the placed checkpoint. A null output means no live object matched that key and class in the resolved World registry.
Do not rely on the order of BeginPlay across unrelated actors. For production initialization, register before the consumer queries, query when needed, or subscribe to registry change events.
4. Try duplicate behavior
Place a second checkpoint with the same key and Replace. The later registration replaces the earlier entry. Which actor registers last is not a stable gameplay selection rule; explicitly register the checkpoint when it becomes active.
If many actors should share a key, choose Allow Many and use Find Objects by Key instead. See Queries and duplicates.
5. Check cleanup
Destroy the registered checkpoint, then query again. The participant's EndPlay removes the entry. If an object was registered manually, save its returned handle and call Unregister when finished.
For the same workflow in native code, see C++ integration. For nearby actors, continue to Actor queries.