Available since Xorin 2.1.0

Addressables that work after compilation.

Xorin inspects how your Unity project already uses Addressables, makes bounded changes, validates the configuration, builds content, and verifies an exact scene at runtime.

Start free trial See the workflow

7 days · $40 in credits · No card required

X ADDRESSABLES RUN
Unity 2022.3 · Xorin 2.1.0
TASK Prepare and verify the boss encounter
Verified
  1. ✓
    Inspected project conventions 6 groups · 2 profiles · existing loader found
    read-only
  2. ✓
    Configured exact entries Prefab and scene registered with approved keys
    reviewed
  3. ✓
    Validated Addressables 0 errors · 1 item flagged for manual review
    passed
  4. ✓
    Built development content Active Android target · previous profile restored
    complete
  5. ▶
    Loaded exact scene key encounters/boss-temple is active in Play Mode
    runtime
Exact key verified Manual review preserved
Inspect firstFollow the project you have
Use Unity APIsBounded, semantic changes
Approve buildsLong-running work stays explicit
Verify runtimeTest the exact configured key
01 / THE PROBLEM

A clean compile is not runtime proof.

Addressables problems often survive compilation. The wrong key, incompatible reference, or mismatched path can fail later during a content build or when the player tries to load it.

KEY_404
" "

Invented or stale keys

Generated code can compile while pointing at an address that does not exist.

REF_TYPE
{ }

Broken references

An AssetReference may be unresolved or incompatible with its field.

PATH_PAIR
⇄

Mismatched paths

Profiles can contain unresolved or inconsistent build and load path pairs.

SCENE_MODE
▶

The wrong scene workflow

An Addressable scene is not the same as opening a scene asset for editing.

02 / THE WORKFLOW

From project state to runtime evidence.

One supported workflow, with the project conventions and approval boundaries visible at every consequential step.

  1. 01

    Inspect

    Read settings, profiles, groups, schemas, entries, labels, scenes, loaders, exact keys, and references.

    Read-only
  2. 02

    Configure

    Create supported groups, manage entries and labels, and set exact addresses without resetting existing settings.

    Reviewable
  3. 03

    Integrate

    Follow the project's loader and key conventions, generate compatible code, and assign supported references.

    Project-aware
  4. 04

    Validate and build

    Report configuration evidence, then run an explicitly approved build against the active target.

    Approval required
  5. 05

    Runtime-test

    Resolve an exact configured scene address, load it through Addressables, and verify that it becomes active.

    Verified
03 / DEVELOPER CONTROL

The agent acts. You keep the boundary.

Inspection and validation stay read-only. Supported mutations are visible for review. Content builds require explicit Plan-mode approval. Runtime tests use the exact configured key instead of a guessed substitute.

Read about safety and change review
?
AskInspect and validate without changing the project
READ-ONLY
≡
PlanReview steps before consequential work begins
APPROVAL
↺
ChangesKeep or Undo supported project mutations
REVIEW
✓
EvidenceRead back configuration and report runtime results
VERIFY
04 / SCOPE

Clear capabilities. Clear limits.

Addressables support is optional and activates when com.unity.addressables 1.19.0 or newer is installed. Xorin does not add, remove, or upgrade the package automatically.

Unity2022.3+ Addressables1.19.0+ Xorin2.1.0+

✓ Supported today

  • Settings, groups, profiles, entries, keys, and labels
  • Supported group and entry configuration
  • Loader-aware code and supported references
  • Validation and controlled content builds
  • Exact Addressable scene runtime verification

Not claimed

  • Project-wide address rename migrations
  • Group rename, deletion, or native bulk transactions
  • CDN upload or remote deployment configuration
  • Bundle performance analysis
  • Automatic build-target switching
05 / START WITH A REAL TASK

Three prompts. Three control levels.

Start read-only, approve a bounded change, or verify an exact scene that is already configured.

ASKRead-only

“Inspect our Addressables groups, profiles, scenes, and duplicate runtime addresses. Do not change the project.”

PLANApprove steps

“Add @MainMenu.unity with exact address scenes/main-menu, validate the setup, and show me the plan before changing anything.”

AGENTExecute

“Load the Addressable scene with exact key scenes/main-menu at runtime and verify that it becomes active.”

AVAILABLE SINCE XORIN 2.1.0

Inspect first. Change deliberately. Verify the exact result.

Bring Xorin into the Unity project where your Addressables work already lives.

Start free trial Read the docs

7 days · $40 in credits · No card required