Config reference: feather.yml

FeatherMC’s own options live in feather.yml in the server root, separate from Paper’s config/ folder. The file is created with every option and its comment on first start. It is read once at startup, so restart to apply changes.

Experimental

The TNT guard and the anti-cheat check are new and have not been tested in a real game yet. Both are off by default.

anti-lag-machine

Guards against mass-TNT “orbital strike” detonations. More checks may be added here later.

Key	Type	Default	Description
enabled	boolean	false	When true, a dense cluster of primed TNT is deleted just before it explodes instead of detonating. Only TNT inside the radius is removed.
threshold	int	100	How many primed TNT within the radius counts as a mass detonation. TNT use below this is unaffected.
radius	double	8.0	Radius in blocks checked around a TNT that is about to explode.

Per-chunk projectile save limits are a separate Paper setting that FeatherMC turns on by default. See Changed Paper defaults.

anti-cheat.autoclicker

A basic, best-effort check that flags players attacking faster than a set number of clicks per second. It is not a replacement for a dedicated anti-cheat. For serious protection use a plugin such as Grim or Vulcan, which run on FeatherMC.

Key	Type	Default	Description
enabled	boolean	false	Turns the attack-rate check on.
max-cps	int	24	Most attack clicks per second before a player is flagged. Keep it generous, because fast legitimate clickers can reach about 20 and lower values risk false positives.
action	string	LOG	What happens when a player is flagged. See below. Any other value falls back to LOG.

The action values:

• LOG writes a warning to the console and changes nothing for the player.
• CANCEL ignores the attacks over the limit.
• KICK disconnects the player.

sentry

Optional error reporting. When a DSN is set, logged errors that carry a stack trace are sent to your Sentry project, so you can see which plugin broke. Gameplay is unaffected.

Key	Type	Default	Description
dsn	string	empty	Your Sentry DSN. Leave it empty to keep error reporting off.

auto-update

Optional automatic updates, off by default. When enabled, FeatherMC checks the configured repository’s latest matching GitHub Release at startup and, if a newer build exists, downloads its jar into update/ over HTTPS and (optionally) relaunches to apply it. It only ever pulls from the repository below, and it never downgrades.

Key	Type	Default	Description
enabled	boolean	false	Master switch for auto-update.
repository	string	1chenyip/FeatherMC	The GitHub owner/repo whose Releases hold the jars. Each release’s tag is a version.
version	string	latest	Which version to track. latest is the newest build of the newest Minecraft version. A version line such as 26.3 is the newest build within that line only (e.g. 26.3, 26.3.1), so it never jumps to a new Minecraft version. An invalid value, or a version with no matching release, logs an error and stops the server.
restart	boolean	true	When a newer build is downloaded, relaunch to apply it. When false, the jar is left in update/ to apply on the next start.

Note

Applying an update needs FeatherMC’s start.sh / start.bat: on exit code 70 they move update/feather-release.jar onto the server jar and relaunch, while a normal /stop ends the loop. Build numbers come from the commit count, so each release’s version increases and the updater can tell builds apart.

Caution

Auto-update downloads and runs a new server jar automatically. Only enable it if you trust the configured repository; it pulls over HTTPS from there and nowhere else.

Generated file

feather.yml (as generated)

anti-lag-machine:
  enabled: false
  threshold: 100
  radius: 8.0
anti-cheat:
  autoclicker:
    enabled: false
    max-cps: 24
    action: LOG
sentry:
  dsn: ''
auto-update:
  enabled: false
  repository: '1chenyip/FeatherMC'
  version: latest
  restart: true