Metaplay Docs

Appearance

metaplay database reset [ENVIRONMENT] [flags]

Reset database by dropping all tables

metaplay database reset [ENVIRONMENT] [flags] ​

Reset the database by dropping all tables in all shards. This operation is designed to handle database schema version mismatches and ensure a clean database state.

The reset process uses the following sequence:

  1. Mark reset in progress by setting MasterVersion to -4004
  2. Drop all tables except MetaInfo (preserves reset state)
  3. Drop MetaInfo tables in reverse shard order

This ensures the reset can be resumed if interrupted and maintains consistency.

WARNING: This operation is DESTRUCTIVE and will delete ALL data in the database. Use with extreme caution and only on development/staging environments.

Expected arguments:

  • ENVIRONMENT (optional) -- Target environment name or id, eg, 'lovely-wombats-build-nimbly'.

Examples ​

sh
# Reset database in nimbly environment (requires confirmation)
metaplay database reset nimbly
# Auto-accept reset without confirmation prompt
metaplay database reset nimbly --yes

Flags ​

  • --confirm-production: Required flag when resetting production environments
  • --force: Proceed with reset even if a game server is deployed (DANGEROUS!!)
  • --yes: Skip confirmation prompt and proceed with reset

Inherited Flags ​

  • --color <string>: Should the output be colored (yes/no/auto)? [env: METAPLAYCLI_COLOR] (default: auto)
  • --project <string>: Path to the to project directory (where metaplay-project.yaml is located)
  • --skip-version-check: Skip the check for a new CLI version being available
  • --verbose: Enable verbose logging, useful for troubleshooting [env: METAPLAYCLI_VERBOSE]