Making a designer hook
Expose a BlueprintImplementableEvent so the C++ triggers something and designers decide what happens in Blueprint. The cleanest "system vs. design" hand-off.
Trigger side (C++/TPScript)
uclass ASpawner : AActor meta: api=MYGAME_API
{
func public void OnWaveComplete() BlueprintImplementableEvent category="Spawner"
func public void CompleteWave() BlueprintCallable
{
// C++ logic happens here...
OnWaveComplete(); // ...then designers react.
}
}
Designer side (Blueprint)
- Select the actor.
- Add Event → OnWaveComplete.
- Spawn rewards, play audio, advance a quest flag.
Why it's powerful
- C++ owns timing/state; Blueprint owns design decisions (spawn what/where, show UI).
- No coupling - the hook has no knowledge of what designers attach.
- Frame-rate safe - the C++ does heavy lifting; Blueprint just reacts.
Two related hooks
| Keyword | Where a body lives | Blueprint sees |
|---|---|---|
BlueprintImplementableEvent | Blueprint only (empty C++) | implementable graph node |
BlueprintCallable | C++ only | callable node |
Use BlueprintCallable when C++ provides the behavior and you want Blueprint to invoke it; use BlueprintImplementableEvent when Blueprint must define the behavior.
Next step: Language reference.