Choose the workflow on Destructible 2D#
Add the package's Destructible 2D component to a suitable Sprite GameObject and choose Slicing Mode. Each mode has a different source of fragment geometry.
| Mode | Geometry source | Relevant controls |
|---|---|---|
| Auto Grid | A generated grid layout. | Columns, Rows, Jitter and Fracture Seed. |
| Manual | A saved authored layout. | Manual Slice Data and Open Manual Slice Editor. |
| Runtime | Gameplay line, segment or path requests. | Runtime Slice Settings and an API/input source. |
Columns, Rows, Jitter and Fracture Seed belong to Auto Grid. Their presence in the Inspector does not make them the controls for a Manual or Runtime cut.
Inspect the shared settings#
This supplied Inspector capture includes additional visible controls such as Fragment Outline and Performance Profile. Use it to locate UI groups; the guide does not fully specify every field shown. Screenshot values are examples.
Set the Material Profile and the fragment physics options appropriate for your workflow. Polygon colliders follow fragment shapes, Box colliders approximate bounds, and None disables fragment collider contacts. Actual collision response also depends on the physics mode.
The Inspector includes Auto Reset, Scene Grid Preview and cache/play-test controls. For the Auto Grid route, start with the relevant grid fields and use the supplied auto-slice guide video alongside your package's own documentation.
Manual and Runtime have different geometry limits#
Manual polygon authoring supports concave regions and can leave holes or disconnected remainder islands. Runtime Slice source geometry requires a supported single convex contour. Assigning ManualSliceData does not convert an unsupported runtime source into a valid one.
Use manual authoring for precise layouts and Runtime Slice for supported gameplay cuts. The editor window is an Edit Mode authoring tool; it does not perform the gameplay swipe.