Casting to Character from Another Blueprint

The character already has a Death custom event that activates ragdoll physics. This lesson changes how that event is reached: a spike Actor detects an overlap, obtains a reference of the expected character type through a cast, and calls the existing event on that character.

The ragdoll setup lesson supplies the event’s behavior. This video does not rebuild the physics asset, damage system, or ragdoll camera. The exact Unreal Engine release is unidentified.

Remove the temporary key trigger without removing the event

At 00:01–01:00, the instructor removes the character’s number-five keyboard connection that previously called Death. A play test confirms that pressing five no longer activates the ragdoll.

The reusable event remains in the character Blueprint. Only its temporary caller is removed. This allows another Blueprint to trigger the same behavior without duplicating the physics operations.

Check that distinction before proceeding: deleting the event itself would leave the environmental Actor with nothing to call, while leaving the key path connected would preserve an extra trigger that is no longer part of the intended interaction.

Build a visible hazard and a separate detection volume

During 01:00–05:02, an Actor Blueprint named Spikes receives a cone component. The cone is scaled into a spike shape and duplicated into a small cluster. A Box Collision component under the scene root defines the region that should detect entry.

The cluster and box are centered and fitted, then instances are placed across the example pit. The box sits around the intended contact area near the spikes’ tops.

The visible geometry and detection volume serve different purposes. Before event logic is added, the character can encounter awkward physical contact with the pointed cones, but that does not yet call Death. A blocking collision with decorative geometry is not proof that the intended overlap event has executed.

Inspect the volume’s location and the actual collision configuration if the character becomes stuck without triggering the behavior. The transcript does not enumerate a complete collision-profile setup for every component.

Cast the overlapping object and call the character event

At 05:02–06:02, the Spikes Event Graph uses Actor Begin Overlap, then Cast to SideScrollerCharacter. The overlap supplies the candidate object reference to the cast, and the successful character reference becomes the target of the Death call.

The cast does not create a new character or broadcast to every character in the level. It provides the expected typed reference when the supplied object is compatible with that character class. The event call then acts on that particular instance.

Keep the execution connection and object reference distinct. The overlap must execute the cast, the cast must receive the object being tested, and its successful result must target the existing character event. A node displaying the right class name is not enough if its Object input or event target is wrong.

The recording does not add a response on the cast-failed path or a reusable interface for different character classes. Its interaction is deliberately specific to the side-scroller character used in the scene.

Test the environmental trigger and retain the remaining work

During 06:02–06:40, entering the spike area activates the ragdoll. The instructor also attempts to jump over the pit and demonstrates that falling into it triggers the same event.

The successful result is environmental access to the existing character behavior. It does not establish health subtraction, a one-time death guard, respawning, camera correction, or general support for unrelated Pawn classes.

Test the two responsibilities independently: the spike volume must identify the intended overlapping character, and that character’s Death event must still perform its existing physics work. This separation lets the hazard change without forcing the ragdoll implementation to be copied into every environmental object.