Unity
ORDO - Project Automation Organizer
$19.99
Rated 0.0/5 from 1 ratings on Unity.
Price history
Recorded standalone sale prices and the latest available store price, in USD. Historical dots use the sale start date and its recorded offer price. Prices can change during a sale; this is not a daily price log. Bundle prices and upcoming offers are excluded. History covers up to the 100 most recent recorded offers.
Lowest recorded standalone price in this history: $19.99. The latest store price is $19.99, matching the lowest recorded price shown here.
View 3 recorded prices
| Sale start / price check | Price | Observation |
|---|---|---|
| $19.99 | Latest store price | |
| $19.99 | Unity Permanent Decrease 2026-09-25 2026-10-02 | |
| $24.99 | Unity Permanent Decrease 2026-09-05 2026-09-12 |
Sale and bundle history
The 2 most recent recorded offers including this asset. Past offers may no longer be available. Bundle prices cover a package, not this asset alone.
About ORDO - Project Automation Organizer
- Tools, Systems & Learning > Development Tools & Automation
The problems you find at the worst possible time
A model ships with Read/Write left on. Audio that should have been mono doubled your bank size. A prefab lost a script three merges ago and nobody noticed. Textures drifted off the filter and compression settings the project agreed on. None of it breaks the Editor, it just quietly costs you build size, memory, and time, and you find it the week you are trying to ship.
ORDO is an Editor tool that checks for these conditions on demand, tells you exactly what and where, and verifies the fix.
How it works
Scan. ORDO evaluates a defined set of readiness conditions across your project:
1. Textures — mipmaps, filter mode, anisotropy
2. Models — Read/Write, global scale, mesh compression, rig type
3. Audio — load type, compression format, force-to-mono, ambisonic, import quality
4. Prefabs — missing MonoBehaviour scripts, and serialized references whose target is gone
5. Scenes — missing scripts on scene objects, and broken serialized references (grouped as Scene Integrity)
Understand. Each finding has a severity (Blocking / Warning / Advisory), the rule it violates, and the expected-versus-actual evidence behind it. Evaluation errors are shown separately from findings, so a scan that could not check something never looks like a clean result.
Fix, with your confirmation. Import-policy findings have a one-click fix that shows you what it will change, changes only that field, reimports, and re-checks on the next scan. If the project or your policy changed since the finding was raised, ORDO refuses the stale fix. Missing scripts and broken references are guided, not auto-removed, ORDO never deletes a component or clears a reference for you.
Verify. Nothing is marked resolved until a rescan confirms it. A clean scan means the checks ORDO runs passed, it is not a claim about the whole project.
Keeps the project in order, automatically
Alongside the readiness checks, ORDO enforces the structure and import settings you decide on once:
- Import policies — 33 built-in policies for textures, models, and audio, attached per folder rule and applied automatically as assets are imported. One command brings an existing project into line.
- Folder organization — new and moved assets are filed into their template folder. Every move goes through Unity's asset database, so references, prefab links, and scene assignments stay intact. Turn it off to approve each move first in the Pending Changes panel.
- One policy for the team — export your folder rules and import policies to a single ProjectSettings/ORDO.policy.json, commit it, and every developer scans the same way. ORDO tells you when your local setup has drifted from the committed file. Fully offline, no account.
Runs in CI
-executeMethod Faktory.ordo.OrdoCli.Scan runs a read-only readiness scan in batch mode with no Editor window, writes a structured JSON report, and exits non-zero when there is a Blocking finding, enough to fail a build. It never moves assets or changes importers.
What's the payoff
Catch the import-setting and integrity problems that cost build size, memory, and debugging time while they are cheap to fix, not during release crunch. And a project that stays organized and on-policy stays fast to work in for as long as you are in it.
Scope
ORDO checks the coverage it shows you: texture, model, and audio import policy; missing scripts and broken serialized references in prefabs and scenes. A clean scan means those checks passed. It does not certify whole-project readiness: no build-settings or Addressables validation, no required-field or required-component checks, no general scene validation beyond the integrity checks above.
A model ships with Read/Write left on. Audio that should have been mono doubled your bank size. A prefab lost a script three merges ago and nobody noticed. Textures drifted off the filter and compression settings the project agreed on. None of it breaks the Editor, it just quietly costs you build size, memory, and time, and you find it the week you are trying to ship.
ORDO is an Editor tool that checks for these conditions on demand, tells you exactly what and where, and verifies the fix.
How it works
Scan. ORDO evaluates a defined set of readiness conditions across your project:
1. Textures — mipmaps, filter mode, anisotropy
2. Models — Read/Write, global scale, mesh compression, rig type
3. Audio — load type, compression format, force-to-mono, ambisonic, import quality
4. Prefabs — missing MonoBehaviour scripts, and serialized references whose target is gone
5. Scenes — missing scripts on scene objects, and broken serialized references (grouped as Scene Integrity)
Understand. Each finding has a severity (Blocking / Warning / Advisory), the rule it violates, and the expected-versus-actual evidence behind it. Evaluation errors are shown separately from findings, so a scan that could not check something never looks like a clean result.
Fix, with your confirmation. Import-policy findings have a one-click fix that shows you what it will change, changes only that field, reimports, and re-checks on the next scan. If the project or your policy changed since the finding was raised, ORDO refuses the stale fix. Missing scripts and broken references are guided, not auto-removed, ORDO never deletes a component or clears a reference for you.
Verify. Nothing is marked resolved until a rescan confirms it. A clean scan means the checks ORDO runs passed, it is not a claim about the whole project.
Keeps the project in order, automatically
Alongside the readiness checks, ORDO enforces the structure and import settings you decide on once:
- Import policies — 33 built-in policies for textures, models, and audio, attached per folder rule and applied automatically as assets are imported. One command brings an existing project into line.
- Folder organization — new and moved assets are filed into their template folder. Every move goes through Unity's asset database, so references, prefab links, and scene assignments stay intact. Turn it off to approve each move first in the Pending Changes panel.
- One policy for the team — export your folder rules and import policies to a single ProjectSettings/ORDO.policy.json, commit it, and every developer scans the same way. ORDO tells you when your local setup has drifted from the committed file. Fully offline, no account.
Runs in CI
-executeMethod Faktory.ordo.OrdoCli.Scan runs a read-only readiness scan in batch mode with no Editor window, writes a structured JSON report, and exits non-zero when there is a Blocking finding, enough to fail a build. It never moves assets or changes importers.
What's the payoff
Catch the import-setting and integrity problems that cost build size, memory, and debugging time while they are cheap to fix, not during release crunch. And a project that stays organized and on-policy stays fast to work in for as long as you are in it.
Scope
ORDO checks the coverage it shows you: texture, model, and audio import policy; missing scripts and broken serialized references in prefabs and scenes. A clean scan means those checks passed. It does not certify whole-project readiness: no build-settings or Addressables validation, no required-field or required-component checks, no general scene validation beyond the integrity checks above.