> For the complete documentation index, see [llms.txt](https://slashin8r.gitbook.io/universal-monster/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://slashin8r.gitbook.io/universal-monster/features/monsters/character-blueprint/collision.md).

# Collision Settings

Since **Universal Monster** is also a complete combat system with hit detection, collision settings are very important to understand. **UM** is capable of working with any custom collision channels and object types that you may add for your project. Depending on how accurate you want the hit detection to be, there will be some alterations you may need to make to the default collision settings of the **Capsule Component** and the **Skeletal/Static Mesh Components**.

## Bone Hit Detection

If it is important that you are able to determine which specific bone was hit, then you will want to make sure your Capsule Component is not triggering the hits. In the following example, the hit detection traces are being done on the Visibility channel.

### Capsule Component

![As you can see, Visibility is set to Ignore for the Capsule Component](/files/-MjK76sJKQUnfjKyn6C2)

### Skeletal Mesh Component

![The Skeletal Mesh Component is set to Block the Visibility channel](/files/-MjK6iSAnEkp4PFsFbgS)

## Simple Hit Detection

If you do not care to track the specific bone that was hit, then you can let the Capsule Component handle the hit detection and turn off collision for the Skeletal Mesh.

### Capsule Component

![You can simply use the default Pawn Collision Preset, but I prefer to Ignore the Camera channel so that the characters do not change the player camera position](/files/-MjK5hTBIbqJ4-coio28)

### Skeletal Mesh Component

![For simple hit detection, we do not care to even test if the skeletal mesh was hit](/files/-MjK7iyhmtNHzY24jO4i)

## Trace Settings

**Universal Monster** allows you to set custom trace settings for every attack, projectile and special attack. You can find more information on the **Trace Info** by clicking the link below.

{% content-ref url="/pages/-MbsNbk3NtEuq9TGGynA" %}
[Trace Info](/universal-monster/features/combat-system/trace.md)
{% endcontent-ref %}


---

# 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://slashin8r.gitbook.io/universal-monster/features/monsters/character-blueprint/collision.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.