See how Addressables changes may affect patch size before release. Compare builds, trace changed bundles, set budgets, and export clear reports.📦 Know the patch costA small asset edit can make a large patch. Addressables Patch Impact shows what changed, which bundles are touched, and how much players may need to download.🔎 Compare real releasesSave a release baseline, then compare the next build. The tool finds Addressables build data and brings the key facts into one clear view.⚡ Estimate before a full buildRun a fast prediction from changed source assets. Each result includes a confidence level, so you can see what is known and what still needs a measured build.🎯 Set patch budgetsAdd limits for download size, changed bundles, or other release rules. Try simple what-if checks to see where a better group or bundle plan may help.📄 Share the answerExport JSON, Markdown, or HTML reports for review and CI. The tool reads your Addressables data. It does not build content or change Addressables settings for you.- Version: 1.0.0- Unity: 2022.3 or newer- Tested with Unity 6.3 LTS- Requires Addressables; package dependency targets com.unity.addressables 1.28.2- Editor-only analysis tool- Discovers supported Addressables build artifacts- Saves and loads release baselines- Compares release-to-release bundle and asset data- Shows changed, added, and removed content- Maps source changes to affected bundles when evidence is available- Fast pre-build prediction with confidence labels- Measured reconciliation compares a prediction with later build data- Clean-cache view helps show first-download cost- Budget checks can flag patch size and changed-bundle limits- What-if tools help test grouping ideas without changing project settings- Causal navigation helps trace a result from asset change to bundle impact- Deterministic JSON, Markdown, and HTML reports- Suitable for local review and CI workflows- Includes sample release baselines and example data- Read-only by design: it does not run Addressables builds- Does not edit Addressables groups, schemas, profiles, settings, or content state- Predictions are estimates; use a measured build for final release numbersAI was used for bug detection and increasing code quality. As well as logo and marketing generation. Core code is human generated.
