Uploading Schemas to the Dashboard

The LiveOps Dashboard uses the uploaded configuration schema to render the module editor. Before you can configure values for a module, you must upload the generated schema file. You must re-upload whenever you add, rename, or remove configuration classes or properties.

Note

If you do not have access to the LiveOps Dashboard, contact your Tactile integration contact to upload the schema file on your behalf.

Uploading

1. Open the Configurations section for your game in the LiveOps Dashboard.
2. Upload the configuration-schema.json file to the appropriate configuration module.
3. Create a configuration module version and assign a version range that matches the game versions this schema is valid for.

Schema–version mismatch

You are responsible for ensuring the uploaded schema is valid for the game version the configuration targets. If the schema does not match the configuration classes in the game client, the client may fail to parse the configuration.

Configuration modules

In the Dashboard, configuration is organized into modules. Each module corresponds to a [Tactile.ConfigProvider] class in your code. When you upload a schema, each annotated class appears as a separate module that you can edit and publish independently.

Module versioning

Each module defines its own list of compatible version ranges. Different version ranges can have:

• Different configuration values (e.g. a feature enabled in 1.90.0+ but disabled in earlier versions)
• Different configuration schemas (e.g. a config class gains a new field in 1.30.0+)

When creating or updating a module version, you specify the version range it applies to. Game clients receive the configuration that matches their version.

Publishing

After configuring your module values, publish them to make them available to game clients. Published configuration is served by the Game Webservice and delivered to clients on their next Sync.

When to upload

Situation	Upload required?
New [ConfigProvider] class added	Yes
Existing module: new property added	Yes
Existing module: property removed	Yes
Existing module: property type changed	Yes
Module class renamed	Yes
Only configuration values changed (no schema change)	No — edit values directly in the Dashboard
[Description] text changed	No — descriptions are informational only

Deprecating modules

If a feature is removed from your game, you can mark its configuration module as deprecated in the Dashboard. This is informational only — the module remains available for older game versions that still use it.