Recommendation
Use the Level Blueprint for one map orchestration. Use a Blueprint Class for reusable Actor behavior.
Compare the options
Level Blueprint
Choose when
- Logic coordinates specific placed Actor instances.
- The behavior controls one map sequence or streaming setup.
- The logic has no use outside the current map.
Tradeoffs
- The graph belongs to one map.
- Reusing the behavior in another level means moving or copying it.
- Blueprint
- Open the current map Level Blueprint from the Level Editor toolbar.
- C++
- There is no direct asset equivalent. World-specific orchestration commonly moves into Actors, framework classes, or Subsystems.
Blueprint Class
Choose when
- Behavior belongs to an object type.
- The project needs multiple instances.
- The behavior must work across maps.
Tradeoffs
- Dependencies and instance references need explicit ownership.
- Map-wide coordination may still need a separate owner.
- Blueprint
- Create an Actor-derived Blueprint Class and place instances where needed.
- C++
- Expose an AActor, APawn, UActorComponent, or other reflected base for Blueprint extension.
Requirements
Both Blueprint types are built into the Engine.
Example
Start a map-specific Level Sequence from the Level Blueprint. Put door behavior in BP_Door so every map can reuse it.