Schema Generation

The SDK includes a build processor that automatically generates a configuration-schema.json file every time you build your game. This schema describes every configuration module in your project and is what the LiveOps Dashboard uses to render the configuration editor.

What is generated

The configuration-schema.json file includes a JSON representation of every class decorated with [Tactile.ConfigProvider]. For example, given the following C# class:

[Tactile.ConfigProvider("AppTracking")]
public class AppTrackingConfig
{
    [Description("iOS version from which the App Tracker dialog should show.")]
    [JsonSerializable("EnableFromIOSVersion")]
    public string EnableFromIOSVersion { get; set; }
}

The generated schema will contain an AppTracking entry with a string field for EnableFromIOSVersion. This is what the Dashboard uses to render the editing UI for that module.

When it runs

The schema is generated automatically as a post-process step after every Unity build.

Exporting without a build

You can also export the schema on demand from the Unity Editor without performing a full build:

1. Open Tactile → Export → Configuration Schema from the menu bar.
2. The schema file is written to your project directory.

This is useful for quick iteration — you can verify your configuration classes are correct before committing to a full build.

What to do with the schema file

After generating the schema, upload it to the LiveOps Dashboard. See Uploading Schemas.