In August 2003, Beamable released SDK versions 1.17.1, 1.17.2, 1.17.3, and 1.18.0. Here are the highlights from those releases.
We’ve spent a lot of effort this month focusing on making the CLI tooling easier to use. In the latest versions of Beamable, the CLI has several usability improvements.
Throughout the latest patches and releases of Beamable, Standalone Microservices have seen a few critical improvements.
There are a handful of other bug fixes and workflow improvements for Microservices in general.
Beamable 1.18.0 also includes a new IUsageAPI service accessed via Dependency Injection. The IUsageAPI exposes CPU and Memory usage statistics and a unique identifier for each service instance.
In Beamable 1.18.0, the BeamContext game object is the last thing to be disposed of when a Beam Context is being shutdown. Previously, there was a large swatch of bugs that would appear when exiting playmode, or using the .Stop() function on a Beam Context. The IBeamableDisposableOrder interface allows any registered Beamable dependency to declare a custom disposal priority. By default, the Beam Context uses a disposal priority to ensure it is handled last. This means that as other components of the Beamable SDK are shutting down, they have access to critical services available on the Beam Context.
For the official changelogs, please visit https://beamable.github.io/changes