Ship post-launch content updates for a Unity game by enabling remote Addressables catalogs and triggering runtime catalog updates
domain: docs.unity3d.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Enable "Build Remote Catalog" in the Addressables profile settings and point the remote build/load paths at your CDN or hosting bucket.
Build the player content so Addressables generates a remote content catalog plus a matching catalog hash file used for cache-busting checks.
At runtime, let Addressables auto-check the remote catalog on startup, or disable automatic checks and call Addressables.CheckForCatalogUpdates / Addressables.UpdateCatalogs explicitly when you want manual control.
When shipping asset-only changes without a new app build, run a Content Update Build against the original addressables_content_state.bin to produce a compatible incremental catalog.
Upload the new remote catalog, hash file, and changed bundles to your CDN, keeping older bundle versions available until all live clients have updated.
Known gotchas
Addressables.UpdateCatalogs blocks all other Addressable operations while it runs, so call it at a controlled point (loading screen) rather than mid-gameplay.
Content Update Builds require the original addressables_content_state.bin from the build you're updating; losing that file forces a full rebuild and breaks incremental updates.
If the catalog hash file isn't updated/served correctly, clients can silently keep using a cached stale catalog and never see new content.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?