AssetStoreまとめ 割引情報 beta

- アセットの価格推移をリアルタイムにチェック -

Find Unity project risks before they become release problems. ORDO checks import policy for textures, models, and audio, plus missing scripts and broken references in prefabs and scenes.The problems you find at the worst possible timeA 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 worksScan. ORDO evaluates a defined set of readiness conditions across your project:Textures — mipmaps, filter mode, anisotropyModels — Read/Write, global scale, mesh compression, rig typeAudio — load type, compression format, force-to-mono, ambisonic, import qualityPrefabs — missing MonoBehaviour scripts, and serialized references whose target is goneScenes — 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 your own content in order, and leaves everything else aloneAlongside 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 payoffCatch 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.ScopeORDO 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.See what changed. ORDO remembers your last completed scan and shows how many findings are new, resolved, or unchanged since then, so after a merge or an asset drop you know immediately whether the project got better or worse.Readiness scan — deterministic checks for texture mipmaps / filter mode / anisotropy; model Read/Write / global scale / mesh compression / rig type; audio load type / compression format / force-to-mono / ambisonic / import quality; missing MonoBehaviour scripts in prefabs and scenes; and serialized object references whose target no longer exists, in prefabs and scenes. Structured findings with stable rule identity, severity, and expected/actual evidence; evaluation errors reported separately.Scene Integrity — scene findings (missing scripts, broken references) are grouped separately and run in the default scan. ORDO opens each scene safely, restores your exact scene setup afterward, and reports partial coverage (Play mode, unsaved changes) rather than skipping silently.Project Health history — each fully completed scan is kept as a local snapshot (Library/ORDO, never committed) and the next scan reports new / resolved / unchanged findings against it. Incomplete scans never replace the baseline.Confirmation-gated remediation — import-policy findings offer a one-click fix that previews the change, mutates only the governed importer field, reimports, and requires a rescan to verify. Stale fixes (project or policy changed since the finding) are refused. Missing-script and missing-reference findings are guided, not automated, ORDO never removes a component or clears a reference.Shareable policy file — export/import the folder rules and import policies as a committable ProjectSettings/ORDO.policy.json (diff-friendly, no GUIDs). Import shows a plain-language diff and applies nothing without confirmation. A drift check on open flags a local setup that no longer matches the committed file.Command-line scan — -executeMethod Faktory.ordo.OrdoCli.Scan runs the scan headless, writes the same versioned JSON report, and exits non-zero on Blocking findings (-ordoReport, -ordoFailOn blocking|warning|none). Read-only.Import policy enforcement — 33 built-in import policies for textures, models, and audio, attached per folder rule and applied on import, only inside the template's folders. Never silent: every setting a policy changes on import is recorded locally and announced once per import (a notice in the ORDO window, or one Console line), with the full list on Overview. "Apply Import Policies Now" brings an existing project into line in one pass. A searchable editor with plain-language names; mutually exclusive choices replace each other instead of piling up.Opt-in organization — ORDO moves a file only when it is loose in Assets, inside the template's folders, or inside a top-level folder you ticked in Settings. Every other folder is left in place, so imported and third-party assets keep their layout. The folder list shows ORDO's guess for each folder (Asset Store package, has its own assembly definition, imported package, or your content) to make the choice quick.Scan proposes, you approve — files already in the project are never moved by a scan. They appear in the Pending Changes panel with exact source and destination, pre-flight checks, a by-folder summary with "Keep Folder Here", and verification reported separately from the move. With Auto Organize on, only files that are new to the project, and files you move yourself, are filed automatically through the asset database, so references stay intact. New scripts are filed once they compile; this can be turned off.Undo — every move is journaled locally (Library/ORDO, never committed). "Undo" on Overview and in Pending Changes puts the files from the most recent run back where they were.Layout-sensitive assets are protected — assembly definitions never move and scripts never leave their assembly; a packaged asset with its own assembly definition is left intact; shader include files and the shaders that depend on them stay together; nothing is moved out of Resources, StreamingAssets, Editor, Gizmos, or Plugins; sprites and plain textures are routed to folders that expect them.Folder templates — define where every asset type belongs, by extension, filename pattern, or priority. Ships with structures for 2D, 3D, mobile, VR, AR, console, and WebGL; edit them or build your own. Templates are plain asset files, so committing one keeps a whole team's projects on the same layout and import rules.Keep Here exceptions — exempt a single asset (GUID-backed, survives renames), a file type, or a whole folder from reorganization, without turning off the readiness checks.Version-control aware — Overview warns when it cannot detect version control, before ORDO moves or rewrites anything. One click adds Unity's recommended .gitignore to the project root. ORDO keeps its own generated settings out of your repo, and leaves Unity's tutorial and Readme scaffolding untouched.One window — Tools > ORDO > Open ORDO: Overview, Findings, Pending Changes, and Settings as tabs in a single workspace. Overview leads with the recommended next step and the most important findings. The installed version is shown in the tab bar. Light/dark theme-aware.Editor-only — runs entirely in the Unity Editor. Zero footprint in game builds.Compatibility — Unity 2022.3 LTS and newer.Third-party content — includes Space Grotesk, IBM Plex Sans, and IBM Plex Mono (SIL Open Font License 1.1), listed in Third-Party Notices.txt.Documentation — full manual (HTML + PDF) included in the package. Online: https://courses.faktorystudios.com/ordo-documentationAssisted in code clean-up and resolving some bugs as well as helping draft documentation.