Who may break a prop, and how hard
Destruction Power, impact speed, health and defense, the Attack Damage Table, Allowed Breakers, indestructible and locked props, breaking from a script, clearing where the player appears, load protection and the launch of the pieces.
A pot shatters at the lightest blow. A door takes three sword hits. A statue shrugs off the sword and falls only to a heavy hammer. A shrine wall never breaks. A barricade only the player may open. Each of these is a rule on the prop’s Behavior, or an exception on one setup or one placed copy, judged on every hit the game sends.
Destruction Power: the first gate
Every hit carries a Destruction Power: None, Very Light, Light, Medium, Heavy or Massive. A hit below the prop’s Minimum Destruction Power only reacts: it can play the hit sound and effect and push the prop, but it does not reduce health, however large its Damage. Its result says Power Too Low. This applies to projectiles too. A hit of power None breaks nothing.
| Built-in Behavior | Minimum Destruction Power |
|---|---|
| Fragile | Very Light |
| Normal, Sturdy, Indestructible | Light |
The demo sword hits at Medium power with 20 Damage.
Impact speed
Minimum Impact Speed is a contact gate in cm/s, so a weapon leaning against a pot never shatters it. The four built-in Behaviors set it to 300 cm/s; a profile created by hand starts at 0. A hit whose measured Impact Speed is below it returns Too Slow. A hit that reports no speed (Impact Speed 0) skips the gate. The melee sender sends 0 unless Begin SDF Melee Swing is given a Swing Speed; the projectile and collision senders send the real speed.
Health and damage
Once the power gate passes, Damage and the Behavior’s multipliers decide the optional health loss.
| Destroy On Single Valid Hit | Use Health | The prop breaks |
|---|---|---|
| On (the default) | Either | On the first valid hit, whatever its health |
| Off | On | When its health reaches 0 |
| Off | Off | On any valid hit |
- Max Health is the health the prop starts with. Damage Multiplier scales each hit’s Damage against health; Impact Damage Multiplier turns the hit’s Impulse Strength into extra damage (0 keeps damage purely conventional).
- Allow Power Override with Instant Break Power (Massive by default) lets a hit that strong break a prop with health at once, whatever health remains.
- Health Mode (new in 2.0.1) says how the health counts. Health Points, the default, lowers it by each hit’s damage, so a strong weapon breaks the prop sooner. Number of Hits breaks it on its Hits To Break-th valid hit (3 by default), whatever each weapon’s damage; a hit under Minimum Damage Threshold does not count, and a body contact still breaks it outright. See Health points or number of hits.
- These are greyed out unless Use Health is on and Destroy On Single Valid Hit is off: a prop that breaks on one valid hit, or has no health, never reads them.
- A hit that took no health returns No Damage; a hit that took some, with health left, returns Health Remains.
The quickest way to a multi-hit prop is the Sturdy Behavior (100 health), or Max Health (0 = Behavior’s) in section 2. How Does It React? of Create Destructible: a value above 0 is written as two exceptions, Override Health and Override Single Hit. At the demo sword’s 20 damage a blow, 50 health breaks on the third. Hits To Break (0 = Health Points), beside it, counts hits instead: the demo door uses 3, and breaks on the third blow of any weapon.
Minimum Damage Threshold and Damage Threshold Blocks Break
Minimum Damage Threshold is the least Damage that reduces health. By default it gates the damage calculation only: a valid power-only hit can still break a prop that breaks on one valid hit, and a health-based prop can survive a zero-damage hit that breaks a single-hit prop. A roll can carry zero Damage and enough power to break a single-hit prop.
Turn on Damage Threshold Blocks Break to make the threshold a defense. Off by default. A hit whose
Damage is below Minimum Damage Threshold then only reacts, even on a prop that breaks on one valid
hit, and returns Below Defense. A hit equal to the threshold passes. Hits tagged
SDF.Source.Collision (pawn contact, a fall) carry no damage number and are never held back by it:
their power decides. One setup or one placed copy can change both through Override Defense.
Attack Damage Table
An attack’s damage to props can differ from its damage to characters. An Attack Damage Table
(USDFAttackDamageTable, a Data Asset) gives each attack its own Damage and Destruction Power
against props, and optionally its own Impulse Strength. Off by default: no table is set.
Each entry of Attacks names an Attack Tag with:
| Field | Default in a new entry |
|---|---|
| Damage | 25 |
| Destruction Power | Light |
| Impulse Strength (behind its own toggle) | 500. Off, the hit keeps its own impulse |
Set the table on a Behavior, on a setup (the profile’s Attack Damage Table), or as the Override Attack Damage Table exception on one setup or one placed copy.
- When a hit’s Gameplay Tags carry an entry’s tag - from a weapon’s Hit Settings, a projectile profile or a radial request - the prop takes that entry’s Damage and power instead of the hit’s own.
- The most specific tag wins: an entry for
Attack.Sword.Heavyis taken before one forAttack.Sword. - A hit that matches no entry, and a prop without a table, keep the hit as it came. Your weapons and their Hit Settings do not change.
- The gates (power, defense, health) then judge the hit as the prop took it, and Diagnose shows it that way.
Who may break it
By default, props break for the player and the enemies alike. Whoever dealt a hit is its Instigator’s
pawn, or the Damage Causer when it is a pawn, or the pawn that fired it (AActor::GetInstigator, set
on projectiles). A player is a pawn or controller a player controls; an enemy is any other. Hits nobody
dealt - a fall, a chain, a script break - are never held back.
On the prop. Allowed Breakers, on the Behavior or as the Override Allowed Breakers exception:
| Value | Who may break it |
|---|---|
| Everyone (the default, as in SDF 1.0) | Anyone |
| Player Only | A player |
| Enemies Only | An enemy |
| Nobody | No attacker |
| Tagged Attackers Only | An attacker whose pawn or controller carries the actor tag set in Breaker Tag |
Tagged Attackers Only with no Breaker Tag lets no attacker break the prop; asset validation reports it
(SDF-DATA-070).
On the attacker, whatever drives it - a Behavior Tree, a State Tree, a marketplace AI or your own code:
- No code: the actor tag
SDF.CannotBreakon the pawn or its controller. That character never breaks a prop. - Its own answer: the SDF Breaker interface (
USDFBreakerInterface) on the pawn or its controller, in Blueprint or C++.CanBreakDestructible(Destructible, Hit)answers for each prop and each hit. A Blueprint that adds the interface must implement the function: an empty one answers no. - One rule for the whole world:
USDFDestructionSubsystem::SetBreakerFilter(Filter)binds a function taking the breaker, the destructible and the hit and returning a bool, for example on your AI manager.ClearBreakerFilter()removes it.
The prop decides first, then the tag, the interface and the world’s filter. A refused hit makes the
prop react - heard, seen, pushed - and returns Not Allowed Breaker. A script break (ForceDestroy)
decides for itself and is never refused.
Indestructible
Tick Indestructible on a Behavior (off by default), or pick the built-in Indestructible Behavior. Hits never damage or break the prop. Each one still plays its Material’s hit sound and effect and pushes it, so the player reads “this does not break”, not “nothing happened”. The result is Indestructible, not Reacted, so the game can tell “this never breaks” from “this hit was too weak”.
Override Indestructible works both ways: one copy of a breakable door can be made to hold, and one copy of an indestructible kind can be made breakable.
Controlling a prop from the game
These calls let a level script or a game system decide for the prop. None of them is saved.
Lock and unlock
SetDestructionEnabled(false) locks an Intact or Damaged prop: every hit, and ForceDestroy, returns
Disabled and changes nothing; the rejection reason is Locked. SetDestructionEnabled(true) gives
the prop back in the state it had, Intact or Damaged, with its health. A broken prop cannot be locked.
The call returns whether the state changed; IsDestructionEnabled() reads it.
ResetDestruction() and a rest at a checkpoint bring a locked prop back whole and still locked. A new
profile or a reload unlocks it, so lock it again from the script that locked it.
Break from a script
ForceDestroy(Params) breaks the prop past every threshold: power, impact speed, projectile policy,
damage threshold and health. Every field of FSDFForceDestroyParams is optional:
| Field | Meaning |
|---|---|
bUseImpactLocation, ImpactLocation | Where the break starts. Unticked, at the centre of the intact bounds |
ImpactDirection | The way the pieces are pushed. Zero: away from the impact point only |
ImpulseStrength | The push |
DamageCauser | Who broke it |
RandomSeed | The break’s seed; -1, the default, picks one |
The hit has Massive power and is tagged SDF.Source.Script. Budgets still apply, and a break that
cannot be shown still rolls back and returns Failed. A locked prop returns Disabled, an
indestructible one Indestructible, a broken one AlreadyDestroyed, and one that has not begun play
yet Ignored. OnDestructionDamageReceived reports the script hit like any other.
Clearing where the player appears
USDFDestructionSubsystem::BreakIntactInSphere(Centre, Radius) breaks every Intact or Damaged prop
whose collision overlaps the sphere, so a player spawning or respawning is never stuck inside one. Each
prop is broken with ForceDestroy, pushed away from the centre, in a stable order. The call returns the
number of props broken.
It leaves alone the props set Protected From Spawn Break (off by default; on their Behavior, or through Override Protected From Spawn Break on one setup or placed copy), indestructible props, locked props and props that have not begun play yet. Call it once the level has begun play.
Settling on load
A prop placed a little above the floor falls into place when the level starts or streams in. With Load Protection Seconds above 0, a landing within that time after the prop appears does not break it. Weapon hits are unaffected. A reset puts a fallen prop back where it was placed, so the protection starts again then. 0, the default, turns the protection off, as in SDF 1.0. The Override Load Protection exception starts at 1 s.
Hit strength and the launch
With Scale Launch By Hit Strength on, a Geometry Collection break throws its pieces faster for a stronger hit. Off, the default, every hit launches the pieces the same way, as in SDF 1.0.
- The multiplier is the hit’s Impulse Strength divided by Reference Hit Impulse (750 by default, the demo sword’s), kept within Launch Scale Range (0.6 to 1.8).
- The pieces’ spin follows the same multiplier up to Maximum Spin Scale (1.5).
- A hit with no Impulse Strength launches normally.
ComputeLaunchScale(HitImpulseStrength)on the profile returns the multiplier, exactly 1 when the option is off.
Whatever the option, no piece is launched back toward whoever broke the prop: the hit’s Damage Causer, or else its Instigator’s pawn. This applies without a setting. Pieces still leave the impact point, but a blow on the side of a crate sends the pieces in front of it sideways rather than at the player. For the first 0.3 s after the break, a piece goes toward that player at 30 cm/s, and faster only as fast as falling and tipping over take it (half of gravity at most): a headstone struck low still topples onto them, but no piece is thrown at them. A hit with neither launches the pieces from the impact point alone.
Weapon recoil
With Weapon Recoils When Held on - on the Behavior, or through Override Weapon Recoil - a melee
blow the prop holds makes the weapon bounce back. A prop holds a blow when it is indestructible or
locked; a prop that breaks, or only loses health, never sends the weapon back. The melee sender sets
bShouldRecoil in its result and fires OnMeleeRecoil, at most once per swing. SDF plays nothing: your
character plays its rebound. Off by default. See
The world reacting to a break and
Melee integration.
Why a hit did not break the prop
Every result carries a RejectionReason. The ones these rules produce:
| Rejection Reason | Rule |
|---|---|
| Power Too Low | Destruction Power below Minimum Destruction Power |
| Too Slow | Impact Speed below Minimum Impact Speed |
| Below Defense | Damage Threshold Blocks Break, and Damage below the threshold |
| No Damage, Health Remains | Health rules |
| Not Allowed Breaker | Allowed Breakers, SDF.CannotBreak, the SDF Breaker interface or the world’s filter |
| Indestructible | Indestructible |
| Locked | SetDestructionEnabled(false) |
Diagnose this object, in the component’s Details, answers in plain words with the values the prop
really plays. See Diagnostics for every reason, and
Destruction hit for the hit structure and
the source tags (SDF.Source.Script, SDF.Source.Collision.Pawn, SDF.Source.Fire and the others) you
can filter on in OnDestructionDamageReceived.
Server decides
In a networked game these rules are judged on the server only; on a client a hit returns Server Decides. See Networked games.
Last updated: 2026-10-29