Blueprint ↔ C++ integration

The boundary between C++ and Blueprint is defined entirely by reflection specifiers declared in UHT macros. Getting them right produces a clean, designer-friendly API; getting them wrong means nodes don't appear, properties don't show, or events never fire. This is the contract layer of the "C++ base + Blueprint subclass" pattern.

When to use this skill

• Choosing UFUNCTION/UPROPERTY/UCLASS specifiers to expose C++ to designers.
• Letting Blueprints override or implement C++ behavior via events.
• Building a Blueprint function library of static helpers.
• Passing class references or soft assets between C++ and Blueprint.
• Defining a shared interface contract implementable in C++ or Blueprint.

Mental model: what UHT generates