Highlights

New Feature: New Metaplay CLI

The new Metaplay CLI is a huge improvement over the previous CLI:

• Faster - being written in Go, the new CLI is significantly more responsive.
• Better usability - the CLI output has gotten much more attention, with a focus on readability.
• Error handling - the CLI does a lot of validation in order to give clear and understandable error messages.
• Self-hosting - the new CLI also works with self-hosted stacks and environments.
• Open source - the CLI is licensed under the permissive Apache-2.0 license.

The new CLI packs a lot of useful functionality:

• Docker builds - Docker images can be built with metaplay build image.
• Server deploys - deploys a built Docker image is done with metaplay deploy server.
• Server logs - reading logs from one or more pods is now easy with metaplay debug logs.
• Server debugging - multiple commands were introduced to help troubleshoot issues on cloud servers, e.g., metaplay debug run-shell to start a shell.
• Server profiling - use metaplay debug collect-heap-dump to collect a memory heap dump and metaplay debug collect-cpu-profile to collect a CPU profile from a cloud server.
• Local development - use the metaplay dev ... commands to run the server, dashboard, botclient, or the Docker image locally.
• Manage secrets - you can manage Kubernetes secrets for your game server with the metaplay secrets ... commands.
• SDK integration - Metaplay can be integrated to your project using the metaplay init project command.
• Dashboard customization - a custom LiveOps Dashboard can be added to your project with the metaplay init dashboard command.

For installation instructions and more details, see the GitHub page.

Compatibility with SDK releases

The new CLI replaces the old metaplay-auth CLI. The old CLI is now considered deprecated and will only receive critical updates.

When upgrading to R32, you should also switch to using the new CLI. The new CLI also works with R31 and older, with the exception of Docker image builds and server deploys.

New Feature: Project Config File

Project configuration is now done via a new metaplay-project.yaml in the project root. This brings many benefits:

• Consolidate project directories into one place, reducing the amount of flags that need to be given to various tools like Docker builds.
• Specify .NET and Helm chart versions for deployments to make upgrading easier.
• List all available environments in the project for easy discovery.

See the Project Configuration guide for more information.

Major Improvement: Admin Authentication Overhaul

We've rewritten our admin authentication system with a focus on performance, security, and extensibility. This ground-up redesign delivers significant improvements across the board:

• Performance Boost: Rewritten in Go, delivering almost twice as fast load times for the LiveOps Dashboard.
• Enhanced Security: Simplified architecture makes the system easier to reason about and more secure by design.
• Expanded Capabilities: Better support for machine users, including also with 3rd party auth providers.
• Future-Proof Design: Architecture designed for easier feature additions and maintenance.
• Better Integration: Authentication gateway is now integrated with Metaplay infrastructure, allowing us to drop external-auth-server.

Migration

For anyone using Metaplay managed cloud, the transition is handled transparently and requires no steps from you. For self-hosting customers, we will reach out to you to help with the migration.

New Feature: Temporary Player Banning

We've updated our banning feature to include the ability to administer temporary bans to misbehaving players. Previously such temporary bans would have to be manually enforced by agents who would need to remember to lift a players' ban after a period of time. This new addition to the tool frees up your agents to think about more important things, as well as giving them new powers to manage players.

Major Improvement: More Business Metrics

In the R31 we introduced Business Metrics, which allowed you to track your key performance indicators from a dedicated page on the LiveOps dashboard. In R32 we've taken things a step further by embedding relevant graphs directly into the pages where they make the most sense. These are fully configurable so that you can decide exactly what you'd like to see, and where.

New Feature: Steam IAPs

Metaplay now supports Steam's microtransactions for in-app purchases when Steam authentication is enabled. Look for "Steam" in Getting Started with In-App Purchases and see Configuring Steam Purchases for more information.

Changes

Metaplay SDK

• Update to .NET 9: MetaplaySDK server projects and samples have been updated to target .NET framework version 9. See the Migration Guide entry For All Metaplay Projects for actions required in your project.
• PublicWebApi: Added a separate ASP.NET web server for hosting public-facing endpoints such as webhooks for 3rd party services and services for players. Contrary to AdminApi, the public web server is sharded to run on all logic nodes by default and doesn't require authentication by the infra layer. See Public Web Endpoints.
• Player Dashboard Actions: Added a new attribute to expose Player Admin Actions to the dashboard. Simply add the PlayerDashboardActionAttribute to any Player Server Action, and it'll automatically show up on the dashboard with a generated form. See Tutorial: Add an Admin Action for more info.
• Player Web Login: The game server can now be configured to act as a OAuth2 client for standards-compliant identity providers and a WebGL games built on Metaplay can use the gameserver login endpoints for player authentication needs. If you are building a WebGL game or consider porting to WebGL, please talk to Metaplay support for details!

Complete List

• Added: [MessageHandler] methods may now take in EntitySubscriber or EntitySubscription instead of EntityId to match only messages sent on the subscription.
• Added: Introduce MetaplaySDK/version.yaml that includes metadata about the SDK version, required infra and Helm chart versions, as well as required .NET, Node.js, and PNPM versions.
• Added: Client authentication will now automatically differentiate Unity Multiplayer Play Mode virtual players.
• Added: StartupRuntimeOptions alternative base class for runtime options that are made available to the server application configuration code before the RuntimeOptionsRegistry is initialized.
• Added: DynamicEnum members are now supported in analytics events.
• Added: Added support to temporarily ban a player and to provide a player facing message, both the end time and the message are delivered to the client for better error messaging.
• Added: integration-tests.py now supports --shared-code-dir to allow the shared code directory to be moved.
• Added: Support for non-daily cohort Game Server Metrics. See the IncidentReportCountsByType metric as an example.
• Added: Dynamic permission checking for Game Server Metrics to allow embedding metrics to different LiveOps Dashboard pages.
• Added: New connection error states for social credentials related login failures. A ClientSideConnectionError with contains exception of type MustReloginError now communicates that the client-side credentials service requires the user to (interactively) log in again. The error state TerminalError.LoginRejected is used to communicate that the server did not accept the given social credentials and that the credentials service did not have the means to automatically refresh the credentials. These errors are translated to CredentialsExpiredError and LoginRejected types in the ConnectionLostEvent provided to IMetaplayLifecycleDelegate.OnFailedToStartSession().
• Added: Added PlayerModel.SessionAuthenticationKey to allow observing the Authentication Key used to start the current session.
• Added: BrowserSdk node project for interfacing with Metaplay Web authentication.
• Added: Multiplayer entities now have OnClientAppStatusChanged() method to allow reacting to client app being put into background or connection being lost.
• Added: Live actor count tracking in the game server metrics, enabling better monitoring of actor distribution in your game servers.
• Added: Add PersistedMultiplayerEntityActorBase.RequestShutdownAndEntityDeletion() to allow multiplayer entities to delete their state.
• Added: Added api.players.gentle, api.players.disruptive, and api.players.dangerous permissions to simplify permission handling for custom features.
• Added: Added EntityActor.ContinueTaskOnActorContext() overload for plain Tasks that do not return a value.
• Added: Added EntityActor.EnqueueOnActorContext() which complements ExecuteOnActorContextAsync(). Unhandled exception in Enqueue- crash the actor, instead of returning a Task that completes with a failure.
• Added: Added cleanup of old game server statistics events from the database.
• Added: Added more helpful logging when a model checkpoint timeline and current model timelines diverge, e.g. when actions and ticks are non-deterministic.
• Added: Optional OnInAppProductRefunded() hook for PlayerModel for handling IAP refunds in a game-specific manner, for example by revoking the granted resources. Note that refund handling is currently not supported for App Store and for Google play is only supported when the refund is issued via the LiveOps Dashboard.

• Changed: [CommandHandler] methods no longer accept MetaMessages. See Migration Guide for details.
• Changed: Common web server functionality has been split out of AdminApiActor into WebApiBase for purpose of sharing this functionality with the newly introduced PublicWebApiActor.
• Changed: The MetaplayHttpException class has been moved into Metaplay.Server.WebApi namespace and the Exceptions static class has been removed.
• Changed: The AdminApiJsonSerialization class has been moved into Metaplay.Server.WebApi namespace and renamed to WebApiJsonSerialization to reflect the fact that it is shared between AdminApi and PublicWebApi.
• Changed: Removed the AuthenticationDomainConfig system used to configure AdminApi authentication per route, authentication is now configured directly in the AdminApiStartup.
• Changed: InAppPurchasePlatform is now a DynamicEnum rather than an enum. This is preparation for making it easier to integrate new IAP stores. This does not change InAppPurchasePlatform's serialization format.
• Changed: The OrderId member in InAppPurchaseEvent and elsewhere in IAP code has been renamed to AlternativePurchaseId, because the old OrderId name was specific to Google Play but can now be used by other platforms as well. As an exception, analytics events still use the name OrderId for compatibility with existing analytics processing systems.
• Changed: InAppPurchaseStatus enum values ValidReceipt and InvalidReceipt have been renamed to the more general Successful and Failed, because not all purchasing platforms involve receipt validation.
• Changed: Generated S3 presigned URLs from S3BlobStorage.GetPresignedUrl now always use V4 signatures. Previously, V2 signature was used for S3 buckets on us-east-1.
• Changed: The integration-tests.py bot runs are shortened to 30sec, use 20 bots and 5 second sessions (from previous 2min run, 100 bots, and 30sec sessions).
• Changed: The validity duration of keys in KeyManager (/.well-known/jwks.json) is now configured with KeyManager:PublicKeyLifetime runtime option. KeyManager:NumPublicKeysToRetain has been removed.
• Changed: The Akka.NET ActorSystem name is now simply node (instead of earlier project name) for better readability.
• Changed: Update entrypoint binary to Go 1.23.6. This fixes CVE-2024-45341 and CVE-2024-45336.
• Changed: Dropped the Helm chart related labels from the docker images. These are now managed in the new metaplay-project.yaml.
• Changed: Authenticating with social credentials for game session has been simplified and improved in a number of ways.
• Changed: If client credentials are invalid, server now responds with a new LoginFailureResponse before closing the connection.
• Changed: On client login when presented with valid social credentials that don't have an existing player account binding the server will now create a new player account and map it to the credentials.
• Changed: Explicitly requesting new account creation with DualSocialAuthLoginMethod has been removed, as a new account is created on-demand anyway.
• Changed: Added fields AuthenticationPlatform and DidBindAccount to LoginSuccessResponse for better communication the outcome of a (social) login operation to the client.
• Changed: Added new methods in ISessionCredentialsService for reacting to login success (OnLoginSuccessAsync()) and failure (OnLoginFailureAsync()). Retired the OnPlayerIdUpdatedAsync() method as OnLoginSuccessAsync() covers the use case.
• Changed: Added the ability to introduce new social credentials providers in UnityCredentialsService via overriding the InitSocialCredentialsProviders() function and implementing the ISocialCredentialsProvider interface. Moved the Steam authentication implementation into SteamCredentialsProvider.
• Changed: Player push notifications are limited to 10 unique push notification tokens. If the limit is exceeded, least recently used tokens are removed.
• Changed: In ServerEndpoint.BackupGatewaySpecs, consecutive entries with empty or null ServerHost are now considered as backup ports for the previous entry with ServerHost set. Previously all entries with unset ServerHost were considered as backup ports for the primary gateway.
• Changed: PlayerActionBase.Id has been removed.
• Changed: The IPlayerClientContext.ExecuteAction overload with the out int id parameter has been removed.
• Changed: The need for defining METAPLAY_ENABLE_WEBGL for WebGL builds has been retired. WebGL specific features in the SDK as well as the WebGL code analyzers are enabled when building for the WebGL platform.
• Changed: Game config sheets are now permitted to have leading empty rows before the header row. Leading empty rows are simply skipped by the config parser.
• Changed: PlayerSessionParamsBase has been split into PlayerSessionParams and PlayerSessionGameParamsBase.
• Changed: Moved PlayerEventPayloadBase and EventPayloadBase to Metaplay.Core.AuditLog.
• Changed: EntityAskAsync and SubscribeToAsync, will now throw EntityNotCreatedError instead of EntityCrashedError if the entity actor fails to initialize due to a missing database save for the entity.
• Changed: EntityActor's virtual method HandleUnknownCommand() can now be async (it returns a Task), consistent with HandleUnknownMessage().
• Changed: Logging:FormatTemplate and Logging:ColorTheme options have been removed. Use Logging:UseColor to enable/disable coloring.
• Changed: When logging a DateTime, the default format is now yyyy-MM-dd HH:mm:ss UTC for Utc kind dates and yyyy-MM-dd HH:mm:ss for Local and Unspecified dates.
• Changed: When logging a DateTimeOffset, the default format is now yyyy-MM-dd HH:mm:ss UTC+xx:yy.
• Changed: [NonSerialized] now produces a warning if used in MetaSerializable classes as it has no effect on Metaplay serialization.
• Changed: The cached app start language is now cleared when credentials are cleared through the menu item in Unity.
• Changed: IChecksumContext.Step(string) has been removed. It had no effect for validation.
• Changed: Multiplayer Entities no longer dry-run client-enqueued Actions before executing them.
• Changed: ClientListeners now work for non-successful actions on Multiplayer Entities, but only for the actions issued by the client itself. Failing actions are communicated back only to the issuing client. For successful actions, ClientListeners work as previously, i.e. they are observable to all clients.
• Changed: ModelUtil.RunAction() no longer takes in IChecksumContext.
• Changed: MultiplayerEntityActorBase._journal has been removed, use MultiplayerEntityActorBase.Model instead.
• Changed: MultiplayerEntityActorBase.DesyncDebugging has been removed, use MultiplayerEntityActorBase.DebugOptions instead.
• Changed: MultiplayerEntityClientBase._enableJournalCheckpointing has been removed. It is now controlled with MultiplayerEntityActorBase.DebugOptions.
• Changed: Client-side MultiplayerEntity consistency checks are no longer controlled with Player's consistency checks but by MultiplayerEntityActorBase.DebugOptions instead.
• Changed: Default checksumming frequency of MultiplayerEntityActorBase has been reduced to once per 10 seconds.
• Changed: (Guest) credentials storage in Unity client has been refactored, the platform (Android/iOS) specific storage backends have been extracted to implement the internal IPlatformCredentialsStorage interface and the potentially time-consuming initial load operation has been split to happen in parallel to other initialization.
• Changed: On client, MetaplaySDK.DownloadCachePath is now stored on platform specific cache folder.
• Changed: Deprecated ServerHello.FullProtocolHash and client-side reporting of potential mismatch. This is now replaced by the server communicating the protocol has mismatch via explicit message ClientFullProtocolHashMismatch. The mismatch is now reported only if the client is on the latest logic version, to prevent false positive warnings.
• Changed: Optimized GameConfigRepository initialization by eliminating scanning of GameConfig types, integration types are now resolved from the IntegrationRegistry.
• Changed: FacebookDataDeletionWebhookController and FacebookDeauthorizeWebhookController have been merged into a single FacebookCallbacksController.
• Changed: Facebook data deletion and deauthorization endpoints are now served both by the AdminApi webhook route and by the new PublicWebApi endpoint under route prefix facebook. The legacy endpoints in the AdminApi are considered deprecated and are subject to be removed in the future.

• Fixed: The check that GameConfigLibrary<,> key types override equality and ToString() methods now happens at an earlier time during game config build. Previously, the config build could fail with unclear error messages due to missing those methods; now, it will provide better error messages instead.
• Fixed: Game config build now detects duplicate keys with better error messages in case the duplicates were only introduced when parsing the key from string (e.g. only whitespace differences in the source sheet).
• Fixed: The Model Inspector now keeps the expanded state, user set flags and the search query between playmode sessions.
• Fixed: Serialization attributes such as [ServerOnly] now work correctly when using implicit member id generation.
• Fixed: Fixed error messages of InvalidOperationExceptions in GeolocationUpdaterFromOrigin if server failed to connect to other cluster members.
• Fixed: Serializing a DynamicEnum now produces its name string rather than a JSON object containing id, name, and isValid.
• Fixed: Reduce allocations of PlayerModel.GetMetaOfferGroupsToFinalize.
• Fixed: Fixed UDP Passthrough failing to start UDP servers when in in Cloud-IP mode.
• Fixed: Fixed UDP Passthrough gateway list being empty on non UDP-enabled server nodes.
• Fixed: S3-based incident upload now works on servers hosted on us-east-1 region.
• Fixed: Browser resources (timers and websockets) are now properly released when MetaplaySDK.Stop() is called. Timer and socket callbacks happening after SDK deinitialization (including unity app shutdown) previously could cause page freezes.
• Fixed: The Unity Layouts menu item is now available again.
• Fixed: Model Inspector now caps at a depth of 32 to handle recursive references instead of bailing out.
• Fixed: Model Inspector now shows types DateTimeOffset, DateTime and TimeSpan as simple values of the ToString() output of the type.
• Fixed: Nullable MetaTime, MetaDuration, F32, F64, NftId, MetaGuid, MetaCalendar, SessionToken, and EntityId are now deserializable using JSON.
• Fixed: The Model Inspector is now able to correctly show collections longer than the window.
• Fixed: On Unity, GameConfig is now loaded on a background thread to keep main thread responsive.
• Fixed: WebSocketOptions.ListHost now defaults to "127.0.0.1" in local builds rather than "localhost", as web clients connect with IP rather than hostname.
• Fixed: In GameConfigKeyValue sheets, a single variant override row can now specify multiple variants separated by commas. Previously this was only supported in GameConfigLibrary sheets.
• Fixed: Exception stacktrace lines logged with IMetaLogger.Error(Exception, Format, ...) are now labelled with ERR level in Loki (Grafana log search).
• Fixed: Unity WebGL builds with Unity 6 when not using the build option WebAssembly.Table were unable to resolve javascript-to-c# callbacks due to function getWasmTableEntry not being available in .jspre files.
• Fixed: The default localization language to use in WebGL builds now uses MetaplayCore.Options.DefaultLanguage correctly. Previously a random supported language was erroneously picked when a localization matching the user's browser language was not found.
• Fixed: Invalid Facebook login tokens are rejected with a proper error status. Previously tokens were rejected with TemporarilyUnavailable status.
• Fixed: On Android and iOS, GameConfig download cache is now stored in the app's cache folder.
• Fixed: Fixed incorrect and confusing error message "Target shard does not exist in the current sharding. Check the Sharding Strategy of the entity." when a connection was lost between server nodes.
• Fixed: The GameConfig archive in StreamingAssets directory is used if available, instead of being re-downloaded.
• Fixed: MessageDirection is now checked properly for messages sent by Client to a Multiplayer Entity.
• Fixed: MetaRecurringCalendarSchedules are now sanity-checked (e.g. duration cannot exceed recurrence) during game config parsing. This sanity check existed in the past but was accidentally disabled in release 25.
• Fixed: Improved deserialization performance on IL2CPP platforms.
• Fixed: Serializer DLL build for Unity editor specifies AssemblyBuilderFlags.EditorAssembly which fixes issues with incremental device builds incorrectly depending on device assemblies.

LiveOps Dashboard

• New MRawDataCard Component: We've replaced the MetaRawData with a new MRawData component. The new iteration of this invaluable development tool is more readable, giving your developers better insight into the data that makes the dashboard work.

• New MInputToggleGroup Component: This new component combines a feature toggle with layout, allowing you to de-clutter your UI by hiding detailed information when it's not relevant.

Complete List

• Added: A new MDateTime component for an easy way to display time with extra tooltips for time zone conversions. Replaces the previous MetaTime component.
• Added: @metaplay/meta-utilities now has four new functions to convert ISO time strings and Luxon DateTimes into UTC plain dates and times.
• Added: A new MCountryCode component that converts ISO country codes to human readable flags and names.
• Added: A new MIpAddress component that helps display IP addresses in a more human-readable format.
• Added: The audience targeting UI's individual player input now supports whitespace, semi-colons, and commas — or even a mix of all three — as separators for player IDs. This makes copy-pasting player IDs from various sources easier.
• Added: The MInputSwitch component now has support for labels and hint messages and also has improved interactive colors for better visual feedback.
• Added: A new MInputSingleSelectDropdown component that allows for a single-select dropdown input with searching and auto-completion. All dropdowns in the dashboard have been upgraded to use this new component and many have gotten visual tweaks while at it.
• Added: A new MInputSingleSelectAsyncDropdown component that allows for a single-select dropdown input with searching and auto-completion, with the options fetched asynchronously from external APIs.
• Added: A new MDuration component to display durations in a human-readable format.
• Added: Player and guild searching now use the new MInputSingleSelectAsyncDropdown component and support infinite scrolling to load more search results. This is great for when you have many players with similar names.
• Added: Two new reusable types, MInputSelectOption and MInputSelectClearButtonOption, to standardize and simplify the definition of options for input components.
• Added: A new MRawDataCard component that displays raw data (for example parsed JSON responses from APIs) in a more human friendly format.
• Added: A new useDeveloperUI composable that allows you to check and toggle the global developer UI setting.
• Added: New MInputToggleGroup component that lets users toggle optional sections in the dashboard.
• Added: A new inlineLabel prop to the MInputCheckbox and MInputSingleSelectRadio components to allow for positioning the label inline with the input.
• Added: A new hintMessage prop to the MInputSingleSelectRadio that lets you add optional hint messages for each radio button.
• Added: Added new updateUiComponent function that gives more flexibility to replace or update UiPlacements.
• Added: Added metric charts to "Player Incidents", "Server Messages" and "Environment" pages.
• Added: Added metaplay/prefer-datetime-utc ESLint rule to enforce the use of DateTime.utc() instead of DateTime.now().
• Added: Added generated forms support for MetaDuration, MetaCalendarDateTime, and MetaCalendarPeriod types.
• Added: The Scan Jobs list view now shows scan jobs on a timeline.

• Changed: The MetaEventStreamCard (call sites such as player event logs) will now show time stamps in UTC time instead of browser local time.
• Changed: MCard's header-right slot no longer has fixed width but instead better responds to dynamic widths. Use manual width classes to force a specific width (for example for a text input) if needed.
• Changed: The audience targeting UI has a new design that works better on all screen sizes and leverages the new MInputSingleSelectDropdown component. The underlying MessageAudienceForm component was renamed to PlayerSegmentsInput and will likely evolve further in future releases.
• Changed: Timeline inspector event properties section now has a maximum height to keep very large event properties lists from expanding the page indefinitely.
• Changed: The MetaIpAddress component has been deprecated in favor of the new MIpAddress component.
• Changed: The MetaCountryCodecomponent has been deprecated in favor of the new MCountryCode component.
• Changed: The MetaAlert component has been removed in favour of the newer MCallout component.
• Changed: The automatic import of the BAlert component from Bootstrap-Vue has been removed in favour of our own MCallout component.
• Changed: The MetaInputSelect component has been removed in favor of the new MInputSingleSelectDropdown component.
• Changed: The MetaDuration component has been removed in favor of the new MDuration component.
• Changed: The MetaRawData component has been removed in favor of the new MRawDataCard component.
• Changed: The MetaPluralLabel component has been removed in favor of using the underlying maybePluralString function directly.
• Changed: The maybePluralString utility was changed to make all overloads mandatory to make its API more obvious and easier to use.
• Changed: MetaGenerated UI components hint messages are now unified in styling.
• Changed: Generated Vue files under dist/assets are now marked Cache-Control: immutable with a 1 month lifetime for more efficient caching.
• Changed: All endpoints under api/ will now set Cache-Control: no-store header by default to prevent polluting browser cache.
• Changed: Developer UI and safety lock now act the same in dev and prod, so developer UI is off by default and safety locks are on by default. The settings are still persisted in local storage.
• Changed: Improved the Game Server Metrics page with added information and better controls, including linkable time ranges.
• Changed: Migrated the parseDotnetTimeSpanToLuxon from Core to MetaUiNext.
• Changed: The Ban Player admin action UI/UX has been redesigned to support temporary bans, allowing users to set a ban duration and send a custom message to the banned player.
• Changed: Refactored activables views to use a tab layout, improving their readability.
• Changed: The average values displayed in daily cohort charts are now weighted averages based on the amount of registered users on the given day.
• Changed: Refactored the GameConfigActionPublish, GameConfigActionArchive, LocalizationActionArchive, and LocalizationActionPublish modals to clearly explain the actions available to the user.
• Changed: Refactored the ScanJobsPauseAllJobs, PlayerActionSetDeveloper, PlayerActionSetTester, PlayerActionJoinExperiment and the PlayerActionToggleDebugMode modals to better explain the action being taken.
• Changed: Removed the utility function durationToMilliseconds, use Duration.fromISO(...).toMillis() instead.
• Changed: In the Purchase History card on the player page, the "Order ID" field has been renamed to "Alternative Purchase ID". It was renamed because "Order ID" was specific to Google Play, but this field has now been generalized to other platforms (in particular Steam).
• Changed: In the Purchase History card on the player page, the status badge for successful purchases now says "Successful" instead of "Validated" and for failed purchases "Failed" instead of "Invalid Receipt". The terminology was generalized because not all purchasing platforms involve receipt validation.
• Changed: The charts on the Overview page are now using higher quality metrics graphs.
• Changed: The Metrics page now has a live updating mode in addition to the fixed time window mode.
• Changed: The LiveOps Events page timeline is the now full width of the browser to show more content at once.
• Changed: The MInputNumber and MInputTime components no longer require a focus change to output their values.
• Changed: Active and paused experiments are now sorted before experiments in testing phase on the experiments page.

• Fixed: A bug in the MetaEventStreamCard component that occurred when keyword filters were applied, causing the card to display incorrect information when no matching events were present. Now, the card correctly shows a message when no events match the filter criteria.
• Fixed: A bug in EntityEventLogCard where the loading spinner would be shown forever if the event stream was empty.
• Fixed: MInputSingleSelectRadio no longer accepts an undefined initial value, which caused an unexpected visual state.
• Fixed: A bug in the attachment picker for the "Send Mail" player action that caused duplicate or incorrect options to appear in the drop-down has been resolved.
• Fixed: A bug that would sometimes cause the main page to have a few pixels of horizontal scroll has been resolved.
• Fixed: The league list page would crash if a league had no schedule status.
• Fixed: Localization Diffs now include changed entries where either side was #MISSING#.
• Fixed: The dashboard root index.html is no longer cached to fix issues with stale versions being served from the browser cache.
• Fixed: MInputDuration now shows the duration as Days, Hours, and Seconds instead of as Milliseconds.
• Fixed: MInputDurationOrEndTime's exact date picker switch no longer overflows to the next line on elements with a small width.
• Fixed: MInputDurationOrEndTime now pre-fills the duration picker when switching from the exact date picker to the duration picker.
• Fixed: Schedule overlap warnings are now shown when creating or editing a LiveOps Event.
• Fixed: Fixed various timezone related UI issues where timestamps would be incorrectly based on browser time instead of UTC time.
• Fixed: The time and duration pickers no longer behave weirdly when near zero or 24 hours, where a local browser time zone issue previously could make them jump days unexpectedly.
• Fixed: Numerous fixes and improvements to the timeline component.
• Fixed: Experiments form now checks that target audience input is valid.
• Fixed: An alignment issue in the MInputStartDateTimeAndDuration component. The duration input is now aligned with the start date and time input.
• Fixed: Transition issue between the duration input and the end date input in the MInputDurationOrEndDate component. The layout no longer jumps when toggling between inputs.

Documentation

• New Game Server Metrics Pages: New pages that explain the game server metrics feature, its use cases, limitations, and how to customize the feature and create your own metrics. Get started here: Introduction to Game Server Metrics. Learn about adding your own metrics here: Customizing Game Server Metrics.

Complete List

• Added: Tutorial: Add an Admin Action which explains how to easily expose new dashboard admin actions for your players.
• Added: Multi-Region Backend describes how to run the server on multiple geographical locations to minimize network latency.
• Added: Dashboard User Authentication explains how to manage roles and authorization in the LiveOps Dashboard.
• Added: Configuring Steam Purchases describes additional considerations needed to configure in-app purchases for Steam.
• Added: Public Web Endpoints documents the process of implementing public web endpoints in your game server.

Migration Guide for All Customers

Please apply the following changes to your project to ensure compatibility with the latest Metaplay SDK.

Backward-Incompatible Changes

Bump your game's MetaplayCoreOptions.supportedLogicVersions to force a synchronized update of your game client and server.

Upgrade Helm Chart to Latest Version

The Metaplay SDK now requires Helm chart v0.8.0 or later for cloud deployments.

Migration Steps:

1. Update your metaplay-project.yaml to the latest Helm chart version.

   metaplay-project.yaml

   serverChartVersion: 0.x.y
   serverChartVersion: 0.8.0

2. Roll out the change to each environment by running the CI job to build and deploy a new version.

   You can do this for each environment separately, whenever is a good time for you.

Migration Guide for Self-Service Customers

Premium SDK Update Support

If your support contract includes Metaplay-provided SDK updates, all the following steps have already been applied to your project. You can skip this migration guide!

This guide offers step-by-step instructions for migrating your project to the latest version of the Metaplay SDK. You can skip the migrations steps for features you are not using in your project.

For All Metaplay Projects

The following core SDK changes affect all Metaplay projects:

Apply Database Schema Migrations

Metaplay's built-in database schema has changed, and you need to apply the migration steps to your project.

Migration Steps:

1. Generate the database schema migration code with:

   # Install or update the EFCore tool:
   Backend/Server$ dotnet tool install -g dotnet-ef
   # Then, generate the migration code:
   Backend/Server$ dotnet ef migrations add MetaplayRelease32

2. Then, add the generated files to your project's source control. For example, using Git:

   Backend/Server$ git add .
   Backend/Server$ git commit -m "Database schema migrations"

The migration steps will be automatically applied when you deploy the updated game server into an environment.

Generate metaplay-project.yaml

The new project config file metaplay-project.yaml will act as the main configuration file for your project going forward and is used by the CLI to interact with your project.

Migration Steps:

1. Generate the metaplay-project.yaml project config file using the CLI in your project's root directory (usually the repository root):

   MyGame$ metaplay init project-config

   The CLI will automatically detect most configuration parameters and ask you the rest. There are override flags in case any of the detection was not correct.

   Your managed environments in Metaplay cloud are also automatically populated in the generated file.

2. Review the generated metaplay-project.yaml that everything looks correct.

3. Add the generated metaplay-project.yaml file to your version control system, eg:

   MyGame$ git add metaplay-project.yaml
   MyGame$ git commit -m "Add Metaplay project config file."

Upgrade to .NET 9

All server and tool builds depending on MetaplaySDK R32 require using the .NET toolchain from the .NET 9 SDK, even if you choose to continue to target .NET 8 in your own projects.

Migration Steps:

1. Update the sdk entry in the global.json file of your project to specify at least version 9.0.100:

   {
     "sdk": {
       "version": "9.0.100",
       "rollForward": "latestFeature"
     }
   }

2. Once the R32 update is merged to your development branch, instruct all developers to install and switch to the .NET 9 SDK.

3. Update the .NET toolchain version used by any CI jobs.

   Note that Dockerfile.server shipped with the Metaplay SDK has been updated to use the .NET 9 SDK so any docker image builds in CI will use the correct .NET SDK version without further action required.

Additionally we strongly recommend updating the target framework of your server and tools builds to target .NET 9 runtime. The actions for updating your project are:

1. Update the dotnetRuntimeVersion entry in the metaplay-project.yaml file to specify 9.0:

   dotnetRuntimeVersion: "8.0"
   dotnetRuntimeVersion: "9.0"

2. Edit the TargetFramework property in all .csproj files to specify net9.0:

   <Project Sdk="Microsoft.NET.Sdk">
     <PropertyGroup>
       <TargetFramework>net9.0</TargetFramework>
       <OutputType>Exe</OutputType>
       ...

3. Verify that your code continues to build against .NET 9:

   MyProject$ metaplay build server

Note

In R32 the Metaplay projects continue to additionally support .NET 8, in case updating your own projects proves to be problematic.

Simplify Helm values files

The CLI now automatically injects the default configuration for the Helm chart deployment, replacing need for the default parameters for the Helm values files in Backend/Deployments/*.yaml.

Migration Steps:

1. You can remove the following items from each Helm values file in your Backend/Deployments/*.yaml as these are now injected by the CLI automatically when doing a deploy.

   environment: develop
   environmentFamily: Development
   config:
     files:
       - "./Config/Options.base.yaml"
       - "./Config/Options.<env>.yaml"
   tenant:
     discoveryEnabled: true
   shards:
     - name: ...
       singleton: ...
       requests:
         cpu: ...
         memory: ...

   If you have not modified these files, you can just remove them.

2. If any YAML files remain (with only your customization in them), add a reference to the file in your metaplay-project.yaml for the environments you want to use it in, for example:

   environments:
     - name: develop
       ...
       serverValuesFile: Backend/Deployments/develop-server.yaml

For more information, see the Configuring a Deployment guide.

For Games With Customized LiveOps Dashboard

The following LiveOps Dashboard changes affect projects that have a game-specific dashboard project:

Install the Correct Node Version

You should ensure that you have Node version 22.14.0 (the latest 22.x version at the time of writing) installed. To check the current version, run node --version. If you are using nvm, you can update Node with:

# Install Node 22.14.0 with Node Version Manager (nvm).
nvm install 22.14.0

# Use the new version.
nvm use 22.14.0

Update the Node version in your project's package.json file to reflect the new requirement:

"engines": {
   "node": "20.x"
   "node": ">=20"
}

Clear Dashboard Dependencies

Migration Steps:

1. Remove any files that Node has cached in your repository. This will lead to a fresh install of all dependencies.
   • Run git clean -fdx ':(glob)**/node_modules/*' from the root of your repository. This clears any currently installed dependencies.
   • Run git clean -fdx ':(glob)**/dist/*' from the root of your repository. This clears any previously built files.
   • Delete the pnpm-lock.yaml file from the root of your repository. This clears the cached dependency versions.

Update the LiveOps Dashboard Project Files

As usual, we have updated the underlying dependencies and configurations of the LiveOps Dashboard. This causes changes to several configuration files, which you will need to update in your dashboard project. We use the MetaplaySDK/Frontend/DefaultDashboard folder as the source of truth for these files.

Migration Steps:

1. Update the package.json to update your project's dependencies.

   • If you have custom dependencies, manually update them or use a file comparison tool to merge the changes.
   • If not, copy and overwrite the package.json file directly from the MetaplaySDK/Frontend/DefaultDashboard directory. Next, restore the name property inside the file to that of your project. This is typically of the form "name": "<projectName>-dashboard".

2. Run pnpm install in your 'Dashboard' folder. This recreates all of the above files and folders with the correct dependencies.

For Games With Custom LiveOps Dashboard Components

As a part of continued code review and polish of the dashboard codebase, we have done a few breaking changes to internal APIs that you may be using in your custom components.

Remove Deprecated Components

As part of this release, the following components have been removed in favor of the new MetaUiNext components:

• MetaIpAddress is replaced by MIpAddress.
• MetaCountryCode is replaced by MCountryCode.
• MetaAlert is replaced by MCallout.
• MetaRawData is replaced by MRawDataCard.
• MetaDuration is replace by MDuration.
• MetaTime is replace by MDataTime.
• MetaPluralLabel is replaced by using maybePluralString() directly.
• durationToMilliseconds is replace by using Luxon's fromIso and toMillis functions.

Migration Steps:

1. Find all instances of the removed components in your dashboard project.

2. Import the new component from the MetaUiNext package:

   import { MIpAddress, MCountryCode, MCallout, MRawDataCard, MDuration, MDateTime } from '@metaplay/meta-ui-next'

3. Replace the removed components with the new ones, and adjust the props and syntax as needed.

• For MetaIpAddress replacement:

  - meta-ip-address(:ipAddress="ipAddress")
  + MIpAddress(:ipAddress="ipAddress")

• For MetaCountryCode replacement:

  - meta-country-code(:isoCode="countryCode")
  + MCountryCode(:isoCode="countryCode")

• For MetaAlert replacement:

  - meta-alert(
  + MCallout(
  +   title="Title"
      ...
      )

• For BAlert replacement:

  - b-alert(
  + MCallout(
  +   title="Title"
      ...
      )

• For MetaDuration replacement:

  // In your script block.
  import { Duration } from 'luxon'
  
  //- If you previously used a string, you will need to convert it to a Luxon Duration object first. Adjust your `showAs` prop to use 'topTwoUnits' and 'topThreeUnits' if needed.
  - meta-duration(:duration="durationString")
  + MDuration(:duration="Duration.fromISO(durationString)")

  The old MetaDuration component was more accepting of different source data types. In some cases, you may now see the component report invalid duration. The cause is often that the source data type is not in ISO format, but in Dotnet format. You should migrate these as follows:

  // In your script block.
  import { Duration } from 'luxon'
  import { parseDotnetTimeSpanToLuxon } from '@metaplay/meta-ui-next'
  
  //- In your template block.
  - meta-duration(:duration="dotNetDurationString")
  + MDuration(:duration="parseDotnetTimeSpanToLuxon(dotNetDurationString)")

• For MetaTime replacement:

  - meta-time(:date="luxonDateTime")
  + MDateTime(:instant="luxonDateTime")

  The old MetaTime component was more accepting of different source data types. In some cases, you may now see the component report Invalid DateTime. The cause is often that the source data type is not in Luxon DateTime format, but an ISO string. You should migrate these as follows:

  // In your script block.
  import { DateTime } from 'luxon'
  
  //- In your template block.
  - meta-time(:date="isoTimeString")
  + MDateTime(:instant="DateTime.fromISO(isoTimeString)")

  The showAs formats for MDateTime are also different from the old MetaTime component.

  • For timeago use relative.
  • For timeagoSentenceCase use relativeSentenceCase.
  • For time, date, or datetime use dateTime.

• For MetaRawData replacement:

  - meta-raw-data(
  -   :kvPair="data"
  -   name="someName"
  + MRawDataCard(
  +   :data="data"
  +   label="someName"
      )

• For MetaPluralLabel replacement:

  // In your script block.
  import { maybePluralString } from '@metaplay/meta-utilities'
  
  // In your template block.
  - meta-plural-label(:value="singleOfferData.statistics.numActivated" label="time")
  + p {{ maybePluralString(singleOfferData.statistics.numActivated, 'time', true) }}

• For durationToMilliseconds replacement:

  - const timeInMilliseconds = durationToMilliseconds(isoTime)
  + const timeInMilliseconds = Duration.fromISO(isoTime).toMillis()

Migrate Re-located Functions

The following functions have been moved from Core Utils to the metaplay/meta-ui-next library.

• parseDotnetTimeSpanToLuxon

Migration Steps:

1. Find all instances of the removed function in your dashboard project.
2. Change the import to use the MetaUiNext package:

• For parseDotnetTimeSpanToLuxon:

  - import { parseDotnetTimeSpanToLuxon } from '../../coreUtils'
  + import { parseDotnetTimeSpanToLuxon } from '@metaplay/meta-ui-next'

Migrate the MetaInputSelect Component

The MetaInputSelect component has been removed in favor of the new MInputSingleSelectDropdown or MInputSingleSelectAsyncDropdown components.

Migration Steps:

1. Find all instances of the MetaInputSelect component in your dashboard project.

2. Replace the import for MetaInputSelectOption with the new types:

   • MInputSelectOption for standard options.
   • MInputSelectClearButtonOption for options with clearable values.

   - import { MetaInputSelectOption } from '@metaplay/meta-ui'
   + import { type MInputSelectOption, type MInputSelectClearButtonOption } from '@metaplay/meta-ui-next'

3. Import the new component from the MetaUiNext package:

   import { MInputSingleSelectDropdown, MInputSingleSelectAsyncDropdown } from '@metaplay/meta-ui-next'

4. Update the dropdown options structure to match the new selected type.

   - const exampleOptions = computed((): <Array<MetaInputSelectOption<string>>> =>
   + const exampleOptions = computed((): MInputSelectOption[] =>
       exampleArray.value.map((element) => ({
   -     id: displayName,
   +     label: displayName,
         value: value,
   }))

5. Add a custom search function to enable searching fields other than the option label.

   const customSearchFunction = (options, query) : Array<MInputSelectOption<T>> => {
       // Filter the options based on the query.
       const lowerCaseQuery = query.toLocaleLowerCase()
       return options.filter((option) => {
           const label = option.label.toLocaleLowerCase()
           const value = option.value.toLocaleLowerCase()
           return label.includes(lowerCaseQuery) || value.includes(lowerCaseQuery)
       })
   }

6. Replace the removed components with the new components and update the props accordingly.

• For simple dropdowns, use the MInputSingleSelectDropdown component:

  - meta-input-select(
      :value="value"
      options="options"
      ...
  + MInputSingleSelectDropdown(
      :model-value="value"
      :options="options"
      :search-function="customSearchFunction"
      ...

• For async dropdowns, use the MInputSingleSelectAsyncDropdown component:

  - meta-input-select(
  -   :value="value"
  -   placeholder="Search for a player..."
  -   :options="search"
  -   @input="$emit('input', $event)"
  + MInputSingleSelectAsyncDropdown(
  +   :model-value="value"
  +   :search-function="search"
  +   placeholder="Search for a player..."
  +   :label="label"
  +   @update:model-value="(newSelection) => emit('input', newSelection)"
  )

For Games With Custom Dashboard Permissions

If you have customized the role-to-permission table in your Options.*.yaml files, you need to add the new permissions to the table.

Add New Dashboard Permissions

The following new dashboard admin permissions have been introduced:

• api.players.gentle, api.players.disruptive, and api.players.dangerous - Generic permissions to simplify creating new admin actions.
• api.liveops_timeline.edit - Allows organizing the items, rows, and groups of the LiveOps Timeline.

Migration Steps:

1. Specify which roles should have access to these permissions in your Backend/Server/Config/Options.*.yaml (whichever file you use to configure the access). You can modify the roles as needed.

    AdminApi:
      Permissions:
         ...
         api.metrics.view_sensitive:          [ game-admin                                                                               ]
         api.players.gentle:                  [ game-admin,              customer-support-senior, customer-support-agent                 ]
         api.players.disruptive:              [ game-admin,              customer-support-senior, customer-support-agent                 ]
         api.players.dangerous:               [ game-admin,              customer-support-senior                                         ]
         api.liveops_timeline.edit:           [ game-admin                                                                               ]

Miscellaneous API Changes

These changes affect you in case you happen to use any of the APIs changed. You can build your project to get a list of any incompatibilities instead of going through the list one item at a time.

Update [CommandHandler] Methods Receiving MetaMessages

To avoid accidentally using a wrong handler attributes, [CommandHandler] now detects on server start if the received command is a MetaMessage, and hence if [MessageHandler] should have been used instead. If server fails at startup due to [CommandHandler] no longer accepting a MetaMessage, you should migrate code to use [MessageHandler] or wrap the MetaMessage into a non-MetaMessage wrapper object.

Migration Steps:

1. Either, replace [CommandHandler] to [MessageHandler] for the affected methods.

2. Or, wrap MetaMessage into a wrapper type:

   MyEntityActor.cs

   public record class MyMetaMessageEvent(MyMetaMessage My); 
   void EventStreamExample()
   {
       Context.System.EventStream.Subscribe(_self, typeof(MyMetaMessage)); 
       Context.System.EventStream.Subscribe(_self, typeof(MyMetaMessageEvent)); 
   }
   void SendExample(MyMetaMessage my)
   {
       Tell(_self, my); 
       Tell(_self, new MyMetaMessageEvent(my)); 
   }
   [CommandHandler]
   void Handler(MyMetaMessage mymessage) {} 
   void Handler(MyMetaMessageEvent mymessage) {} 

Update HandleUnknownCommand() to Return Task

EntityActor's virtual method HandleUnknownCommand() now returns Task (instead of void) and can be async. You will need to update your overrides, if any.

Migration Steps:

1. If any of your custom EntityActor classes override HandleUnknownCommand(), change them to return Task.
   MyEntityActor.cs

   protected override void HandleUnknownCommand(object command) 
   protected override Task HandleUnknownCommand(object command) 
   {
       // ... handle the command ...
       return Task.CompletedTask; 
   }

Change InAppPurchasePlatform switches to if-elses

InAppPurchasePlatform has been changed from enum to DynamicEnum in preparation of making new IAP stores easier to integrate. Unlike enum, DynamicEnum is not allowed in C#'s switch statements, so in case your code uses InAppPurchasePlatform in switches, you will need to change those to if-else chains.

Migration steps:

1. Change InAppPurchasePlatform-based switches to if-else.
   MyGameCode.cs

   switch (iapPlatform) 
   { 
       case InAppPurchasePlatform.Apple: 
           HandleApplePurchase(); 
           break; 
       case InAppPurchasePlatform.Google: 
           HandleGooglePurchase(); 
           break; 
       default: 
           _log.Warning("Unhandled IAP platform {Platform}", iapPlatform); 
           break; 
   } 
   if (iapPlatform == InAppPurchasePlatform.Apple) 
       HandleApplePurchase(); 
   else if (iapPlatform == InAppPurchasePlatform.Google) 
       HandleGooglePurchase(); 
   else
       _log.Warning("Unhandled IAP platform {Platform}", iapPlatform); 

Update References to IAP OrderId Variables

The OrderId member in InAppPurchaseEvent and elsewhere in IAP code has been renamed to AlternativePurchaseId to avoid confusion. It was originally used only for Google Play's Order ID, but has now been generalized to other platforms.

As an exception, it is still called OrderId in analytics events, such as PlayerEventInAppPurchased, to avoid interfering with external analytics processing systems.

Migration Steps:

1. Update usages of InAppPurchaseEvent.OrderId to use InAppPurchaseEvent.AlternativePurchaseId instead.
2. Do the same update in any other code IAP code where the compiler complains about orderId not being found.

Update Renamed InAppPurchaseStatus Values

In the InAppPurchaseStatus enum type, ValidReceipt has been renamed to Successful and InvalidReceipt to Failed. Similarly, IAPFlowTracker.FlowStep.FinishedWithInvalidReceipt has also been renamed to FinishedWithFailure.

They were renamed to better reflect the fact that on some purchasing platforms, such as Steam, the purchase process does not involve receipt validation, and a failed purchase does not necessarily mean a cheating attempt (as InvalidReceipt would imply).

Migration Steps:

1. In your C# code, replaces usages of InAppPurchaseStatus.ValidReceipt and InAppPurchaseStatus.InvalidReceipt with InAppPurchaseStatus.Successful and InAppPurchaseStatus.Failed, respectively.
2. In your C# client code, replace usages of IAPFlowTracker.FlowStep.FinishedWithInvalidReceipt with IAPFlowTracker.FlowStep.FinishedWithFailure.
3. In any custom LiveOps Dashboard code that accesses the IAP status, replace usages of ValidReceipt and InvalidReceipt with Successful and Failed, respectively.

Update References to AdminApi HTTP Controller API Namespaces

Some common services used by controller endpoint implementations have been renamed and changed namespace, custom controller implementation may need to be updated.

Migration Steps:

1. Update all references to Metaplay.Server.AdminApi.Exceptions.MetaplayHttpException to refer to Metaplay.Server.WebApi.MetaplayHttpException instead.

2. Update all references to Metaplay.Server.AdminApi.AdminApiJsonSerialization to refer to Metaplay.Server.WebApi.WebApiJsonSerialization instead.

Replace Deprecated S3BlobStorage.GetPresignedUrl() Methods with GetPresignedUrlAsync()

To avoid accidentally blocking threads during credential refresh, S3BlobStorage.GetPresignedUrl has been deprecated. Use S3BlobStorage.GetPresignedUrlAsync instead.

Migration Steps:

1. Replace GetPresignedUrl() with await GetPresignedUrlAsync().

2. If your server environment is on us-east-1, ensure the new URL format works with the downstream systems.

Update Custom ISessionCredentialsService Implementations.

Following the refactoring of the ISessionCredentialsService interface custom implementation of it need to be updated.

Migration Steps:

1. If your custom implementation of ISessionCredentialsService simply adds a new social credentials provider, consider basing your class on the default UnityCredentialsProvider and moving the social credentials functionality into a class implementing ISocialCredentialsProvider instead.

2. Remove updating MetaplaySDK.PlayerId from your implementation, as this is now done by the SDK.

3. Replace OnPlayerIdUpdatedAsync() with OnLoginSuccessAsync().

Replace IntegrationRegistry.IntegrationClasses<T>() Calls with IntegrationRegistry.GetIntegrationClasses<T>()

For clarity and naming consistency, IntegrationClasses<T>() is now GetIntegrationClasses<T>() and returns a Type[] instead of IEnumerable<Type>.

Migration Steps:

1. Replace IntegrationRegistry.IntegrationClasses() with IntegrationRegistry.GetIntegrationClasses().

2. If you need IEnumerable<Type>, you can cast the new return type to IEnumerable<Type>.

Replace Uses of PlayerSessionParamsBase with PlayerSessionParams and PlayerSessionGameParamsBase

To avoid further API breaks when SDK adds more parameters to SessionParams, all SDK parameters have been moved to PlayerSessionParams, leaving PlayerSessionGameParamsBase dedicated to game-specific data.

Migration Steps:

1. If overriden, replace PlayerActor OnClientSessionHandshakeAsync(PlayerSessionParamsBase) with OnClientSessionHandshakeAsync(PlayerSessionParams)

2. If overriden, replace PlayerActor OnSessionStartAsync(PlayerSessionParamsBase, bool) with OnSessionStartAsync(PlayerSessionParams, bool)

3. If PlayerSessionParamsBase was customized by inheriting it, inherit from PlayerSessionGameParamsBase instead. In all usages, in OnClientSessionHandshakeAsync and OnSessionStartAsync, retrieve the PlayerSessionGameParamsBase by casting PlayerSessionParamsBase.SessionGameParams

   PlayerActor.cs

   class MyPlayerSessionGameParams : PlayerSessionGameParamsBase { } 
   class MyPlayerSessionGameParams : PlayerSessionParamsBase { } 
   
   protected override async Task OnSessionFooAsync(PlayerSessionParamsBase sessionParams, bool isFirstLogin) 
   protected override async Task OnSessionFooAsync(PlayerSessionParams sessionParams, bool isFirstLogin) 
   {
       MyPlayerSessionGameParams myParams = (MyPlayerSessionGameParams)sessionParams; 
       MyPlayerSessionGameParams myParams = (MyPlayerSessionGameParams)sessionParams.SessionGameParams; 

4. If PlayerSessionParamsBase was customized by inheriting it, update SessionActor implementation to return PlayerSessionGameParamsBase, and remove any SDK params from the constructor.

   SessionActor.cs

   class MyPlayerSessionGameParams : PlayerSessionGameParamsBase { } 
   class MyPlayerSessionGameParams : PlayerSessionParamsBase { } 
   
   protected override PlayerSessionParamsBase GameCreatePlayerSessionParams(SessionStartParams sessionStart, SessionToken sessionToken) 
   protected override PlayerSessionGameParamsBase GameCreatePlayerSessionParams(SessionStartParams sessionStart, SessionToken sessionToken) 
   {
       return new MyPlayerSessionGameParams(
        sessionId:     _entityId, 
        sessionToken:  sessionToken, 
        deviceGuid:    sessionStart.Meta.DeviceGuid, 
        ... 
        myCustomParam: 123
       );
   }

Update Return Type of TryGetNextDueJob() in Custom DatabaseScanJobManagers

The return type of DatabaseScanJobManager.TryGetNextDueJob() has been changed from a tuple to a class due to new return values.

Migration Steps:

1. If you have custom DatabaseScanJobManager classes, change their TryGetNextDueJob() methods to return a DueJobInfo object, or null if no job is due. The previously required canStart parameter is now optional and is true by default.
   MyScanJob.cs

   public class MyScanJobManager : DatabaseScanJobManager
   {
       ...
   
       public override (DatabaseScanJobSpec jobSpec, bool canStart) TryGetNextDueJob(IContext context, MetaTime currentTime) 
       public override DueJobInfo TryGetNextDueJob(IContext context, MetaTime currentTime) 
       {
           DatabaseScanJobSpec dueJobSpec = ...
           bool canStart = ...
   
           if (dueJobSpec == null)
               return (null, false); 
               return null; 
   
           return (dueJobSpec, canStart); 
           return new DueJobInfo(dueJobSpec, canStart); 
           // Or if canStart is always true:
           return new DueJobInfo(dueJobSpec); 
       }
   }

Update PlayerActorBase.CreateSocialAuthenticationEntry Signature

To allow accessing user information of user's Social Account, CreateSocialAuthenticationEntry now contains IAuthenticationPlatformUserInfo parameter for platform-specific information.

Migration Steps:

1. If overriden, replace PlayerActor CreateSocialAuthenticationEntry(AuthenticationKey) with CreateSocialAuthenticationEntry(AuthenticationKey key, IAuthenticationPlatformUserInfo user)

2. If the overriden method uses PlayerAuthEntryBase.Default, pass the IAuthenticationPlatformUserInfo in PlayerAuthEntryBase.Default constructor.

3. If the overriden method uses custom PlayerAuthEntryBase, pass the IAuthenticationPlatformUserInfo to PlayerAuthEntryBase constructor.

Update Usage of PlayerEventPayloadBase and EventPayloadBase

PlayerEventPayloadBase and EventPayloadBase were moved from Metaplay.Server.AdminApi.AuditLog to Metaplay.Core.AuditLog.

Migration Steps:

1. Add using Metaplay.Core.AuditLog; to all files that reference PlayerEventPayloadBase or EventPayloadBase.

Update Calls to ModelUtil.RunAction()

ModelUtil.RunAction() no longer takes in IChecksumContext. The parameter was unused.

Migration Steps:

1. Replace all instances of ModelUtil.RunAction(model, action, context) with ModelUtil.RunAction(model, action), i.e. remove the last argument.

2. In case generic parameters are not inferred, replace ModelUtil.RunAction<TModel, TAction, TChecksumCtx>(model, action, context) with ModelUtil.RunAction<TModel, TAction>(model, action), i.e. remove the last generic argument and parameter.

Update Multiplayer Entity API Usage

In a multiplayer entity, _journal is no longer used or exposed. Multiplayer entity debugging configuration has been unified under MultiplayerEntityActorBase.DebugOptions.

Migration Steps:

1. Replace all null-checks of MultiplayerEntityActorBase._journal to target MultiplayerEntityActorBase.Model.

2. If MultiplayerEntityActorBase.DesyncDebugging was overriden with a custom value, override MultiplayerEntityActorBase.DebugOptions instead and choose a suitable checksum mode.

3. If MultiplayerEntityClientBase._enableJournalCheckpointing was mutated, remove it. Instead, override MultiplayerEntityActorBase.DebugOptions and set a suitable consistency check mode.

Update Custom ISessionCredentialsService Construction

The function IMetaplayConnection.GetSessionCredentialService() now gets the instance of the guest credentials store as parameter guestStore.

Migration Steps:

1. If your custom implementation of ISessionCredentialsService derives from UnityCredentialsService then pass on the guestStore parameter to the base class constructor.

2. Update your implementation of IMetaplayConnection.GetSessionCredentialService() to declare parameter CredentialsStore guestStore and pass it along to the constructor of the ISessionCredentialsService as appropriate.

Remove Uses of PlayerActionBase.Id

The field PlayerActionBase.Id was a client-generated incrementing integer. It has been removed as it was commonly useless, but at worst it lead to error-prone constructs. If your PlayerActions need an ID, the game client should generate and assign one itself.

Migration Steps:

1. Replace all uses of PlayerActionBase.Id with a new integer property in your Action.

   MyPlayerAction.cs

   public class MyPlayerAction : PlayerAction
   {
       public int TrackingId { get; set; } 

2. Assign the TrackingId of the value of a running counter, for example by incrementing a global variable.

   MyActionManager.cs

   public class MyActionManager
   {
       int _runningId; 
   
       public void PerformMyAction()
       {
           MyPlayerAction action = new MyPlayerAction();
           action.TrackingId = _runningId++; 
           PlayerClientContext.ExecuteAction(action);
       }