# Troubleshooting

{% hint style="danger" %}
**Updating from 1.0.5 or earlier?** There are some breaking changes to how references work. Check the updated troubleshooting before installing → [Read more](https://docs.fullscreen.no/info/game-creator-2-assets/logicblock/pages/6YhdytcM9T30EvJTVOtq#updating-from-1.0.5-to-1.0.6)
{% endhint %}

## Restart Instructions

When creating instructions that **run over time,** such as continuously rotating a GameObject, you may want to **restart the instruction list** to create a loop.

**Important: Always Wait 1 Frame**

Before restarting the instruction list, **add a `Wait 1 Frame` instruction**.\
This brief delay allows Unity to finish processing the current frame and ensures the loop continues smoothly.

**Why This Matters**

Restarting the list without waiting a frame can trigger an **immediate infinite loop**, overwhelming Unity’s update cycle.\
This can cause the **editor or game to freeze.**

***

## **Open for Full Editing Support**

You cannot edit any of the references inside the **Run Instruction Block List** or **Run Conditions Block List** instructions **of a prefab** unless you:

* Open the prefab in **Prefab Mode**, or
* Have an instance of the prefab in the scene.

**Why This Happens**

Unity prevents deleting a prefab asset if it is open in the Inspector due to how our references logic is set up. Because of this, editing references inside these specific block list instructions directly on the prefab asset is blocked to avoid conflicts.

**What This Means**

* To edit these references, open the prefab in Prefab Mode or edit an instance of the prefab in your scene.

***

## Updating from 1.0.5 to 1.0.6 or later

There are some potentially breaking changes to how **references** are handled in this update. We’ve tried to make it as painless as possible, but because there are so many different ways to use LogicBlock, the safest way to update is:

1. **Take a backup** of your project.
2. **Uninstall** LogicBlock.
3. **Install** LogicBlock again from the Package Manager.
4. **Restart Unity** (this one’s important).

We normally avoid breaking changes like this, but this one was needed to fix an important issue where reference values could sometimes become linked.

#### What’s Changed

* **Fixed:** New references made after 1.0.6 will no longer link their values together.
* **Backwards Compatibility:** We’ve added a system to try to keep your current reference values as they are. That said, there may be edge cases where you’ll need to re-assign some.
* **Important:** The fix won’t touch old linked references from 1.0.5. This is to avoid accidentally deleting or changing your existing data.

#### Caveat

Before making new references, you **must** have inspected the GameObjects with the **Run Instruction/Condition List** instruction at least once. This triggers the backwards compatibility check and marks the old references as safe.

If you spot missing references, **try** to unload the scene and load it again (don’t save before doing this).

**Tip:** To unlink a shared reference value, simply change the property type on the last reference.


---

# Agent Instructions: 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://docs.fullscreen.no/info/game-creator-2-assets/logicblock/troubleshooting.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.