Start hereEveryone

Where the files are

Your own settings sit in your config folder; a world's rules sit with the world, or in config on NeoForge 26.3 and newer.

The mod writes its files the first time it needs them, with every setting at its default and a note above each one. If a file isn’t there yet, start the game (or the world) once.

Your own settings

fantasy-client.toml is always in the game’s config folder, on every loader and version:

.minecraft/config/fantasy-client.toml

With a launcher such as CurseForge, Modrinth or Prism, each profile (instance) has its own config folder. Most launchers have an Open folder button for it.

A world’s or a server’s rules

fantasy-server.toml, fantasy-balance.toml and fantasy-skills.toml belong to the world they run in. Where they live depends on the loader:

Loader Where the three files are
Forge, Fabric and Quilt The world’s serverconfig folder
NeoForge up to 26.2 The world’s serverconfig folder
NeoForge 26.3 and newer The game’s config folder, one set for every world

So on a dedicated server they are in world/serverconfig/ (or config/ on NeoForge 26.3 and newer), and in single player in saves/<your world>/serverconfig/.

On NeoForge 26.3 and newer, one world can still have rules of its own: copy a file into that world’s syncedconfig folder (saves/<your world>/syncedconfig/) and it is used instead of the one in config.

Files for new worlds

To start every new world with your rules, put your copies in the game’s defaultconfigs folder (next to config). When a world’s file is made for the first time, the copy in defaultconfigs is used. This is how modpacks ship their settings: see Ship your settings in a modpack.

Which copy wins

  • Single player, or hosting on LAN: your world’s files decide.
  • On someone else’s server: the server’s files decide the rules, balance and skills, whatever your own copies say. Your fantasy-client.toml is still yours. See How server settings reach players.
↑ ↓ 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.