Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Question about Update Restriction : Cannot Change Post Release

Discussion in 'Addressables' started by seraphki, Mar 10, 2020.

Thread Status:
Not open for further replies.

  1. seraphki

    seraphki

    Joined:
    Jul 20, 2016
    Posts:
    26
    I have a question about setting groups to 'Cannot Change Post Release' for their Update Restriction.

    Is this flag only used if you use the 'update previous build' option when building asset bundles? If you use the 'new build' tool, does this flag has no effect?

    Just trying to figure out what all this flag does. I've seen the documentation talking about how updating static bundles works (https://docs.unity3d.com/Packages/c...manual/AddressableAssetsDevelopmentCycle.html) but I'm a bit more curious about what effect it has if you don't use the the update tools.
     
    seraphki, Mar 10, 2020
    #1

  2. seraphki

    seraphki

    Joined:
    Jul 20, 2016
    Posts:
    26
    Bump
     
    seraphki, Mar 12, 2020
    #2

  3. davidla_unity

    davidla_unity

    Unity Technologies

    Joined:
    Nov 17, 2016
    Posts:
    736
    Correct. If you just do a new build every time it shouldn't matter either way. Static Content is meant for data that you want to make Addressable but also want to ship with your actual player (game) build. That said, keep in mind, if you're not setup to take remote catalogs (and so are saying, in most cases but not all, you'll likely have updated content in the future) and then deploy your game build with only local static bundles then you'll have to do an entire re-deploy of your game for any changes to take effect.

    Not saying any of that is relevant to your situation, just giving a little context on some of its intend use.
     
    davidla_unity, Mar 16, 2020
    #3

  4. phobos2077

    phobos2077

    Joined:
    Feb 10, 2018
    Posts:
    350
    @DavidUnity3d, could you clarify something?
    Is it possible to first have a particular Asset Group that is bundled via StreamingAssets and is marked as "Can Change Post Release", build the player and release it (with remote catalog). THEN, decide to update some of the assets in that group, change the group to "Cannot Change...", build the content for update and expect the previously released Player to download the bundles with updated static content and load it properly? Or the bundled asset catalog should already "know" that particular assets are "updateable"?

    I also find the naming of these "content update restrictions" weird. "Can Change..." really means "can't change if local, can change if remote", while "Cannot Change" means "can change if local, can change if remote". Very misleading or I'm missing something here...

    PS: your documentation still mentions "StaticContent" although this was renamed. Probably the old name of the flag was easier to understand.
     
    Last edited: Apr 8, 2020
    phobos2077, Apr 8, 2020
    #4
Thread Status:
Not open for further replies.