Votifier

host, port and v2Token are read only at server start#

VotifierServer.start() is called once, on ServerStartedEvent: it reads host/port, opens the socket and stores v2Token in its own field. /votifier reload only clears the config cache — the already open socket stays on the old address, and V2 signature verification keeps using the old token. The comment in votifier.json warns about this too: enabled: false does not stop a listener that is already running either.

Only sections that are re-read on every use are picked up live via reload: sites, voteLinks, broadcastMessage and voteParty.

What to do: After changing host, port, v2Token or enabled, restart the whole server. Keep /votifier reload for rewards, links, the broadcast and vote party settings.

/votifier reload clears the cache of all the mod's configs, not just votifier.json#

The subcommand calls ConfigManager.getInstance().clearCache(), which clears the shared configCache entirely. This means that along with votifier.json, economy.json, kits.json, crates.json and all the others are re-read from disk — including unfinished edits you left in the editor.

What to do: Do not run /votifier reload while half-edited configs of other systems are on disk. If you only need Votifier, first save everything else in a consistent state.

Two independent switches, and they turn off different things#

modules.votifierEnabled in config.json is checked at command registration: with false the commands /vote, /votes, /voteparty, /togglevotebroadcast and /votifier do not appear in the tree at all — neither in completion nor in help.

votifier.enabled in votifier.json is checked separately, at listener start: the commands stay, but the TCP port is not opened. Side effect: voteParty.resetOnRestart is handled on the line after the listener start, so with Votifier disabled the party counter is not reset on restart even if the flag is true.

What to do: To remove the system from the game entirely — modules.votifierEnabled: false. To temporarily stop accepting votes while keeping commands and statistics — votifier.enabled: false plus a server restart.

Site matching is case-insensitive; the only fallback is "default"#

resolveSiteConfig() iterates the sites keys and compares them with the received serviceName via equalsIgnoreCase, so case in the site name does not matter. If there is no exact match, the default entry is used. If that is missing too (or there is no sites section at all), no reward is given, silently — no commands, no crate keys, no error message. The player's statistics and the vote party counter still increase.

What to do: Always keep a default entry in sites. Take the exact serviceName value from the voting site's panel, and test with /votifier testvote <serviceName> <name>.

Crate keys require the Crates module to be enabled#

The sites.<site>.keys block is processed only if ConfigManager.isCratesModuleEnabled(). With modules.cratesEnabled: false keys are silently not given, while the commands from sites.<site>.commands run as usual — the vote reward becomes partial without a single warning.

What to do: If crate keys are the main vote reward, check modules.cratesEnabled in config.json and make sure the balance grows: /crate keys <name>.

broadcastMessage understands more than the config comment says#

The text goes through RichTextFormatter.processTablistText(), so besides the declared {player} these work: the {site} substitution (the voting site name), & codes, gradients and rainbow, named colour tags and even {animation:name} tokens from animations.json. Hover/click markup, however, is stripped — you cannot put a clickable link in a vote announcement.

An empty broadcastMessage string disables the announcement entirely.

What to do: Style the announcement like tablist lines; keep the link to the voting site for /vote.

Statistics and the reward queue are tied to the name, not the UUID#

The votifier_stats and votifier_pending collections (in neoessentials/store/) are keyed by username.toLowerCase() — the name the voting site sent. Case does not matter, but a name change does: after renaming, /votes shows 0, and an already queued reward stays under the old name and is never delivered. The UUID is used here only for giving crate keys and for remembering the broadcast opt-out (votifier_broadcast_toggle).

What to do: When a player renames, move their records in neoessentials/store/votifier_stats.json and votifier_pending.json by hand on a stopped server.

From the console /votes and /votifier testvote substitute the name "Server"#

Without a player argument both commands use source.getTextName(). For the console that is the string "Server", so /votes from the console always shows "Server has 0 total vote(s).", and /votifier testvote default without a name counts a vote for the nonexistent player "Server": it increases the vote party counter, creates a statistics record under the key server and queues a reward (there is no such player online).

What to do: From the console always specify the name explicitly: /votes Steve, /votifier testvote default Steve.

Permission checks let non-players through#

/vote, /votes, /voteparty and /votifier are written as p == null || PermissionAPI.hasPermission(...): the console, a command block and a function always pass, regardless of the neoessentials.votifier.vote and neoessentials.votifier.admin nodes. /togglevotebroadcast requires both a player and neoessentials.votifier.togglebroadcast.

What to do: Remember that a command block with /votifier testvote gives a reward without any permissions — restrict access to command blocks with the usual Minecraft means.