For failures spanning listener, storage, proxy forwarding, and rewards, use Advanced Troubleshooting.
/vote says “vote here: www.votelinkhere.com”This is usually VentureChat intercepting /vote. Remove or change VentureChat's /vote alias, restart or reload VentureChat, and test again.
Put the crate plugin's give-key command in the reward's Commands list:
Rewards:
Commands:
- "command here %player%"
Examples, which must be adjusted to match the crate plugin's current command syntax:
Rewards:
Commands:
- "cc give physical <CrateName> 1 %player%"
- "cmi give %player% key:<KeyName> 1"
- "crate givekey %player% <CrateName> 1"
%player% is replaced with the voter's name.
/av vote <player> <site>
Validate the file with a YAML parser and check that:
Example:
Messages:
Player: '&aThanks for voting!'
Either the vote listener is not receiving the vote or ServiceSite does not exactly match the value sent by the vote service.
Run a test vote, check the console, and follow Votifier Troubleshooting.
Redownload the jar. It is probably corrupted or is not the correct server plugin artifact.
DebugLevel: EXTRA
For proxy issues, also enable BungeeDebug in BungeeSettings.yml and debug output on the proxy.
Use:
&#FF0000#
The hexadecimal color is surrounded by &# and #.
/av reload
/av reloadall
/av reloadall also reloads user storage.
First determine whether the failure is Java heap exhaustion or a container PID limit. A PID-limit problem is normally visible in Wings, Docker, or host logs and is different from insufficient Java memory.
Only a Pterodactyl node administrator should change the host-wide setting. When logs confirm PID exhaustion, the node administrator can review container_pid_limit in /etc/pterodactyl/config.yml and restart the required node services after making an appropriate change.
Do not increase a node-wide process limit as a substitute for diagnosing Java heap usage, runaway processes, or plugin errors.