A game designer may need to change gameplay balance without waiting for a new application build. Keep balance data in a separate file, upload a revised version to a server, and let the game download it when it runs. This works for data changes; an asset change that requires new code still needs a new build. section 9.7 section 7.2.4
Choose the update path by identifying what actually changes:
- For an entire prefab, consider Unity Addressables or custom asset-bundle downloading. section 7.2.4
- For an image, consider a content delivery network; for text, consider downloading a new string from a database. section 7.2.4
- If the asset rarely changes, question whether live updating is worth the added complexity. section 7.2.4
Updating game balance
Distribute a new balance file when designers change gameplay values. Load balance from a single source so a player does not return to an older local version after downloading a newer one. Retain past versions separately: reproducing a reported bug may require the balance the player had at the time. Separate files also allow A/B testing by distributing different values to two groups and comparing their analytics. section 9.7
Live updates are hard for QA to test. Decide first whether an update is needed, then choose the smallest data-delivery solution that fits; adding Addressables by default can create unnecessary complications. section 7.2.4
