Your own character

Wire your game's own characters into SDF with the 2.0.1 integration kit - swords with SDF Weapon Trace and the SDF Melee Window notify, rolls and charges with SDF Body Hit and the SDF Body Window notify, arrows with SDF Projectile Impact and SDF Projectile Movement, fire arrows with SDF Fire Arrow - mostly without code.

SDF breaks props with whatever your game’s characters already do: their swords, their rolls, their arrows. Swing your hero’s axe through a crate and it breaks; roll through a row of pots and they shatter; loose an arrow from your own bow and it plants in a barrel or flies on through a bottle. The demo character is a reference, not a requirement. This page wires your own character in, mostly without code, with the integration kit added in 2.0.1.

Your character…AddThen
swings a sword, an axe, a clubSDF Weapon Trace on the weaponthe SDF Melee Window notify on each attack montage
rolls, charges, bargesnothing, or SDF Body Hit on the characterthe SDF Body Window notify on the roll’s montage
shoots arrows or boltsSDF Projectile Impact and SDF Projectile Movement on the arrowa Projectile Profile with the arrow’s power
shoots fire arrowsSDF Fire Arrow on the arrow as wellnothing

Each one sends ordinary SDF hits: every rule of the prop - its Behavior, Material, exceptions, power gate, projectile policy - applies, and Diagnose this object tells you why a hit did not break it. Any character could always break props by sending its hits through SDF’s hit senders from its own code; that still works, and the kit does it for you. See Melee integration for the steps the kit automates.

Swords, axes and clubs: SDF Weapon Trace

  1. Open the weapon’s Blueprint (or the character’s, if the weapon’s mesh is one of its components) and Add Component > SDF Weapon Trace (USDFWeaponTraceComponent).
  2. On the weapon’s mesh, add two sockets: BladeBase at the guard and BladeTip at the point. Without them the blade runs along the mesh’s longest axis, from its pivot (where the hand holds it) to its far end. Weapon Mesh picks the mesh when the actor has several. On a character that carries the trace itself, pick Weapon Mesh or add the sockets: its body is never read as a blade, and the Output Log says so.
  3. Give the weapon its strength against props: Add Component > SDF Melee Hit Sender on the same actor and set its Hit Settings - Damage, Destruction Power, Impulse Strength. Without one, the trace adds a sender with the defaults (25, Light, 500): Light breaks Normal props (crates, barrels, furniture) and Fragile ones (pots, bottles).
  4. On each attack montage, add the notify state SDF Melee Window over the frames that strike.

Tick Override Hit Settings on a window for an attack that hits harder - a heavy attack, a plunge: for that window its Damage, Destruction Power, Impulse Strength and Damage Type replace the weapon’s, and its Gameplay Tags are added to the weapon’s. The weapon’s own settings do not change. From Blueprint, Begin SDF Weapon Trace (or Begin SDF Weapon Trace With Hit Settings) and End SDF Weapon Trace do the same as the notify.

What the trace does

While a window is open, the trace sweeps spheres of Trace Radius along the blade every frame, each from where that point of the blade was to where it is, so a fast swing misses nothing between two frames.

  • It queries WorldStatic, WorldDynamic, PhysicsBody and Destructible objects: a prop’s hit assist, its collision box and its simulated mesh. Because it queries by object type, it also finds an animated prop’s Weapon Hit Assist and the hit assist of a prop set to Use Mesh Collision When Intact.
  • Every part it touches is sent, once per window: a stained-glass window’s panes are reached even when the blade met its stone frame first.
  • It skips its wielder, and the blade behind the wielder - a wind-up over the shoulder - strikes nothing.
  • The notify finds the traces the character wields: its own, and those of the actors attached to it - a weapon actor held in a hand socket - but not those of another character attached to it, a rider on its back.
  • An attack’s window that begins before the previous one ends merges with it: the trace stays open until the last ends, one hit per part of a prop. A weapon dropped or thrown during the window stops striking, and a window whose end never comes closes by itself soon after.
  • Nothing happens in the animation editor’s preview.
SettingDefaultWhat it does
Weapon MeshemptyThe weapon’s mesh, a component of this actor. Empty: its first mesh with both blade sockets, or else, on a weapon, its first mesh
Blade Base SocketBladeBaseWhere the blade begins: a socket at the guard
Blade Tip SocketBladeTipWhere the blade ends: a socket at the point
Trace Radius6 cmThe radius of the spheres swept along the blade; never under 0.5 cm
Reach Below Blade0 cmHow far below the blade each point reaches, so a high slash still strikes a low pot. Never below 10 cm above a wielding character’s feet
Ignore Behind WielderonThe blade behind its wielder strikes nothing
Draw Debug (advanced)offDraws the blade’s path while a trace is open, in development builds

Is Tracing, Get Melee Hit Sender, Get Effective Hit Settings and Get Wielder read its state from Blueprint.

Rolls, charges and barges: SDF Body Hit

  1. Add the notify state SDF Body Window to the roll’s montage, over the frames whose body should break props. That is all: a character without SDF Body Hit (USDFBodyHitComponent) gets one when the window first opens.
  2. To choose the body’s strength, add SDF Body Hit to the character yourself: Damage (0 - a roll breaks what its power allows and takes no health) and Destruction Power (Light). Tick Override Power on a notify for a move that hits harder, a charge.

While the window is open, whatever the character’s capsule (or the Body component you pick) runs into - a prop’s collision, which answers with a hit, or its hit assist, which it passes through - is sent to SDF with the character’s speed, once per part of a prop per window. A prop it already stands in when the window opens is struck too. The contacts go through the character’s SDF Collision Hit Sender, added if it has none; its Minimum Contact Speed (200 cm/s) refuses a contact slower than a walk.

Outside a window, walking into a prop does nothing here. To let a mere touch break pots and bones, use the Contact module instead: see Bodies against props.

From Blueprint, Begin SDF Body Window, Begin SDF Body Window With Power and End SDF Body Window do the same as the notify; Is Body Window Open, Get Contact Damage and Get Contact Power read its state. See Roll and collision integration.

Arrows and bolts

The adapter. Add SDF Projectile Impact (USDFProjectileImpactComponent) to the arrow’s actor and replace its Projectile Movement with SDF Projectile Movement (USDFProjectileMovementComponent), its settings copied - speed, gravity, the collision body as its Updated Component - with the adapter’s Auto Handle Component Hit and Auto Apply Reaction on. Together they send the arrow’s hits and apply SDF’s answer: the arrow plants in wood, glances off stone and metal, flies on through what it broke.

Unreal's own Projectile Movement stops on every hit

Unreal’s Projectile Movement stops on every hit it does not bounce off, after the hit event, whatever that event did: an arrow it moves freezes in the first prop it breaks. The adapter alone on it cannot guarantee the glance or the fly-through. Give such an arrow SDF Projectile Movement, or a movement whose HandleBlockingHit flies through the contact the arrow chose to continue through.

An arrow that keeps its own movement code uses the plain SDF Projectile Hit Sender, or the adapter with Auto Apply Reaction off, and applies the delivery result’s Projectile Reaction itself: Embed, Deflect along Deflected Direction, Continue, Stop. On Continue it ignores the prop it broke (Ignore Actor When Moving) and keeps its velocity; SDF has its body ignore the pieces that break made, so it flies on to the next prop - two bottles in line both break. A pooled arrow calls Reset SDF Projectile Impacts when it is reused. See Projectile integration.

Its power. Assign a Projectile Profile (USDFProjectileHitProfile). Without one the arrow sends nothing. Its Destruction Power is Very Light by default: it breaks Fragile props - pots, bottles, glass - and a Normal crate or barrel answers Power Too Low. Set Light for arrows that break crates, barrels, chains and ropes. See The Projectile Profile.

Its collision. The arrow’s collision must block PhysicsBody as well as WorldStatic and WorldDynamic. A prop that simulates, or that projectiles strike on its mesh only (Projectiles Strike Its Mesh Only, on by default), is met through its PhysicsBody mesh: an arrow that ignores PhysicsBody flies through it.

Fire arrows. Add SDF Fire Arrow (USDFFireArrowComponent) to the arrow and place it on the arrow’s wrap, a little behind its tip. While it burns, every hit the arrow sends carries SDF.Source.Fire, so a Flammable prop catches even when its policy lets the arrow stick without breaking it. It carries its flame (NS_SDF_FlamingArrow) in flight and where it plants; water puts it out, and a put-out arrow lights nothing. See Fire arrows and Fire and burning props.

Hanging props. A cage or a lantern hung by an SDF Breakable Attachment keeps its hit assist below the top of its mesh, so an arrow aimed at its chain or rope reaches it rather than glancing off the prop. See Hanging props.

In a networked game

The server decides every break; see Networked games. The kit’s windows open on the server, and in single player; on a client they do nothing. So:

  • The attack and roll montages must play on the server, as they do for the game’s own melee damage.
  • On a dedicated server the character’s mesh must move its bones: set its Visibility Based Anim Tick Option to Always Tick Pose and Refresh Bones, or the blade’s sockets stay where the last rendered pose left them.
  • Arrows follow the same rule: the server’s arrow sends the hits.

Props your weapons hit hard

Your game’s damage numbers are its own: a door with 50 health points takes three blows of the demo sword’s 20 and one blow of a weapon dealing 60. For props that should take the same number of blows whatever the weapon, set Health Mode to Number of Hits and Hits To Break - on the Behavior, the setup, or one placed copy’s health exception; Hits To Break (0 = Health Points) in Create Destructible, Batch Generate and Modify Destructible. The demo door breaks on its third blow this way. See Health points or number of hits.

When a hit does nothing

Select the prop and use Diagnose this object: it lists the last hits it received, what each carried and why it held - Power Too Low, Too Slow, Projectile Policy, Below Defense. A hit that never appears there never reached SDF: check the trace’s window (Draw Debug), the arrow’s collision, or that the sender found a target. See Diagnostics.

Where next

Last updated: 2026-10-29

Type to search titles, sections and keywords.