Skip to content
psyGamer edited this page Jan 25, 2025 · 1 revision

Studio provides various customization options to configure styling of TASes.
To unify styles for a single project, a .studioconfig.toml file will enforce certain styling rules.

.studioconfig.toml File

This file needs to be placed in the root of the project. The project root is determined based on certain heuristics, however using a Git repository is the most reliable way.
The contents of the file is written in TOML to adjust the following styling rules:

  • RoomLabelStartingIndex: Integer which indicates the first index for room labels. (values must be >= 0; defaults to 0)
  • RoomLabelIndexing: Mode which determines how room labels are indexed. (defaults to Studio preference)
    • Disabled: Disables any automatic room label indexing
    • CurrentFile: Only counts room labels in the current file towards indexing
    • IncludeReads: Also counts room labels in Read-commands towards indexing
  • ForceCorrectCommandCasing: Boolean to determine whether the correct casing should be enforced (defaults to false)
  • CommandArgumentSeparator: String which is used as the separator for command arguments. (defaults to Studio preference)

Tip

The Project File Formatter tool allows for applying the specified styling rules to all files in a project.

Example File

The following file is an example which can be used as a reference:

RoomLabelStartingIndex = 0
RoomLabelIndexing = "IncludeReads"

ForceCorrectCommandCasing = true
CommandArgumentSeparator = ","

Tooling Documentation

Celeste TAS

TASing Reference

General Gameplay Techniques

Mechanics and Engine Functionality

Entity Interactions

Community

Clone this wiki locally