Powered by NovaDocs
Welcome to NovaDocsStart with Installation → Install with Docker, or switch language to Polish (PL).

Config playground

Admin6 min readUpdated Aug 27, 2026

Config playground

The config playground is an optional add-on (sold / downloaded separately from the main NovaDocs package). It is not included in the base product.

Readers stay on the docs page: they tick options, paste a broken file, or fill in command arguments, then copy the result. This demo site has the add-on enabled so the blocks below work.

Live examples

These are the same three blocks that used to sit on Feature overview.

Config builder

Tick the options, then copy the file. Try a preset, then Reset. Comments in the YAML stay put.

config.yml

Turn everything off without uninstalling.

Blocks around spawn.

1# Core settings2enabled: true3max-players: 204difficulty: normal5 6spawn:7  protection: true8  radius: 169 10# Tuning11debug: false12save-interval: 300
Default configuration

Config checker

Copy the broken example into the box to see the errors:

yaml
enabled: yes
max-plyers: 20
difficulty: normal
Check your config.yml

Command builder

Fill the fields. The copy button stays disabled until the required ones are set.

Give an item
/give {player} {item} 1
Fill in: Player, Item

What it adds

  • Config builder — controls above a live config.yml (or JSON / .properties). Changed lines are highlighted. Comments and key order in your original file stay intact. Copy or download the finished file. Optional presets set several options at once.
  • Config checker — a paste box. Readers drop in their file and get line-numbered errors, plus “did you mean…?” for misspelled keys.
  • Command builder — fields that assemble a copyable command, so nobody has to guess argument order.

Who it is for

Plugin, theme, and game-server docs — anywhere readers are supposed to edit a config file or run a console command. Broken configs are usually the biggest support load; this answers them on the page instead of in a DM.

How authors use it

In the editor, type / and insert Config builder, Config checker, or Command builder.

  1. Paste your real config (or command template) once.
  2. Press Detect options / Detect arguments to create a control for every value.
  3. Optionally add labels, help text, hide advanced keys, and name presets.

YAML, JSON, and .properties files are supported. Nested keys (like spawn.radius) keep their indentation when the reader changes them.

tip

Paste the file you actually ship. The builder edits values in place and leaves every comment alone — including the ones on the same line as a key.

Was this helpful?