Blueprint function vs custom event vs macro: when to use each

BLUEPRINT FUNCTION: - Has its own execution context, can have inputs/outputs/return value. - Cannot have Delay, Timeline, or latent nodes inside. - Best for: pure logic, calculations, data transformation. - Can be overridden in child BPs (if not pure).

CUSTOM EVENT: - Lives in event graph, can be called like a function. - CAN have Delay, Timeline, latent nodes. - Can be Replicated (Server/Client/Multicast). - No return value. Best for: triggered behavior, RPC calls.

MACRO: - Inlined at call site — like a code template. - CAN have multiple exec inputs AND outputs. - CAN contain latent nodes. - Best for: reusable flow patterns (e.g. 'IsValidAndCast' check-and-cast pattern).

PURE FUNCTION: checked 'Pure' — no exec pins, evaluated on demand. Best for getters.