Start hereEveryone

Editing a config file

Open the file in any text editor, change a value, save. Here is how values are written and what happens if one is wrong.

The files are plain text in TOML, a simple key = value format. Open one in any text editor (Notepad, TextEdit, VS Code), change a value and save.

# fantasy-server.toml
[flight]
    # Highest Y a flying mount may climb to.
    # (Changed here from its default, 320.0.)
    maxAltitude = 256.0

Lines starting with # are notes the mod writes for you. The [flight] line starts a section: every key under it belongs to it.

How values are written

Kind Write it like Examples
On or off true or false enabled = false
Whole number digits odds = 8192
Number digits, with a decimal point if you like xpMultiplier = 2.0, chance = 0.5
One of a few words the word in quotes, as listed riderPermission = "TRUSTED"
Text in quotes theme = "fantasy:wildwood"
List in square brackets, each in quotes allowedDimensions = ["minecraft:overworld"]

Every setting’s page lists its kind, its default and the range it accepts.

If a value is wrong

  • Outside its range: the mod sets it to the nearest value it accepts.
  • Can’t be read (a typo, a missing quote): that setting goes back to its default.
  • A key the mod doesn’t know (misspelled, or from an older version): it is taken out of the file.

Each time it does one of these, the game writes a line in its log (logs/latest.log) and keeps a copy of your file as it was, named like fantasy-server-1.toml.bak, so nothing you typed is lost.

If the file as a whole can’t be read (a bracket or quote left open across lines), the game says so in its log, and your loader may write the file again with every setting at its default. Keep a copy before big edits, or use the Settings Workbench, which only ever writes lines the mod reads.

The line at the top

Each file starts with configVersion. Leave it as it is: the mod uses it to carry your values over when an update renames a setting or moves it within its file, and its log says what it carried over. A value that no longer fits a changed setting goes back to its default, and the log says so too.

Changing defaults in an update

When an update changes a default, files you already have usually keep the value they were written with (an update can move files still at the old default to the new one). To get the new defaults, delete the file (or the line) while the game is closed, and the mod writes it again when it starts.

↑ ↓ to moveEnter to openEsc to closeMounts and items: Encyclopedia →

Report a bug

Four quick steps. No GitHub account needed.

What kind of problem is it?

Pick the closest one. It decides what we ask next.

Bugs only. Have an idea instead? Trailblazers share theirs with the developer on Discord. Playing an early-access build? Post in #beta-feedback there.