> For the complete documentation index, see [llms.txt](https://postica.gitbook.io/binding-system-3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postica.gitbook.io/binding-system-3/project-tools/diagnostics/errors.md). # Error Visualization What a red bind field is telling you, and what to do about it. A binding that cannot work says so, on the row, at authoring time. Nothing is fixed for you: an automatic repair would hide a side effect you probably want to know about. That covers the binding in front of you. For the same question across a scene or a whole project, run the [Bindings Validator](/binding-system-3/project-tools/diagnostics/validator.md), which reports the same problems and a number of others that only show up once a path is actually resolved.

## Reading the row An **error point** appears at the start of the row. Hover it, or the field it marks, for the reason. The part of the row that is at fault is highlighted, so a source problem and a path problem look different.

Highlighted	What it means
Source	The source is missing, of the wrong type, or not allowed here.
Path	The path no longer resolves, or was never set.
Mode	The mode and the target member disagree.
Parameters	A method or indexer parameter is missing or invalid.
Component	The component the path went through is gone.

## The messages ### Source problems

Message	What it means
No source set	Nothing assigned. If the binding genuinely needs no source, use Nothing from the bind path menu instead of leaving it empty.
Requires <Type>	The path expects a component of that type. Assign one, or change the path.
missing <Type>	The assigned object no longer has that component.
Assets NOT Allowed / Scene Objects NOT Allowed	An attribute on the field restricts what can be assigned. Odin's `[AssetsOnly]` and `[SceneObjectsOnly]` produce these.
Missing Script	The component's script could not be loaded, so there is nothing to bind to. Fix the script reference first.

### Path problems

Message	What it means
No path set	A source is assigned but nothing was picked. Click the row.
A path shown in red	The member is gone. This is the case Refactoring exists for: it can often find where the member moved to.
The selected path cannot be bound because there is no source object set	The path is fine, the source is not.

### Source mode problems Each source mode reports its own missing piece:

Message	What it means
No variable selected	Variable mode with nothing chosen.
Variable 'x' not found	The variable was renamed away, or its container is gone. See Bind Variables.
Variable 'x' is of type A, which cannot be bound to B	Both types are named, so the mismatch is unambiguous.
No tag set, No pattern set, No context set	The mode's own field is empty.
No type selected	The mode needs a component type to look for.
Type Not Found: x	The stored type no longer exists, usually after a class rename. See Refactoring.

### Multi-selection notes Not errors, but worth recognising:

Message	What it means
Incompatible Types	The selected objects have no common type, so a single path cannot be set for all of them.
Multiple Components of the same GameObject are used	A warning: the selection includes several components of one object.
Converters editing is not allowed with multi selection	Converters and modifiers can be added across a selection, but their inner values cannot be edited for several objects at once.

## The status light on name-based sources Modes that resolve by name, tag or pattern do not fail loudly, because at authoring time the object might legitimately not exist yet. They show a [status light](/binding-system-3/overview/sources.md#the-status-light) instead: green for a match, yellow for a name match with the wrong component type, red for nothing found. Clicking it highlights what it found. ## Where else errors appear

Place	What it shows
Live Debug	Runtime exceptions inside the pipeline, with message, source and stack trace, shown at the stage that threw.
Bindings Monitor	Bindings whose status is not healthy while the game runs.
Bindings Dependencies	Every binding in the project, so the ones that no longer resolve are visible in one list rather than one scene at a time.
The Console	Runtime failures, prefixed so they are easy to filter.

{% hint style="success" %} Before a release, open [Bindings Dependencies](/binding-system-3/project-tools/diagnostics/dependencies.md) once. It is the only view that catches a broken binding in a scene nobody has opened for a month. {% endhint %}