TDX VotePlus
Troubleshooting
Symptom-first answers for the bugs that actually come up in production.
This page is organised by symptom, not feature. Find the entry that matches what you are seeing and follow the steps. If none fit, open a thread in the TDX Discord.
The tools you have
| Tool | What it tells you |
|---|---|
/voteplus give <player> | Sends a test vote through the whole pipeline without any vote site. If this pays out, VotePlus is fine and the problem is between the site and your Votifier. |
/voteplus offline [player] | Shows the offline vote queue, overall or for one player. |
/voteplus debug | Shows how much is waiting to be saved and how many players are cached. |
general.debug: true in config.yml | After /voteplus reload, every step of every vote is logged. Switch it off again afterwards, it is chatty. |
Two lines are logged for every vote even with debug off, and they answer most questions on their own:
[TDXVotePlus] [VotifierHook] Received vote: user='Steve' service='TopG' address='1.2.3.4'
[TDXVotePlus] [VoteService] Queued offline vote for Steve (uuid=...) from service='TopG' into table=offline_queueThe first appears for every vote VotePlus hears about. The second appears when that player was offline.
Common symptoms
Still stuck? Post in #voteplus-support on the
TDX Discord with the output of
/version TDXVotePlus, your Votifier plugin and version, and the
console lines around a test vote with general.debug switched on.