Same addressables_content_state.bin across branches?

Can somebody help verify my assumptions here?

We want different teams working in their own branches to have their own addressable content. Each team has their own branch, each branch can have its own S3 bucket for content, its own config environment, and its own builds. Stakeholders can play a team’s build on device.

My question is whether we can use the same addressables_content_state.bin across branches for each platform.

My assumptions:

  • It’s possible to work forever with the same addressables_content_state.bin.
  • It’s okay to switch catalogs and data with the same same addressables_content_state.bin
  • One can think of addressables_content_state.bin as basically a hash that just identifies compatible asset catalogs.

Idk what else it could be!
Cheers

Arg. The addressables_content_state.bin is locked to download location.

How do I save a different addressables_content_state.bin per addressables profile?

I have multiple folders each with a different bin file in them and select the bin according to the profile I’m using. Also seems to push and pull from git to be used on other pc’s fine

1 Like

Thanks sniffle.

I ended up solving is using this: Transforming resource URLs | Addressables | 1.19.19

I just modify the runtime path to point to the correct S3 bucket. Seems to work.

I also set a “Player Version Override” but I don’t know if that was required. It seems to tell Unity to use the same filenames for each build.