TDXDevelopment
TDX VotePlusConfiguration

general

The general block in config.yml, debug, storage type, timezone, offline auto-claim, plus the bStats switch.

The general block in config.yml holds the switches that do not belong to any single subsystem.

plugins/TDXVotePlus/config.yml
general:
  debug: false
  storage: sqlite
  timezone: UTC
  auto-claim-offline: true

metrics:
  enabled: true

Reference

KeyTypeDefaultNotes
general.debugbooleanfalseLogs every step of the vote pipeline to console. Turn it on when a vote or a reward is not arriving, then off again.
general.storagestringsqlitesqlite or mysql. See the storage page. Needs a restart.
general.timezonestringUTCA Java zone id such as Europe/London or America/New_York. Decides when the day, the week and the month roll over.
general.auto-claim-offlinebooleantruetrue pays queued offline votes the moment the player joins. false holds them until the player runs /vote claim.
metrics.enabledbooleantrueAnonymous bStats metrics. No vote data and no player names are sent. Needs a restart.

There is also a config-version line at the top of the file. Leave it alone, the plugin uses it to add new keys to your file after an update.

Set timezone to where your community lives, not where your host is. Daily counters, streak days, the weekly board and the monthly payout all roll over at midnight in this zone. An id the JVM does not know falls back to the system timezone without an error, so check the spelling.

auto-claim-offline and the offline queue

This key works together with offline-queue.enabled in vote-rewards.yml:

offline-queue.enabledauto-claim-offlineWhat a returning player sees
truetrueQueued votes are paid on join, with one summary line.
truefalseA reminder that votes are waiting. They collect with /vote claim.
falseeitherNothing is queued. A vote for an offline player still counts (totals, streak, vote party), but the player gets no rewards for it.