TDXDevelopment
TDX VotePlusConfiguration

Overview

One YAML per subsystem, what each file does and where to look first.

TDX VotePlus splits its configuration across one file per subsystem. Each file is small and self-contained, so you can tune milestones without scrolling past 400 lines of unrelated YAML.

config.yml
vote-rewards.yml
vote-sites.yml
leaderboard.yml
monthly-rewards.yml
milestones.yml
vote-party.yml
reminders.yml
effects.yml
discord.yml
messages.yml

Every bundled file is heavily commented. If something on these pages disagrees with a comment in the file you are editing, trust the file and tell us, because the page is wrong.

Where to look

Automatic updates of your files

config.yml and the nine feature files each carry a config-version number. When a plugin update ships a newer version of a file, the keys you are missing are added to your copy and a timestamped backup is written next to it first, for example vote-rewards.yml.backup-20260411-183005. Values you have set are never changed.

messages.yml and the files in guis/ are not rewritten. A message key missing from your messages.yml falls back to the bundled default text, and a menu file that does not exist is created from the bundled one.

Reload vs restart

  • /voteplus reload applies everything in the feature files, messages.yml and guis/, and general.debug, general.timezone and general.auto-claim-offline from config.yml.
  • A restart is needed for general.storage and everything under mysql, because the database connection is only opened at startup, and for metrics.enabled.