Debugging Unity Errors With AI: What to Paste and What to Ask

Pasting a red Console line into ChatGPT or Claude and asking “fix this” sometimes works. Often it gets you a confident patch that hides the bug instead of fixing it. Debugging Unity errors with AI works far better when you give it what a senior developer would ask for: the full stack trace, the code at the right lines, how you got there, and a request for likely causes before any fix. This guide shows exactly what to paste, what to ask, and how to spot a wrong answer before it costs you an evening.

Get the Full Error and Stack Trace

The one-line message in the Console list is only the headline. Click the error and look at the lower pane of the Console window. That shows the full message and the stack trace: the chain of method calls that led to the error, newest first, with file paths and line numbers.

NullReferenceException: Object reference not set to an instance of an object
PlayerHealth.TakeDamage (System.Single amount) (at Assets/Scripts/Player/PlayerHealth.cs:27)
EnemyAttack.OnTriggerEnter (UnityEngine.Collider other) (at Assets/Scripts/Enemy/EnemyAttack.cs:19)

Read it bottom-up for the story: a trigger fired in EnemyAttack at line 19, which called TakeDamage, which crashed at line 27 of PlayerHealth.cs. That top line with your script name is where to look first.

To copy it, select the error in the Console and press Ctrl+C (Cmd+C on Mac), or select the text in the lower pane. If the Console is flooded, turn on Collapse and look at the first error that appeared. Later errors are often side effects of the first one.

When the Console isn’t enough, the Editor log has everything, including errors from before the Console was open. Open it from the Console’s three-dot menu with Open Editor Log.

What to Paste (and What Not To)

A good debugging message has five parts. Missing any of them forces the AI to guess:

1. The full error and stack trace, copied exactly. Don’t paraphrase. “Null error in health” loses the line number and type.
2. The code at the top frames. The whole method that crashed, plus the caller if it’s one of yours. Mark the line: // line 27. Line numbers are useless to the AI without the code they point to.
3. The setup. Which GameObject has the script, what’s assigned in the Inspector, whether it’s a prefab instance or spawned at runtime.
4. How to reproduce. “Happens when the second enemy touches the player, never the first.” Timing details like this often are the bug.
5. Your versions. Unity 6, URP, Input System, any relevant packages. The fix for Unity 2019 can be wrong for Unity 6.

Don’t paste your entire project or a 600-line manager class. More code is not more context. It buries the important lines and gives the model more places to invent a theory. Paste the frames from the stack trace, then add more only if the AI asks for a specific class.

If you use an agent that reads your project files directly, you can skip pasting code. Give it the stack trace and it can open the files itself. Still tell it the setup and how to reproduce, because those aren’t in any file.

Ask for Causes, Not Patches

“Fix this” invites the quickest change that makes the error go away. For a NullReferenceException that’s a null check, which hides the real problem. Ask a different question:

Unity 6, URP, Input System. Here’s the error, the stack trace and the two methods in it. Don’t write a fix yet. List the three most likely causes, most likely first. For each one, tell me how to confirm or rule it out in the Editor (what to check in the Inspector, or a Debug.Log to add).

This gets you a checklist instead of a guess. You test the top cause in a minute, then come back with the result: “Cause 1 ruled out, healthBar is assigned on the prefab. Cause 2 confirmed: the spawned enemy calls TakeDamage before Awake runs.” Now the AI’s next answer is grounded in facts from your project.

The “how to confirm” part matters most. It turns the AI into a debugging partner instead of a patch generator. The same techniques work without AI too. Our Unity debugging guide shows how to use breakpoints and Debug.Log to check each theory.

A Worked Example: NullReferenceException

Here’s the code behind the stack trace above:

public class PlayerHealth : MonoBehaviour
{
    [SerializeField] float maxHealth = 100f;
    [SerializeField] HealthBar healthBar;
    float current;

    void Awake() => current = maxHealth;

    public void TakeDamage(float amount)
    {
        current = Mathf.Max(0f, current - amount);
        healthBar.SetFill(current / maxHealth);   // line 27
    }
}

Asked “fix this”, many assistants answer with this:

if (healthBar != null)
    healthBar.SetFill(current / maxHealth);

The error disappears. The health bar also silently stops updating, and you’ve lost the message that told you why. Asking for causes gets you the real candidates: healthBar isn’t assigned on this instance; the player was spawned from a prefab and the health bar lives in the scene, so the prefab can’t reference it; or the health bar object was destroyed on a scene change.

In this case the player is spawned at runtime and the bar is a scene object, so the prefab field is empty. A real fix makes the dependency explicit and fails loudly:

using UnityEngine;

public class PlayerHealth : MonoBehaviour
{
    [SerializeField] float maxHealth = 100f;
    [SerializeField] HealthBar healthBar;
    float current;

    void Awake()
    {
        current = maxHealth;
        if (healthBar == null)
            Debug.LogError($"{name}: HealthBar not assigned. Call SetHealthBar after spawning.", this);
    }

    // The spawner passes in the scene's health bar right after Instantiate.
    public void SetHealthBar(HealthBar bar)
    {
        healthBar = bar;
        healthBar.SetFill(current / maxHealth);
    }

    public void TakeDamage(float amount)
    {
        current = Mathf.Max(0f, current - amount);
        if (healthBar != null) healthBar.SetFill(current / maxHealth);
    }
}

The null check in TakeDamage is fine now, because the missing reference is reported clearly in Awake and there’s a proper way to provide it. Passing this as the second argument to Debug.LogError makes clicking the message highlight the object in the Hierarchy. For the other common causes of this error, see our NullReferenceException guide.

Spotting Confident Wrong Fixes

AI never sounds unsure, so you need your own filters. Be suspicious when the suggested fix:

• Only silences the error. Null checks, empty try/catch blocks, or if (index < list.Count) guards that skip the work. Ask: “Why is it null in the first place?”
• Changes timing to make it work. Moving code from Awake to Start, adding yield return null, or editing Script Execution Order. Sometimes right, often just hiding an ordering bug.
• Touches settings you didn’t mention. Project Settings, Player Settings or package versions, for a bug in one script.
• Rewrites far more than the broken line. A 60-line rewrite for a one-line bug brings new bugs with it.
• Uses an API you haven’t seen. Check it exists before trying it. Our guide to hallucinated Unity APIs shows how to spot them fast.

The best test: ask the AI to explain why the error happened in one or two sentences, in terms of your project. If it can’t connect the fix to a cause you can confirm, don’t apply it.

Also commit before trying fixes. If an AI fix makes things worse, git restore gets you back in seconds, and you don’t end up stacking three half-fixes on top of each other.

Build, Shader and Package Errors

Not every Unity error has a C# stack trace. Different errors need different pastes:

• Android build failures. The Console shows a long Gradle log and a final “Gradle build failed”. The useful line is usually higher up, starting with FAILURE: Build failed with an exception or * What went wrong:. Paste that section, not the last line. Our Gradle build failed guide covers the common causes.
• Shader errors. Select the shader asset and copy the errors from its Inspector, along with the shader code and your render pipeline. “Pink material” alone tells the AI nothing.
• Package errors. Paste the error plus Packages/manifest.json. Version conflicts are often visible right there.
• Errors with no stack trace, like “The referenced script on this Behaviour is missing!”: these are asset problems, not code problems. Describe what you changed recently (renamed a file, deleted a folder, pulled from git).

Troubleshooting

MissingReferenceException: The object of type ‘GameObject’ has been destroyed but you are still trying to access it.

Something kept a reference after Destroy, often an event subscriber that never unsubscribed. Tell the AI what destroys the object and paste the subscribe and unsubscribe code.

IndexOutOfRangeException: Index was outside the bounds of the array.

Paste the loop and how the array is filled. Ask whether the array can be empty or shorter than expected at that moment, rather than accepting a bounds check.

The AI’s fix works in the Editor but breaks in a build

Mention it’s build-only. Common causes are code in #if UNITY_EDITOR, editor-only APIs, or execution order differences. Paste the Player log from the build.

The AI asks for code I don’t have

It may be inventing a structure. Say “that class doesn’t exist in my project” and paste the real one.

The same error keeps coming back after each fix

Stop patching. Start a new chat, paste the original error and the current code, and ask for causes and checks only.

FAQ