Appearance
Appearance
New maintenance mode feature. You can use the LiveOps Dashboard to schedule controlled backend downtime. Use maintenance mode to safely tell clients to disconnect from the deployment and prevent new connections.
Documentation for handling maintenance mode in your game client code can be found in Handling Maintenance Mode In Your Game UI
User-land logging and metrics tooling for game server deployments on shared platform.
Game server support for structured logs.
Checksum computations optimized to be about 10x faster on the server.
Fixed critical bug in persisting objects to database: any byte[] were truncated to 65535 bytes due to MySQL default limit for its BLOB data type. Now, byte[] defaults to LONGBLOB, which supports up to 4GB.
INFO
No actions needed: Migration has been taken care of by Metaplay.
byte[]
requires creating a Entity Framework Core migration step dotnet ef migrations add LongBlob
in your project's Game.Server
directoryAWSConfig.json
is split into multiple files Split the file into Config.base.json
(shared for all deployments) and Config.<env>.json
for environment-specific overrides.
Ensure that the proper config file(s) are configured in the values.yaml
of the project's metaplay-gameserver
Helm chart, e.g.:
config:
files:
- "./Config/Config.base.json"
- "./Config/Config.dev.json"
Config/Config.base.json
(for common configs) and Config/Config.{env}.json
(for env-specific configs)