> For the complete documentation index, see [llms.txt](https://docs.sollumz.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sollumz.org/2.4/documentation/fragments.yft/bone-physics.md).

# Bone Physics

You will notice that each Fragment bone now has a `Use Physics` property.

<div align="left"><figure><img src="/files/qNLRpcDcLxltbtjckCUo" alt=""><figcaption><p>Bone Properties > Sollumz > Fragment</p></figcaption></figure></div>

Enabling this will reveal a `Physics` subpanel where various physics properties can be configured for that bone. The defaults work great for most use cases but feel free to tweak them to get the results you want.&#x20;

{% hint style="info" %}
If you're ever not sure what physics properties to set, import a similar model from the game and copy its physics properties.
{% endhint %}

Most importantly, enabling Use Physics is what causes the bone to react to physics. If this is unticked, any geometry associated with the bone will always remain static in-game. Usually, you'd have a bone for each separable part. That way, all parts of your Fragment will act independently of each other. See the [Prop Setup](/2.4/documentation/fragments.yft/prop-setup.md) page for an example (vehicles also have separable parts but the bone hierarchy is usually much more complex).

{% hint style="info" %}
Strength is what determines how easily the part can be separated. If strength is -1, the part will not separate, but will still react to physics. This can be seen in props with hinging doors such as the container prop shown in [Prop Setup](/2.4/documentation/fragments.yft/prop-setup.md#skeleton-setup).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sollumz.org/2.4/documentation/fragments.yft/bone-physics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.