Common problems
Fix ExyliaRewards when a reward cannot be claimed, a daily reset is at the wrong hour, votes pay nobody or the plugin does not start.
The usual causes, with the fix for each.
The plugin does not start#
ExyliaRewards needs ExyliaLib 1.570.1 or newer. The loader installs it, or stages a newer one, and asks for a restart: restart once more. If the console reports a licence error, send that line to support. See Installation.
A module answers that it is off#
Each module (rewards, AFK zones, votes, referrals, battle pass) is switched on in config.yml under modules. A change needs a restart. See Configuration.
"Your rewards are still loading"#
A player's claims are read from the database as they join, and a playtime reward also waits for their playtime. Until then nothing can be claimed. It lasts a moment; if it does not, check the database connection in ExyliaLib's database.yml. See Database.
A player cannot claim a reward#
- It is disabled. Open
/rewardsadmin, the reward, Status. - It is locked. The reward asks for a permission, a playtime range, a condition or another reward claimed first, and the list shows the reason. Change it under Requirements.
- It is used. The daily, weekly and monthly rewards wait for the next reset; a reward with a claim limit stops at it. Staff holding
exyliarewards.bypassskip both. - They lack
exyliarewards.use. Claiming needs it. See Permissions. - Two accounts from one address. With One per address on, only one account of a house claims it.
To test as a player, use /rewardsadmin give <player> <id> or /rewardsadmin reset <player> <id>.
Daily rewards reset at the wrong time#
Days start at clock.reset-hour in clock.timezone; an empty timezone is the server's. Set both in config.yml and run /rewardsadmin reload.
Votes arrive but nobody is paid#
Votes are paid to the player with that name when they are online, or on their next join. Check the name the vote site sends. Without NuVotifier (or Votifier), votes only arrive through /voteadmin fake <player>, and the console says so on start. See Votes.
The vote party paid rewards instead of sending a piñata#
A party set to PINATA or BOTH pays rewards when there is no enabled piñata or no enabled spawn point. The console says which.
A reward is missing, or I deleted the presets#
Rewards are rows in the database, not a file. /rewardsadmin presets adds every preset whose ID is free. See Installation.
A reward's placeholder shows the wrong value#
An ID that starts like another placeholder of the plugin (playtime, ready, freezes, afk_, votes_, referrals_, battlepass_) is answered by that placeholder. The preset playtime_1h rewards are in that case: give your reward an ID such as pt_1h. See Placeholders. Placeholders in other plugins also need PlaceholderAPI.
A player's inventory was full#
Nothing is lost. What does not fit is kept and handed over on their next join, and staff see it with /exylialib pendingrewards.
Players are paid twice on a network#
Not if every server's database.yml points at the same database. Turn on Redis too, so announcements and the vote party reach every server at once. See Network and data.
Something missing on this page? Tell us on Discord