DeerFoliaPlus · Configuration overview
Docs/deerfoliaplus/DeerFoliaPlus · Configuration overview

DeerFoliaPlus · Configuration overview

Find DeerFoliaPlus configuration files, runtime data, and restart rules.

Configuration files and data

DeerFoliaPlus core settings live in config/:

File or directoryPurposeLoad boundary
config/deer-folia-plus.ymlFakePlayer, strongholds, protocols, recipe sync, posture, and utility switchesCore startup
config/custom-recipes.ymlCustom recipe definitionsLoaded when custom-recipe.enabled is true
worlds/world-name/fakeplayer.datList of saved fake playersWorld save loading
worlds/world-name/fakeplayerdata/NBT data for saved fake playersFake-player save or load
syncmatica/litematica/Uploaded Syncmatica schematic filesUsed when Syncmatica is enabled
syncmatica/temp/Temporary Syncmatica upload filesDuring Syncmatica transfers

Fake-player data follows the world save. It is not stored in plugins/. Syncmatica files live in the server-root syncmatica/ directory. Include this directory with worlds and configuration in backups.

How files are generated

The core creates config/deer-folia-plus.yml during the first configuration load. Java camelCase names become kebab-case keys. For example, amountPerPlayer becomes amount-per-player, and skipFabricOnViaNonNative becomes skip-fabric-on-via-non-native.

When custom-recipe.enabled is true, the core creates custom-recipes.yml under config/. The file has no active recipes by default. Add definitions under recipes. If parsing fails, start with the full log. Do not delete the file first.

  1. Stop the server. Wait for world saves.
  2. Back up config/deer-folia-plus.yml, config/custom-recipes.yml, world data, and syncmatica/.
  3. Change one feature group or one recipe.
  4. Check YAML indentation, quotes, lists, and namespaces.
  5. Start the test directory. Read the complete log.
  6. Test with real players, client components, and target worlds.
  7. Move the tested change to production.

Restart and client boundaries

deer-folia-plus.yml is loaded during core startup. Restart the server after changing it. Bukkit or Paper reload does not reload core configuration. Custom recipes are registered during server loading. Restart after edits and check the registered count.

Syncmatica, Servux, and Recipe Sync depend on the server switch, client support, and protocol compatibility. A server-side true value does not make the feature usable without the matching client component.

YAML notes

  • Use spaces. Never use tabs.
  • Write booleans as true or false. Do not quote them.
  • Quote messages, namespaces, and values that contain colons.
  • Use fully namespaced item IDs in custom recipes, such as minecraft:diamond.
  • Keep a recoverable copy before editing.
  • Restore the last known-good file when unknown keys or parsing errors appear.

Continue with DeerFoliaPlus configuration and Features and client protocols.