Config YML: Runtime Defaults and Save Policy

config.yml is where Duck Blocks decides how the whole server should behave before any one builder creates an individual machine.

If duckblocks.yml is the content library, config.yml is the ruleset that shapes the default feel of that library.

What belongs in config.yml

The most important global surfaces are:

• save behavior
• default clickbox sizes
• default execution mode
• default cooldown and one-time scope behavior
• animation service cadence
• move-tool behavior
• help-message style
• message wording and permission expectations

Example global layout

require-use-permission: false
save-state-on-shutdown: true
auto-save-interval-seconds: 120
 
default-clickbox:
  block: 0.5
  stand: 0.9
  interaction:
    width: 1.4
    height: 1.4
 
default-exec-mode: CONSOLE
default-cooldown-scope: PER_PLAYER
default-onetime-scope: PER_PLAYER
default-render-mode: NONE
 
animations:
  enabled: true
  tick-interval-ticks: 1
  nearby-check-interval-ticks: 10
  default-nearby-range: 24.0
 
move-tool:
  inject-hotbar-tools: true
 
help:
  use-components: true

Save policy

These settings decide how safe live edits are:

• save-state-on-shutdown
• auto-save-interval-seconds

Use shorter intervals if builders are making frequent live changes. Use longer intervals only if you are confident in the server environment and do not want unnecessary disk churn.

Default clickboxes

This is one of the most important quality-of-life sections for builders.

It decides the starting size of:

• block triggers
• armor-stand triggers
• interaction hitboxes

If your server favors large adventure-map buttons, kiosk props, or oversized interaction panels, raise the defaults. If you prefer tight, precise use points, keep them smaller.

Default execution behavior

These settings shape new triggers before the builder edits them:

• default-exec-mode
• default-cooldown-scope
• default-onetime-scope
• default-render-mode

Good guidance:

• keep CONSOLE as the default if most machines need server authority
• keep per-player cooldowns if interactive props should feel fair to each user
• keep NONE as the render default only if your builders mostly add visuals manually

Animation cadence

The animation block controls how hard Duck Blocks works in the background.

Important settings:

• enabled
• tick-interval-ticks
• nearby-check-interval-ticks
• default-nearby-range

If your server has many decorative props, nearby-only animation is one of the best ways to keep the world feeling alive without paying the full cost everywhere at once.

Move-tool and help behavior

Two smaller sections matter a lot in live editing:

• move-tool.inject-hotbar-tools
• help.use-components

The first changes how smooth the in-world edit flow feels. The second changes how readable the help surface is for builders using the command system.

When to change config.yml

Change config.yml when you want to alter:

• the starting defaults for all future DuckBlocks
• the runtime service cadence
• the safety and save policy of the whole plugin

Do not use it when you only want to change one individual machine. That belongs in the trigger editor and then in duckblocks.yml.

Best next pages

• main Menu, Create Flow, and the Help Command
• duckblocks YML: Trigger Layout and Live Examples
• admin Runtime, State, and Live Troubleshooting