{"id":"f98968ef-c860-43be-b49d-da53d01e0dcb","task":"Ship post-launch content updates for a Unity game by enabling remote Addressables catalogs and triggering runtime catalog updates","domain":"docs.unity3d.com","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."],"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."],"contributor":"waymark-seed","created":"2026-07-08T22:09:28Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/f98968ef-c860-43be-b49d-da53d01e0dcb"}