FAQ and troubleshooting

Confirm the project is running Unity 2022.3 LTS or Unity 6.3+. 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 and confirm the Xorin package appears as installed in Package Manager. Return to the installation guide to review the complete setup.

Open Settings, select Xorin account, sign in again, and check the displayed balance. Authentication errors and credit errors are separate; adding a BYOK key does not add Xorin credits.

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.

Wait for workspace indexing to finish and confirm the item is a supported image, Hierarchy GameObject, component, indexed project folder, script, prefab, ScriptableObject, material, scene, shader or Shader Graph, or allowlisted text, configuration, or Unity UI file. Non-image files and folders must be under the indexed Assets or Packages roots. External non-image files and folders, .meta files, audio clips, animation clips, models, and other non-allowlisted assets cannot be dropped directly. For example, .yaml is supported but .yml is not. Use an @ mention when available.

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

Reuse restores only references that remain available. Re-add any item named in the notice, and review the complete request before sending it. Reuse is disabled while another request is running and asks before replacing an existing composer draft.

Use the inline card to add turns and resume, or select Stop. Open Adjust… to apply the increased limit to this request, this chat, or the device default. This resumes the paused request. See agent turn limits for details.

Xorin preserves the partial response and displays Continue. Select it to start a follow-up request that finishes the incomplete task without repeating completed work. If the composer contains a draft, Xorin asks before replacing it.

Strategy models can spend time reasoning before displaying a response. Xorin 2.1.2 improves handling of these waits and recognizes gateway activity while a response is still being prepared. You can wait for the result or stop the request from the composer.

The service could not complete the response within its allowed time. Review any changes already applied, then retry with a smaller, focused request. Xorin 2.1.2 surfaces gateway timeout details more clearly. If the issue repeats, use the task's Report action to send diagnostic information to support.

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 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.

Select View changes and inspect every accumulated script diff and Unity operation. Keep retains the whole active checkpoint; Undo restores its baseline. A pending checkpoint may contain changes from multiple requests, and selective per-file decisions are not currently available.

Auto-approve 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.

Xorin keeps ordinary successful execution details out of the completed response by default. Open Settings and enable Show detailed work activity to expose the retained steps. Failures and interruptions remain visible regardless of this preference.

Sign in to Xorin, choose a reason, and retry. If the session expired, sign in again and explicitly select Submit report; sign-in does not submit the form. For a size error, remove the screenshot or submit without optional task content. Network failures keep the form available for an explicit retry and are not silently queued.

After submission, copy the confirmation ID shown in the report dialog and include it when contacting support. The task's Report action then shows the submitted ID; selecting it copies the ID again. Older tasks created before request IDs were retained may not be reportable.

Confirm that com.unity.addressables 1.19.0 or newer is installed and let Unity finish compiling and importing. Xorin does not install or upgrade the optional package. If settings do not yet exist, ask Xorin to initialize Addressables before creating groups or entries.

Content builds require an explicitly approved Plan-mode step, an exact existing profile, and a build target equal to Unity's current active target. Content-update builds also require the previous content-state .bin file. Exit Play Mode and wait for compilation, import, or another build to finish before retrying.

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.

For image, 3D, or audio generation, select Xorin account in Settings, sign in, and check your Xorin credit balance. 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 changes.