Integration examples
The Integration Examples map and its seven small Blueprints that call SDF the way a game does — sword, arrow, a statue that needs Heavy, a rolling boulder, a bonfire rest, save and load — and the nodes that turn a result into plain words.
The Integration Examples map shows, station by station, how a game calls SDF from Blueprint. Each station is a pad on the floor with a title. Step on the pad: the station runs its graph, then writes what happened on its line under the title and on screen, in plain words. When a prop refuses a hit, the line says why and what to do about it.
Open the map
Enable Show Plugin Content, open
/SoulsDestructionFramework/SoulsDestructionFramework/Demo/Maps/L_SDF_IntegrationExamples, then
Play. The Blueprints are in Demo/Integration/Examples: open one to read its Event Graph.
The stations
| Station | Blueprint | What the graph does |
|---|---|---|
| Rest at a Bonfire | BP_SDF_Example_RestAtBonfire | Calls NotifyRestAtCheckpoint(ZoneId) on the SDF Destruction Persistence subsystem. The broken props of that zone come back whole; the line says how many. Leave Zone Id at None to rest every zone. Break the pot beside it first. |
| Sword Hit | BP_SDF_Example_SwordHit | An SDF Melee Hit Sender opens a swing (Begin SDF Melee Swing), a line trace finds the prop, Send SDF Melee Hit delivers it, and the swing closes (End SDF Melee Swing). The sender’s Hit Settings choose the Damage and Destruction Power: 25, Light. |
| Sword Hit: This Statue Needs Heavy | the same Blueprint | The statue placed in front has one exception on this copy: Minimum Destruction Power Heavy. The sword is Light, so the statue holds the blow and the line says it was not strong enough. |
| Arrow Hit | BP_SDF_Example_ArrowHit | What a game’s own arrow does on impact: an SDF Projectile Hit Sender with the DA_SDF_Projectile_Arrow profile sends the hit with the arrow’s velocity, here 3000 cm/s toward the prop. |
| Rolling Boulder | BP_SDF_Example_RollingBoulder | A charge, a roll or a thrown object: the game detects the contact and chooses its Damage and Destruction Power. The station opens a window on its SDF Collision Hit Sender (Begin SDF Collision Window) and rolls the boulder at the crate. On the boulder’s On Component Hit with the crate, Send SDF Collision Hit delivers the contact with Damage 100 and Power Heavy, variables you can change on the placed copy. |
| Save the Broken Props | BP_SDF_Example_SaveProps | Exports the records with Get Persisted Destructions, keeps them in the game’s own save game (BP_SDF_Example_SaveGame, one array variable) and writes it to the slot SDF_Examples. Break the pot beside it first. |
| Load the Broken Props | BP_SDF_Example_LoadProps | Reads the slot and hands the records back with Apply Persisted Destructions: the saved props break again, with no sound, effect or debris replay. Rest at the bonfire between the two to see the pot come back, then break again on load. With nothing in the slot, the line says so. |
Reuse a station in your project
Copy its Blueprint, place it and set its Target (under SDF Example) to your prop. The pad, the trace and the lines on screen are only there for the demonstration: in a game, the same calls go in the weapon, the projectile, the character or the checkpoint.
- Your whole character - its sword, its roll, its arrows and fire arrows - mostly without code: Your own character.
- A sword: Melee integration.
- A roll, a charge or a thrown object: Roll and collision integration.
- An arrow: Projectile integration.
- A bonfire, a death, a save: Broken props remembered.
- A statue that needs a stronger blow: Exceptions for one setup or one prop.
Notes on the graphs
- The collision speed. A contact reported by On Component Hit arrives after the physics solver has already slowed the body, often below the sender’s Minimum Contact Speed (200 cm/s by default). The boulder’s graph sends the speed it was rolled at, toward the prop. In your game, send the speed of the charge or of the throw.
- One delivery per window. The collision sender ignores repeated contacts with the same actor in one window (Suppress Repeated Actors Per Window): the boulder bouncing on the broken crate is not another hit. The graph writes the first delivered contact only.
- Refusals are results, not errors. Every send returns its delivery result; its Destruction Result holds the outcome and the rejection reason. The examples write them with the nodes below.
Results in plain words
Three pure nodes, under Souls Destruction > Diagnosis, turn a result into one sentence for an on-screen message, a log or a debug widget. They work in packaged games and are localizable.
| Node | Example of what it returns |
|---|---|
| Describe SDF Result | Broken. / Broken into 6 pieces. (loose debris) / Damaged: 40 health left. / It held the blow. Not strong enough: ... / Refused. Too slow: ... |
| Describe SDF Radial Result | The explosion reached 5 props: 2 broken, 1 damaged, 2 unharmed. 3 behind cover. A prop that held the blow lost no health: it counts as unharmed. |
| Describe SDF Rejection Reason | Why a prop refused the hit and what to do about it, for each rejection reason. Empty for None. |
A Geometry Collection break counts as one spawned actor, so Describe SDF Result says Broken.
for it, without a piece count. The rejection reasons, and the Diagnose this object panel that
explains them in the editor, are described in
Diagnostics.
Scope limitation
The pads react to the player’s pawn only. The slot SDF_Examples is shared by every play session of this map: Load applies the last save, even one from an earlier session. The texts are in English.
Last updated: 2026-10-29