Config files

Where the rules are saved on Fabric and on Bukkit, and what the files look like.

The chest menu and the Commands save to these files. You can also change a file by hand and run /vspolicy reload.

Fabric #

config/voxelsprout-policy.jsonJSON

{
  "buildprint": {
    "features": { "easy_place": true, "printer": false, "free_camera": true },
    "limits": { "printer_speed": 0, "printer_range": 0, "paste_max": 0 }
  },
  "sorted": {
    "features": { "quick_stack": true, "find_items": false },
    "limits": { "clicks_per_tick": 4 }
  },
  "message": "The printer is off to keep the economy fair."
}

true means allowed. In limits, 0 means no cap.
The file is written back in full, so every rule shows up in it after the first start.
If the file can't be read, the server logs the error and allows everything until it is fixed.

Bukkit #

plugins/VoxelSproutPolicy/config.yml has the same settings, with a comment above each one saying what it does.

plugins/VoxelSproutPolicy/config.yml, shortenedYAML

buildprint:
  features:
    easy_place: true
    printer: false
    # ...
  limits:
    printer_speed: 0
    printer_range: 0
    paste_max: 0

sorted:
  features:
    quick_stack: true
    find_items: false
    # ...
  limits:
    clicks_per_tick: 4

message: "The printer is off to keep the economy fair."

From BuildPrint Policy #

An old config/buildprint-policy.json or plugins/BuildprintPolicy/config.yml is read on the first start, becomes BuildPrint's part of the new file, and is renamed to end in .moved. See Moving from BuildPrint Policy.

Something missing or wrong on this page? Say so on Discord.