FOR DATA-DRIVEN GAMES
Update without deploying
Turn spreadsheets into type-safe configs and push changes instantly—no app store review required.
Why use Metaplay for data-driven games?
Designer-friendly workflow
Author configs in Google Sheets or Excel—tools designers already know.
Type-safe C# classes generated from spreadsheet columns automatically.
Visual dashboard for reviewing, comparing, and publishing configs.
Instant updates
Push config changes over-the-air without app store review or client update.
Players receive new configs on their next session start.
Roll back changes instantly if something goes wrong.
Type-safe and validated
Compile-time checks catch typos and reference errors before they ship.
Config references are validated—broken links fail the build, not production.
Schema migrations handle evolving data structures safely.
Three ways Metaplay helps data-driven games work better
Faster iteration
Designers change a spreadsheet, build configs, and publish—players see updates in minutes. No code review, no deploy cycle, no app store wait.
Safe by default
Type-safe configs mean errors are caught at build time. Reference validation ensures you can't ship a level that references a deleted item.
Version everything
Config archives are versioned and immutable. See what changed between versions, compare configs, and roll back to any previous state.
Features for data-driven games
Game configs
Spreadsheet data compiled into type-safe C# classes automatically.
OTA updates
Push config changes instantly without app store review.
Localization
Multi-language content with the same config pipeline.
Logic versions
Support multiple client versions with config compatibility.
Config archives
Versioned, immutable packages with full change history.
Dashboard management
Visual tools for reviewing, comparing, and publishing configs.
Hot-reload dev
Instant config reload in Unity Editor for rapid iteration.
Experiment variants
A/B test different config values with built-in experiment system.
Schema migrations
Evolve data structures safely with automatic migrations.
It couldn't be easier to get started
Sign up
Sign up to Metaplay and install the Metaplay SDK. Try a sample project and familiarise yourself with our comprehensive support docs.
Start developing
Use our pre-built features to cover all the basics and start developing your game with complete control.
Scale and extend
Progressively develop more features and workflows as your game grows and never get held back by your tech.
My favorite part of working with Metaplay so far has been the ease of setting up game configs in the LiveOps dashboard, and getting granular, user-level insights to see how our players are progressing and the different issues they're facing.
Jijo Jackson
Game Lead at Nitro Games
Top frequently asked questions
Yes. App store policies allow updating game data and configuration over-the-air. You're changing balancing values, economy numbers, and content data—not executable code. This is standard practice for live service games.
Every config archive is versioned and stored. From the LiveOps Dashboard, you can view the history of published configs and instantly republish any previous version. Players will receive the rolled-back config on their next session.
When configs are built, the SDK validates all references between items. If you reference a deleted item or use an invalid ID, the build fails with a clear error. Type mismatches are caught at compile time. Broken configs never reach production.
Yes. Once the config pipeline is set up, designers can edit spreadsheets, trigger builds, and publish to production from the dashboard. Engineering defines the schema; designers iterate on the values.