Hey @unity_bill & @davidla_unity , After searching the forums and a few other sources I have been unable to find good information on this, so I’d like to know your thoughts on a few things related to Addressables, mainly in regards to multiple people working on the same project with them, with exclusive locks turned on for assets.
1.) What are the best practices for sharing workload?
2.) Are addressables assets/manifests easily mergeable if two+ people make changes?
3.) If we were to lock files based on changes, I know some of the higher level files are also modified and would therefore also be locked, what are the best practices for working under these conditions while blocking each other as little as possible?
Thanks in advance! Looking forward to your response(s)
Since we have no idea and devs don’t answer most questions here, my recommendation is to minimize changes to the Addressable groups and data to avoid those problems.
When creating Addressable groups, just drag whole folders into the addressable window instead of putting assets in there one by one. This way the Addressable data doesn’t need to change often.
This will also let you easily notice when bugs like this happen:
Hey, thanks for the responses guys, I’d still really love to see if @unity_bill or @davidla_unity (or any other Unity people of course) have any answers/thoughts on the matter! I realize it might take a little while for them to respond but you have to understand that they have to work on the system(s) too and can’t just reply to the forums all day
