> For the complete documentation index, see [llms.txt](https://hiveminddocs.gitbook.io/hivemind/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hiveminddocs.gitbook.io/hivemind/code-systems/ultimate-building-system-framework-ubs/tools/collision-channel-fixer.md).

# Collision Channel Fixer

This tool functions very similar to the [Example Content Initializer](/hivemind/code-systems/ultimate-building-system-framework-ubs/tools/example-content-initializer.md), with the difference that you can choose your own buildable definitions and buildable parent actor class to fix.

This tool was created in 1.3.2 to help solve issues with collision channel disperancies in the parent actor class as well as the users custom buildable definitions.

***

### 1. Open the Tool

To open the tool you need to navigate to the Plugins /Content/Tools folder.

<figure><img src="/files/Q0gJ8iFXEQnxOybNQrZu" alt=""><figcaption></figcaption></figure>

From there you will find an asset called `EUW_CoillisionChannelFixer`, right click it and click `Run Editor Utility` Widget.

<figure><img src="/files/XaSs63Y7uaA2xY7DNvbz" alt=""><figcaption></figcaption></figure>

The tool should now appear in a new window.

***

### 2. Set Tool Settings

In here you will be able to set the `Buildable Type`, and two `Invalid Object Types`.

Simply set the `Buildable Type` to `Buildable` and then add two `Invalid Object Types` and set each respectively to `BuildableSocket` and `ConstructibleProxy`.

If you're not using the BP\_Buildable Parent Actor class which comes with the plugin, then make sure to choose your own custom Buildable parent class which you use for all of your Buildables in the class selection, otherwise skip this step.

<figure><img src="/files/5pTAFCUUpVZ3utoi8fsQ" alt=""><figcaption></figcaption></figure>

***

### 3. Select Buildable Definitions Folder

Next, select the folder containing your **custom Buildable Definitions**.

In the **Content Browser**, navigate to and select the **parent folder** that holds all your definitions.\
This allows the tool to **recursively search** through the folder and find all Buildable Definitions that need to be modified.

<figure><img src="/files/MLNbEb6azF2VfUfzkQAl" alt=""><figcaption></figcaption></figure>

> 📌 *In the example above, the `Definitions` folder is selected, which contains the custom Buildable Definition.*

***

### 4. Execute Tool Functionality

After you've **configured the tool settings** and **selected the folder containing your Buildable Definitions**,\
you’re ready to run the tool.

Click the **Fix Collisions** button. When prompted, click **Yes** to continue. The tool will scan the selected folder, apply the necessary changes, and notify you once the assets have been successfully updated.


---

# 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:

```
GET https://hiveminddocs.gitbook.io/hivemind/code-systems/ultimate-building-system-framework-ubs/tools/collision-channel-fixer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
