How to Fix “Can't add script component because the script class cannot be found” in Unity

You drag a script onto a GameObject and Unity refuses with this message. Unity can only attach a MonoBehaviour whose class name matches its file name and which currently compiles. Here is the checklist.

How to fix it

1. Match file name to class name

A class PlayerController must live in PlayerController.cs — exact spelling and case. Rename one side so they match.

2. Fix all compile errors first

If anything in the project fails to compile, Unity cannot register new script classes. Clear the red errors in the Console, then try adding the component again.

3. Derive from MonoBehaviour

Only classes inheriting MonoBehaviour can be attached. A plain C# class or a ScriptableObject will produce this exact error.

4. Check for generics and multiple classes

Generic classes (class Foo<T>) cannot be attached directly, and only the class matching the file name is attachable when a file holds several classes.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.