Highlights

• New feature: Localizations are now first-class citizens in the LiveOps Dashboard. You can now view localization builds and push them out as OTA updates to clients from the dashboard.

  • 

• New feature: Environment Configs are a new way to define your client-side environment-specific configurations as a JSON file with full Unity editor support, better CI support and more. See Release 25 Environment Configs Migration Guide for more information.

  • 

• Major improvement: Game Config Parsing from spreadsheets now supports nested members, vertical collections, and combinations of the two. With these, you can directly parse things like arrays of classes without needing to use source transforms. See Working with Game Config Data for more information.

• Major improvement: Game Config Building is now enabled by default in the LiveOps Dashboard. You can see the history of config builds and the results of config validation straight from the dashboard and there's a new form for customizing how the config build is triggered.

  • 

• Major improvement: Game Config Source Data Fetching Game config building now natively supports multiple data sources as well as adding your own types of data sources. This can be a useful tool for optimizing your config workflows!

INFO

Note: ✨ This release has seen a lot of work in the game configs and localizations pipeline and we are not done yet! We will continue iterating on and polishing these new features in the next release ✨

Breaking Changes

• This release requires a synchronized upgrade of the client and the server due to backward-incompatible changes in the networking protocol.
  • Action required: Bump your game's MetaplayCoreOptions.supportedLogicVersions to force a synchronized update of your game client and server.
• The minimum Unity version is bumped to 2021.3 LTS in this release. It is the latest LTS version that is still supported by Unity itself.
  • Action required: Upgrade your project to Unity 2021.3 or later before upgrading Metaplay.
• The game config parser has been refactored significantly to better support new features which requires some changes when using it.
  • Action required: Follow the instructions in the Release 25 Game Config Migration Guide.
• As a part of migrating from bootstrap-vue to MetaUiNext we have removed the following dashboard components:
  • b-tooltip - Use MTooltip instead.
  • b-badge - Use MBadge instead.
• Game Server database schema has been updated to support the new features:
  • Note This release contains EFCore migrations that will be applied to the database on server start. The process is automatic but especially with large databases it's worth testing before going into production!
  • Action required To generate the necessary migrations yourself, run dotnet ef migrations add MetaplayRelease25 in your Backend/Server folder and commit the updated files in 'Migrations/'.

INFO

Note: If you have a service contract signed with Metaplay, the breaking changes outside the list above have been fixed already in the SDK upgrade pull request of your project. Otherwise, please see CHANGELOG.md for a full list of changes, along with the HelloWorld and Idler samples for references on how to apply the changes.

Version Compatibility

We recommend upgrading to the latest versions of the infrastructure and game server Helm chart:

• For infrastructure, terraform module infra-modules v0.2.10.
  • Action recommended: Upgrade your self-hosted infrastructure to use the latest version.
• For deployments, Helm chart metaplay-gameserver v0.5.0.
  • Action recommended: Upgrade your deployments (in Helm values or CI job parameters) to use the latest version.

The minimum required versions are infra-modules v0.2.2 and metaplay-gameserver v0.4.4.

Notable LiveOps Dashboard Changes

• Individual player targeting in the notification and broadcast forms received a UX pass and is now easier to use.
  • 
• Event log cards (for example the player analytics event log) can now be filtered based on the newly added keywords in addition to the existing event types and general search. The underlying MetaEventStreamCard component has new properties to both set and freeze the filters to easily create cards that show a specific subset of all the events. The filters are also OR instead of AND to make it easier to create very narrow filters.
  • 
• The new MErrorCallout component provides a consistent and user-friendly way to report and share both technical and non-technical errors throughout the LiveOps dashboard.
  • 
• You can now customize the header color of the dashboard for each of your environments (development, staging, production) to make it easier to tell them apart. Check out the updated Configuring the LiveOps Dashboard page for more details.
  • 

Notable Under-the-Hood Changes

• The MetaUiNext component library has expanded with lots of new components that are currently in internal testing, and the following components have graduated to stable:
  • MBadge - A colored box/pill to highlight information. Replaces b-badge.
  • MTooltip - A utility to show tooltips. Replaces b-tooltip.
  • MErrorCallout - A specialized callout to display technical errors.
• The add<listName>OverviewListItem and the addUiComponent integration APIs have been extended to support the ability to hide specific list-items and/or UI components on your dashboard based on user permissions. See Customizing the LiveOps Dashboard Frontend for more details.
• The LiveOps Dashboard subscriptions API has been streamlined and the old API has been deprecated. There is now only a single useSubscription function instead of the previous useStaticSubscription/useDynamicSubscription pair. Check the Working with Subscriptions documentation for how to migrate your code.
• You can now use Tuple, ValueTuple, DateTimeOffset, Version, Guid, TimeSpan, ReadOnlyCollection<T>, and ReadOnlyDictionary<Key, Value> in MetaSerialized types.
• MetaSerialization can now use a constructor to deserialize. Just declare a constructor with matching parameter names and types to the MetaMembers and add the MetaDeserializationConstructor attribute.
• MetaSerialization now provides better hints to the origin of serialization errors.
• Converting fixed-point numbers (F32, F64, and the vector variants) ToString() and Parse() now have robust implementations. The conversion from fixed-point to string and back is guaranteed to produce the original fixed-point value. The methods are also deterministic.
• Reading files with FileUtil methods uses sharing options that makes it work even if the file is opened in an editor. This is useful for example if importing game configs from .csv files while they are open in Excel for editing.
• It is now possible to have multiple game config libraries with the same item type, or different item types inheriting from the same base class which implements IGameConfigData<>. Reference resolving will look for the item in each library whose item type is compatible with the reference.
• The C# project and solution files no longer explicitly specify the x64 or ARM64 platforms but use the Any CPU that works well with either target.
• The server no longer uses the config build timestamp for figuring out if the current game config should be auto-updated to the builtin config found on filesystem. Config auto-update on server boot now always happens if the builtin gameconfig hasn't been seen in the environment before. This fixes cases where auto-update did not take place due to the live gameconfig having a newer timestamp than the config associated with a server update.
• Game config data now properly supports the Hidden and ServerOnly MetaMember flags for stripping data from the client visible config. The "full protocol server hash" does not include these items so that they don't cause spurious hash mismatches between the client and the server.
• JSON Serialization in the Admin API now ignores properties that throw exceptions, these properties are excluded from the output of the endpoint. Exceptions are deduplicated (by message, to prevent spam) and are still logged to the server output after serialization is complete.
  • Action recommended: We still recommend fixing any such errors, as it can lead to degraded performance and error fatigue.
• The Game Config base classes SharedGameConfigBase and ServerGameConfigBase no longer contain entries for the SDK side config libraries (Languages, InAppProducts, PlayerSegments, Offers, OfferGroups, PlayerExperiments) and these entries have been made optional. This removes the need of declaring game config builds (and associated sheets) for features that are not being used.
• To reduce unnecessary copying of ConfigArchives and ConfigArchiveEntrys, we've refactored ConfigArchive to be read-only and it is now decompressed on load.

Change Log

Breaking

• SDK: Minimum required Unity version is now 2021.3.
• SDK: ExportEntityHandler and ImportEntityHandler are Obsolete.
  • Action Required: All classes inheriting from ImportEntityHandler should inherit SimpleImportEntityHandler instead.
• SDK: MultiplayerEntityClientContext constructor now takes ClientMultiplayerEntityContextInitArgs.
  • Action Required: When a context is generated, create init args with MultiplayerEntityClientBase.DefaultInitArgs and pass it into the constructor.
• SDK: The fixed-point F32/F64 methods ToString() and Parse() have been rewritten to be deterministic and faster, but the outputs are not identical to the earlier releases. This applies parsing fixed-point values during game config building as well.
  • Action Required: Check that the tiny differences in the game config build outputs don't cause any meaningful changes. If you need the behavior of the parser, talk to us and we'll help you restore it.
  • Action Required: If you're converting fixed-points to/from strings, you must perform a full synchronized update of the client and the server to avoid desyncs.
  • Action Required: If you're converting fixed-points to JSON, make sure the changed results (from the updated rounding rules) do not affect any system consuming the said JSON documents.
• SDK: The game config base classes SharedGameConfigBase and ServerGameConfigBase have been refactored to make SDK side config libraries (Languages, InAppProducts, PlayerSegments, Offers, OfferGroups, PlayerExperiments) optional and to not require specifying custom info classes for the SDK libraries via template parameters. The old base classes have been preserved with Legacy prefix to aid in the migration.
  • Action Required: If using any of the SDK side features requiring config libraries, introduce the associated game config entries into your SharedGameConfigBase and ServerGameConfigBase derived classes and tag the entries with GameConfigEntryAttribute. Alternatively you can switch the base class to the Legacy variants to retain the old behavior of having the entries declared on the SDK side.
• SDK: PersistedParticipantDivisionAssociation has a new field LeagueStateRevision to help restore the league's state in case of shutdowns and crashes.
  • Action Required: If the leagues feature is enabled, this change requires a new database migration.
• SDK: ConfigArchive has been refactored to be read-only to reduce unnecessary copies of the data, ConfigArchiveEntrys are now decompressed on load.
  • Action Required: Replace calls to ConfigArchiveEntry.Uncompress() and ConfigArchiveEntry.RawBytes with ConfigArchive.GetEntryBytes() or ConfigArchiveEntry.Bytes.
• SDK: Remove the LocalizationStorageFormat and LocalizationStorageFormat.LegacyCsv. The binary format is now always assumed.
  • Action Required: Remove any references to LocalizationStorageFormat and the legacy format from your code.
• SDK: MetaPlayerReward.Consume now takes the IRewardSource parameter. MetaPlayerReward.InvokeConsume is now sealed and exists only as a helper to call Consume with the concrete PlayerModel type instead of IPlayerModelBase.
  • Action Required: In your custom player reward classes, change your existing Consume overrides to take the IRewardSource parameter. Also, change your existing InvokeConsume overrides to be Consume overrides instead.
• SDK: Social authentication code now tolerates the case where there was a conflicting player account, but the server failed to get the conflicting player's state, for example due to a deserialization error. The social login API was updated to reflect this. Previously, the current game session would be terminated in this scenario.
  • Action Required: If you implement IMetaplayClientSocialAuthenticationDelegate in your client code: Add an implementation of OnSocialAuthenticationConflictWithFailingOtherPlayer. The minimal implementation can be empty (though logging an error is recommended), but ideally the error should be communicated to the user, with the option of contacting customer support. See the comments in IMetaplayClientSocialAuthenticationDelegate for more information.
  • Action Required: If you handle SocialAuthenticateResult directly in your client code: Member ConflictingPlayer has been renamed to ConflictingPlayerIfAvailable, and ConflictingPlayerId has been added. Unlike before, ConflictingPlayerIfAvailable can now deserialize to null even if there was a conflict. The presence of a conflict is now determined by checking if ConflictingPlayerId is available (i.e. is not EntityId.None). Therefore the new case you will need to handle is that where ConflictingPlayerIfAvailable deserializes to null yet ConflictingPlayerId is available. You should handle this case in the same way as described above for IMetaplayClientSocialAuthenticationDelegate.OnSocialAuthenticationConflictWithFailingOtherPlayer.
• SDK: ConfigParser's method TryGetParseFunc() has been replaced with TryParse().
  • Action Required: Calls to ConfigParser.TryGetParseFunc() should be changed according to the use case:
    • Calls to TryGetParseFunc() immediately followed by a call to the returned parse func should be replaced by a call to TryParse() instead.
    • Calls to TryGetParseFunc() made for the purpose of checking if a custom parse func has already been registered should be replaced with a call to HasRegisteredParseFunc().
    • Other kinds of calls to TryGetParseFunc() are unlikely to exist, but if they do then they need to be considered case by case.
• SDK: In PersistedMultiplayerEntityActorBase, TimeSpan TickUpdateInterval is replaced with TickRateSetting TickRate and has a new default behavior.
  • Action Required: If there is existing TickUpdateInterval, convert it into TickRate. See TickRateSetting constructor for details.
  • Action Required: If there was no previously defined TickUpdateInterval, the actor now by default uses the Model's tick rate when there is an ongoing Session. This may significantly increase the tick execution rate. To keep the previous tick rate, set TickRate to new TickRateSetting(TimeSpan.FromSeconds(5), TimeSpan.FromSeconds(5)).
• SDK: GameConfigBuilderServices has been removed in favor of the new Game Config build sources system. Integrations need to update to specifying the config build sources using in the GameConfigBuildParameters input parameter and configuring source fetchers with the IGameConfigSourceFetcherConfig input parameter.
  • Action Required: Refer to the Release 25 game configs migration guide to update existing build pipeline configuration.
  • Action Required: ConfigArchive.FromBytes(), ConfigArchive.GetEntryBytes(), and ConfigArchiveEntry.Bytes APIs have been updated to use Memory<byte>, please update usages.
  • Action Required: Replace ReadOnlyConfigArchive with ConfigArchive.
  • Action Required: Replace ConfigArchive.ToBytes() calls with ConfigArchiveBuildUtility.ToBytes().
  • Action Required: FolderEncoding is now a child class or ConfigArchiveBuildUtility.
  • Action Required: Replace calls to ConfigArchive.WriteToFile() with ConfigArchiveBuildUtility.WriteToFile().
  • Action Required: Replace uses of the IConfigArchive and IConfigArchiveEntry interfaces with ConfigArchive and ConfigArchiveEntry.
• SDK: Runtime option GoogleSheets:GameConfigSheetId has been removed in favor of the new Game Config build sources system. Integrations should now specify the available source spreadsheets by deriving from GameConfigBuildIntegration and overriding its GetAllAvailableBuildSources.
  • Action Required: Remove GoogleSheets:GameConfigSheetId from your runtime option yaml files. Refer to the Release 25 game configs migration guide to update existing build pipeline configuration.
• SDK: MetaplayClientOptions and MetaplaySDKConfig have been refactored and several options including ServerEndpoint are moved to the new EnvironmentConfig class.
  • Action Required: Refer to the Release 25 environment configs migration guide to start using the default environment config provider or to implement a custom IEnvironmentConfigProvider.
• Unity: Support for METAPLAY_UNITY_DEFINES override file has been removed.
  • Action Required: For overriding app target environment in CI (i.e. setting the target server it connects to), use METAPLAY_ACTIVE_ENVIRONMENT_ID environment variable, or -MetaplayActiveEnvironmentId env command line parameter.
• BotClient: StartSession doesn't need to be called and is removed.
  • Action Required: Remove call to StartSession.
• Dashboard: b-tooltip has been removed in favor the newer MTooltip component.
  • Action Required: Replace b-tooltip with MTooltip in your Vue components.
• Dashboard: b-badge has been removed in favor the newer MBadge component.
  • Action Required: Replace b-badge with MBadge in your Vue components.
• Dashboard: MetaApiErrorAlert has been removed and replaced with the MErrorCallout component.
  • Action Required: Replace MetaApiErrorAlert with MErrorCallout in your Vue components.

Added

• SDK: Added virtual IPlayerModelBase.UpdateTimeZone() method to allow restricting player time zone changes. Sample implementation is included in the Idler sample.
• SDK: MetaSerialization now reports the type and member name when encountering an unexpected type.
• SDK: MetaSerialization now reports the ConfigKey and spreadsheet Url when encountering an invalid MetaRef in a game config item.
• SDK: MetaSerialization now supports deserializing objects by invoking the constructor, this enables support for Records and read-only structs. You can use this by either passing MetaSerializableFlags.AutomaticConstructorDetection to [MetaSerializable] or by add the [MetaDeserializationConstructor] attribute to your constructor.
• SDK: MetaSerialization now supports serializing Tuple and ValueTuple up to 7 elements.
  • Note that the order of parameters has to stay the same, similarly to MetaSerializableFlags.ImplicitMembers.
  • Tuple and ValueTuple are compatible with a class and a struct respectively, meaning you can change the Tuple/ValueTuple to an instance of a class/struct provided you keep the same TagId order of the members.
• SDK: MetaSerialization now supports DateTimeOffset, Version, Guid, TimeSpan, ReadOnlyCollection<T>, and ReadOnlyDictionary<Key, Value>.
• SDK: [BigQueryAnalyticsName("...")] and [FirebaseAnalyticsName("...")] attributes for overriding the name of an analytics event or a parameter in an analytics event, which would by default be determined by the C# class or member name.
• SDK: It is now possible to have multiple config libraries with the same item type, or different item types inheriting from the same base class which implements IGameConfigData<>. Reference resolving will look for the item in each library whose item type is compatible with the reference.
• SDK: Analytics events "keywords" for convenient classification and filtering of analytics events in the dashboard.
• SDK: Added LeagueManagerOptions.AllowDivisionBackFill option to turn off division backfilling when removing a participant from a division.
• SDK: Added LeagueManagerOptions.ConcludeSeasonMaxDelayMilliseconds option to introduce a delay to divisions concluding.
• SDK: Added a new abstraction for game config build sources communicated in GameConfigBuildParameters.
• SDK: Added integration extendable abstract IGameConfigSourceFetcher system for implementing fetching of game config source data, and SDK implementations of google sheets and local file fetching.
• SDK: Added integration hook GameConfigBuildIntegration to encapsulate various extension points related to game config building.
• SDK: Added configBuildSource parameter to GameConfigEntryAttribute for specifying the used game config build source per entry.
• SDK: Added server-side limit of 1000 on the list of individually targeted players in broadcasts and notification campaigns, configurable in ServerOptions.
• SDK: Added new EnvironmentConfig system and the DefaultEnvironmentConfigProvider that replaces the Idler sample's DeploymentConfig and similar systems in other samples. Refer to the Release 25 environment configs migration guide for more information on migrating to the new system, or implementing a simpler minimal integration.
• Dashboard: Added a new unified way to handle errors on the dashboard. Using the MErrorCallout component, you can now display both technical and non-technical errors in a consistent and user-friendly way.
• Dashboard: LeagueDetailView now has a migration progress indicator during preview phase using new MProgressBar component.
• Dashboard: Event log cards (for example the player analytics event log) can now be filtered based on the newly added keywords in addition to the existing event types and general search. The underlying MetaEventStreamCard component has hew properties to both set and freeze the filters to easily create cards that show a specific subset of all the events.
• Dashboard: New sidebar section for building and managing localizations as OTA updates to clients. This is a first pass on the UI with focus on viewing the localization contents and any missing keys to help with release management workflows on large games.
• Dashboard: Added the LiveOpsDashboard.DashboardHeaderColorInHex and LiveOpsDashboard.DashboardHeaderLightTextColor runtime options to customize the dashboard header color and text color in your environments.
• Dashboard: New MetaUiNext components. Run pnpm storybook in the MetaplaySDK/NodePackages/MetaUiNext folder to see the components in action.
  • MBadge - A colored box/pill to highlight information. Replaces b-badge.
  • MTooltip - A utility to show tooltips.
  • MInputSingleSelectDropdown - A minimalistic select input for string values.
  • MInputSingleCheckbox - A single checkbox input for boolean values.
  • MInputTextArea - A textarea input for string values.
  • MErrorCallout - A specialized callout to display technical errors.
• Dashboard: The add<listName>OverviewListItem and the addUiComponent have been extened to support hiding of overview list items and UI placement components based a user's permissions.
• Dashboard: Pinned Vue version to 3.3.4 to avoid withDefault boolean type bug with vue bootstrap.

Changed

• SDK: Change solution files to use "Any CPU" and remove explicit x64 and arm64 from C# project files. This fixes build issues when using the solution files.
• SDK: It is now an error for PlayerModel or other ISchemaMigratable classes to have extraneous [MigrationFromVersion(fromVersion: x)] methods where fromVersion is outside the range specified in the [SupportedSchemaVersions(...)] attribute. This is intended to guard against mistakes in the specified version range.
• SDK: Game config libraries no longer register as config resolvers to the GameConfig instance on import (or library build), the operation of registering active resolvers now happens in GameConfigBase.OnConfigEntriesPopulated().
• SDK: The server no longer uses the config build timestamp for figuring out if the current game config should be auto-updated to the builtin config found on filesystem. Config auto-update on server boot now always happens if the builtin gameconfig hasn't been seen in the environment before. This fixes cases where auto-update did not take place due to the live gameconfig having a newer timestamp than the config associated with a server update.
• SDK: It is now possible to extend GlobalState with game-specific data via introducing a game side implementation of GlobalStateManager.
• SDK: Updated the client-side IAPManager to use the IDetailedStoreListener interface added in Unity Purchasing 4.8.0 when available. This fixed a warning about an obsoleted UnityPurchasing method.
• SDK: Game config data now properly supports the Hidden and ServerOnly MetaMember flags for stripping data from the client visible config.
• SDK: The IMetaActivableConfigData fields are now conditionally compiled for server only, which allows implementations to omit them from client visible config data.
• SDK: The "full protocol hash" used for warning about client and server generated serializer potential incompatibility now ignores any meta-members tagged with flag MetaMemberFlags.Hidden or MetaMemberFlags.ServerOnly. This allows hidden and server-only flags to be conditionally compiled only in server builds without resulting in compatibility warnings during the login handshake.
• SDK: A memory-expensive debug check (added in release 24) done at config build time is now disabled in non-local server environments. The check guards against certain kinds of bugs in SharedGameConfig.OnLoaded and is likely only worthwhile during development, not during live operation.
• SDK: TCP backlog is now inspected with sock_diag instead of /proc/net/tcp for reduced overhead.
• SDK: JSON Serialization in the Admin API now ignores properties that throw exceptions, these properties are excluded from the output of the endpoint. Exceptions are deduplicated (by message, to prevent spam) and are still logged to the server output after serialization is complete.
  • We recommend that these exceptions are still fixed, as it can lead to degraded performance and error fatigue.
• SDK: The game config classes (implementations of ISharedGameConfig and IServerGameConfig) are no longer required to contain config library entries associated with SDK features. Runtime stub libraries are exposed via the base class implementation when no concrete entry is declared by the game integration config class. Additionally the following uses of SDK config libraries have been updated:
  • The config data exposed to dashboard via SystemStatusController is now augmented with stub data when no config entry exists.
  • MetaActivableRepository check for config data associated to offer groups existing has been removed.
• SDK: Change the config archive content hash for an empty archive (no entries present) to not conflict with ContentHash.None for the ability to refer to an empty archive separately from a missing archive.
• SDK: Removed GameConfigBase.ArchiveVersion. With the introduction of ServerOnly game config data the game config content hash is no longer the same for server and client, and therefore relying on the ArchiveVersion property of the in-memory game config is prone to error.
• Unity Editor: Model Inspector now displays IEnumerable types as collections.
• Metrics: Added metaplay_in_maintenance gauge which has the value of 1 when the game server is in maintenance.
• Metrics: Entity subscribe durations and counts are now represented separtely per target entity in game_entity_ask_duration and game_entity_asks_total metrics. This allows identifying which SubscribeToAsync() call is causing elevated metrics.
• Dashboard: MetaUsername component no longer needs URL or permissions to be passed in.
• Dashboard: The core page layout has been rebuilt with the new MetaUiNext components.
• Dashboard: The quick links section is now a popover instead of a modal for better usability.
• Dashboard: SegmentDetailView, OfferGroupDetailView, OfferDetailView, ActivableDetailView now using single endpoint subscription instead of deconstructing all endpoint data.
• Dashboard: The subscriptions API has changed to become significantly easier to use. useStaticSubscription and useDynamicSubscription are now deprecated. Update all callsites to use the new useSubscription API instead. Check the "Working with Subscriptions" documentation for how to do this.
• Dashboard: Improved display of game configs that contain errors or that can no longer be deserialized due to changes in game code.
• Dashboard: A UX pass on the individual player targeting form in broadcasts and notifications. It should now be easier to use and understand.
• Dashboard: Unified error handling and displaying on the dashboard. Using the MErrorCallout component, you can now display and share both technical and non-technical error information in a consistent and user-friendly way.
• Dashboard: Event stream cards (like the player analytics events log) filtering utilities are now OR instead of the previous AND between the different filters. This makes it easier to drill down into specific events. There is also a new text label to make it clearer how the filters act as you enable them.
• Dashboard: Game config building from dashboard is now enabled by default if the integration provides available game config sources by overriding GameConfigBuildIntegration.GetAvailableBuildSources.
• Dashboard: Removed the "Overview of changes" section links from the game config diff page due to a regression in how the page rendering works. This page is due for a re-design that will introduce a better way to navigate large diffs. Tentatively planned for release 26.
• Tests: The integration tests now log all docker invocation outputs by default. Added the -q/--quiet flag to get the old behavior.

Fixed

• SDK: Fixed the player re-deletion feature.
• SDK: Fixed the racy build failures when building the solution files with dotnet build. Previously, the build could fail with error CS2012: Cannot open ... for writing.
• SDK: model.CurrentTime now has a valid value (instead of epoch) already during model schema migrations. This applies to players, guilds, and multiplayer entities such as divisions. This also fixes the PlayerEventModelSchemaMigrated and GuildEventModelSchemaMigrated analytics events having an invalid timestamp and thus being rejected from BigQuery.
• SDK: Loss of websocket socket without clean shutdown is no longer logged on error level.
• SDK: Session resume failures after restoring application from background is more robust and interprets this more reliably as a SessionLostInBackground error.
• SDK: The fixed-point ToString() methods now produce deterministic string outputs that can be parsed to the original value losslessly. The output is also the shortest such string for better human readability.
• SDK: The fixed-point Parse() methods now handle rounding properly to achieve lossless fixed->string->fixed conversions.
• SDK: Fix handling of Akka.NET log message parameters.
• SDK: The leagues system season migration no longer drops participants from season migration in case of a crash.
• SDK: Fixed crash in Android client builds on Android 6. The SDK code was using an API added in API level 24 which is only available in Android 7 and above.
• SDK: Fixed iOS build failing if Symlink Sources build setting was enabled.
• SDK: File reading via FileUtil methods now allows the file to be open in other applications. This is done by opening the file with the FileAccess.Read and FileShare.ReadWrite flags.
• SDK: Fixed async matchmaker player deserialization and added better error reporting.
• SDK: ConfigParser can now parse all StringId<>, enum, and Nullable<> types (assuming the Nullable<>'s underlying type is parseable), regardless of whether those types appear as key types in GameConfigLibrary<,>s.
• SDK: Fix network thread hang detection (thread pool starvation) to also detect hangs in early login.
• Unity Editor: Fixed a rare deadlock of Unity Editor that could happen when 1) Game was in Play-mode, 2) Editor was being put into background, 3) and client was at a very precise moment in processing a network message.
• Unity Editor: Fixed Model Inspector leaving an empty child proxy to collections whose last member was removed.
• Dashboard: Entity Import and Export error messages now display the whole error message.
• Dashboard: Improved sluggish segment selector in audience targeting components when there are a large number of segments.
• Dashboard: Improved explictness of boolean checks on all dashboard alerts enhancing readability and maintainability of the code.
• Dashboard: Fixed issue where events without descriptions would cause the event log cards (eg: the "Latest Player Events" card) to error out.
• Dashboard: Fixed issue where fetchSubscriptionDataOnceOnly could hang forever if the requested endpoint returned no data.
• Dashboard: Fixed error handling on the player overwrite form. An error message is now shown when an overwrite request fails.
• Dashboard: Fixed links to logs displaying a Deprecation Notice in Grafana.
• Dashboard: Entity archive import and player import now display error messages more clearly and use clearer language on the changes applied or to be applied.
• Dashboard: Fixed an issue in the broadcast and notification time picker that would sometimes give unexpected results when changing the start date into the future.