Xorin documentation

FAQ and troubleshooting

Start with the narrowest relevant check. Unity's Console and the Xorin tool rows usually contain more useful evidence than retrying the same request unchanged.

Installation

Xorin does not appear in the Unity menu

Confirm the project is running Unity 2022.3 or newer. Open Package Manager and verify that the Xorin package installed without package-resolution or compilation errors. If Unity cannot download it, confirm Git is installed and available from your terminal, then restart Unity. Return to the installation guide to review the complete setup.

Accounts and providers

A Cloud request says I am unauthenticated or out of credits

Open Settings, sign in again, and check the displayed balance. Authentication errors and credit errors are separate; adding a BYOK key does not fund Cloud mode.

Context and indexing

Xorin cannot find a recently added file

Wait for Unity's asset import and Xorin's workspace indexing to finish; indexing progress and completion are reported in the Unity Console. Try an exact @filename mention. If the asset remains missing, reimport it in Unity and start a new chat to avoid stale conversation assumptions.

The context ring is nearly full

The indicator is informational. Start a new chat, remove unnecessary mentions or images, and put only stable conventions in project memory.

Scripts and compilation

A script request fails during compilation

Expand the tool result and check Unity's Console. Xorin performs bounded automatic repair and then attempts to restore and recompile the affected scripts if it cannot reach a fresh successful compile. If rollback is unavailable or cannot be verified, the result identifies the paths that require manual recovery. Existing project errors can still block verification.

Compilation passed but the feature does not work

Compilation proves that the code compiled, not that runtime references or behavior are correct. Inspect serialized fields, run Play & Check, and reproduce the relevant interaction manually.

Changes and recovery

Should I use Accept All or Undo All?

Expand the Change Log and inspect every accumulated script diff and Unity operation. Accept keeps the whole active checkpoint; Undo restores its baseline. A pending checkpoint may contain changes from multiple requests, and selective per-file acceptance is not currently available.

Why did Auto-Accept not run?

Auto-Accept runs only after normal request completion when every entry accumulated in the active checkpoint succeeded. Cancellations, request errors, partial work, or any failed entry remain in manual review.

Testing and generation

Play & Check did not prove the behavior I expected

It observes a bounded Play Mode window and console errors. It does not simulate every input path or judge game feel. Reproduce the interaction yourself or add project tests.

An asset-generation job failed

Check credits or provider access, then simplify the prompt and confirm supported settings. Provider availability and output formats can change. A failed external generation job may not be recoverable through Undo All.

Known scope boundaries