Version 3.1.x

This is the release notes for the The Unity SDK version 3.1.x series

Unity SDK 3.1.5

Fixed

• [Unity] Fixed an IndexOutOfRangeException occurring when using the Content Editor Window.
• [Unity] Fixed an issue where button to create a new snapshot was not displayed when no snapshots existed.

Unity SDK 3.1.4

Fixed

• [Unity] Fixed an issue where content drawer was not including subtype contents

Unity SDK 3.1.3

Fixed

• [Unity] Fixed an issue where renaming a content item in a virtual scroll view would fail.
• [Unity] Fixed an issue where searching for items of a content subtype was not being found.
• [Unity] Fixed an issue where updates to content did not trigger a repaint in the Content Editor.

Unity SDK 3.1.2

Fixed

• [Unity] Unity performance issue from calling some CLI commands in a short period of time

Changed

• [Unity] Bumped CLI Version to 5.4.2

Unity SDK 3.1.1

Changed

• [Unity] Bumped CLI Version to 5.4.1

Unity SDK 3.1.0

Added

• [Unity] Support to CLI Snapshot management on Content editor.
  • Snapshots capture the entire content state of a realm as a single JSON file, making them suitable for Git.
  • Automatic snapshots can be written to .beamable/local/ (default, gitignored) or .beamable/shared/ (not gitignored).
  • Configure snapshot destination in Project Settings → Beamable → Content → On Publish Auto Snapshot Type (None / Local Only / Shared Only / Both).
  • To track content in Git, set the snapshot type to Shared Only or Both and commit .beamable/shared/.

Fixed

• [Unity] StatsService does not throw NullReferenceException on request recovery.

Changed

• [Unity] Updated Microservices configuration Federation list to a view-mode only. Now federation are listed based on the OpenApi specification generated from the Microservices. So no need to previously add Federation Id to a Federation Interface on Unity.

Upgrading from SDK 2.x

When upgrading from 2.x, in addition to the standard migration, you may want to consider the following Git changes:

• Stop committing Assets/Beamable/Resources/content/ to Git — this folder is no longer the source of truth for content.
• Content is now stored as JSON files under .beamable/:
  • .beamable/content/<realm>/ — most recently synchronized remote content.
  • .beamable/local/content/<realm>/ — local working copy, may contain unpublished changes.
• .beamable/local/ is gitignored by default (see .beamable/.gitignore). Raw content JSON files change on every publish due to referenceManifestId updates, making them too noisy for direct Git tracking. Use Snapshots instead.
• Realm-to-realm promotion: publish from Unity to your Dev realm, then promote to Staging and Production via the Beamable web portal.