Force local bundles to Cannot Change Post Release

Hello ,

I would like to know if is there any reason not to enforce addressables groups targetting a

LocalLoadPath

to also have the update restriction

Cannot Change Post Release

. Or at least log a warning on the console if there are groups missing this condition.

I've faced the situation of having to publish a new, patched game build because the previous one had a local group which was not marked as static(many people in charge of messing with addressables config, and honestly given the wide arrange of settings to control it's easy to miss this kind of thing until it's too late).

When doing the content update procedures, those assets would change(sometimes just because of a non deterministic bundles build) but obviously won't get moved to a

Content Update

remote group.
The new catalog has now updated local paths for asset bundles that are not in the client device and won't be ever updated, and thus when the client downloads the catalog it will fail trying to load those.

So again, do you know of any scenario that prevents enforcing this restriction ?

Thank you

 

Please, can you shed some light on this ?

Thanks !