DEV Community

Juego Studios
Juego Studios

Posted on

Shipping a Unity Content Update Without a Full Store Release: An Addressables Checklist

Pushing new levels, cosmetics or a seasonal event to a live Unity game without waiting on a full App Store or Google Play review is one of the main reasons teams adopt Addressables. It is also where a lot of live games quietly break: a catalogue that points at a bundle the old client cannot load, a shader stripped from the player build, or a download that stalls on a train with patchy signal. This is the checklist we would run before any remote content update goes out.

1. Decide what can and cannot change remotely

Write this down before the first update, not during it.

  • Safe to ship remotely: textures, meshes, audio, prefabs and ScriptableObject data that only use code already in the shipped client.
  • Not safe: anything that needs new C# code, a new package, or a MonoBehaviour type the old build does not contain. Those need a store release.
  • Keep a short list of "remote-safe" groups in the repo so designers know what they can schedule without an engineer.

2. Keep the content state file under version control

The addressables_content_state.bin produced by the release build is what Update a Previous Build compares against. Lose it and you cannot make a proper content update for that client version.

  • Commit it (or archive it with the build artefacts) for every build that reaches players.
  • Tag it with the app version and build number so nobody updates against the wrong baseline.

3. Group assets by how often they change

Bundle layout decides how much players download.

  • Put rarely changing core assets in "Cannot Change Post Release" groups.
  • Put event and seasonal content in its own groups, packed separately, so a new event does not force a re-download of the whole UI atlas.
  • Watch for duplicated dependencies with the Analyze tool; a shared material pulled into five bundles is five downloads.

4. Check shaders and stripping

A frequent cause of pink materials after an update is a shader variant that the player build stripped because nothing in the original build used it.

  • Include any shaders that remote content may use in the build, or keep them in a shared bundle that ships with the app.
  • Test remote content against the actual release build, not an editor play session.

5. Plan for poor connections

Players open the game on the Tube, on hotel Wi-Fi and with mobile data turned off for big downloads.

  • Call GetDownloadSizeAsync first and show the size before downloading anything large.
  • Let the player keep playing existing content if the download fails, and retry later rather than blocking the main menu.
  • Set sensible timeouts and test with a network link conditioner at 3G-like speeds.

6. Version the catalogue and keep a rollback

  • Host each catalogue under a path that includes the client version, so an older build never picks up content built for a newer one.
  • Keep the previous catalogue and bundles on the CDN until the new one has been live for a while; rolling back should be a pointer change, not a rebuild.
  • Mind CDN caching: give bundles unique, hashed names so a stale cached copy cannot be served.

7. Run a short release rehearsal

Before the update goes live:

  1. Install the current store build on a clean device.
  2. Point it at a staging catalogue with the new content.
  3. Check download size, first load, memory on a low-end device, and that nothing references a missing type.
  4. Repeat on the oldest client version you still support.

8. Write the update down like a release

A one-page note per content update (groups changed, catalogue version, CDN path, who approved it, how to roll back) saves a lot of guesswork when something goes wrong on a Saturday evening.


If the same game is heading to console later, our pre-cert porting checklist covers what to audit before certification.

I work at Juego Studios, a game development studio. If you would rather hand this pipeline work to a partner, here is how our Unity game development services team approaches live projects.

Top comments (0)