AlphaRewardsHelpTroubleshooting

Troubleshooting

The problems server owners actually hit, matched to the console line or symptom you will see.

On this page

Startup
Rewards
Menus
Player data

Check the server console first. AlphaRewards logs a specific line for most of these problems. Each card gives the symptom, the likely cause and the fix.

Startup

Console: AlphaRewards is disabled — this server is waiting for approval.

Cause: A new server starts as pending, and the plugin stays off until AlphaStudio approves it.
Fix: Send the server id from the next console line to AlphaStudio, then restart once it is approved. See Server approval.

Console: Invalid reward-mode: X, defaulting to DAILY

Cause: reward-mode is not DAILY or STREAK. Any other value falls back to DAILY, even though the shipped default is STREAK.
Fix: Correct the value in config.yml and run /alpharewards reload.

Console: Failed to load menu config: <file>

Cause: A file under menus/ has a YAML error. The stack trace under the line shows which line.
Fix: Fix the indentation or quoting and reload. On success the console prints Loaded N menu configurations.

Rewards

The reward is claimed but the money never arrives

Cause: Money is paid by a console command (the shipped files use money give {player} …). If nothing on your server answers that command, nothing is paid.
Fix: Use your economy plugin's command in every day and tier. See Shipped reward pack.

A VIP player got the default reward, or the wrong tier

Cause: The player lacks the tier permission, or the tiers are in the wrong order in the menu file. The last matching tier wins.
Fix: List tiers lowest to highest. See Tier order.

A player cannot claim even though a reward shows as available

Cause: Another plugin cancelled the claim through AlphaRewardPreClaimEvent. A cancelled claim returns without any message.
Fix: Check for plugins that hook the event. See Developer API.

A streak broke although the player logged in every day

Cause: Days roll over at midnight in the server's own time zone, for every player. A player in another time zone can cross that line without noticing. The grace period only covers a claim made up to grace-period-hours into the second day after the last one.
Fix: Raise streak.grace-period-hours, or set streak.reset-on-miss: false if streaks should never break.

Console: Invalid date format in player data

Cause: A player file in playerdata/ has a date that is not yyyy-MM-dd, so the plugin skips the streak check for that player.
Fix: Edit the date in that player's file, or run /alpharewards reset <player> while they are online.

Menus

Pages look wrong, or some reward slots are empty

Cause: rewards-per-page in config.yml does not equal the number of reward-slots in the menu file.
Fix: Make them the same number. The shipped files use 4 slots per page.

Console: [AlphaRewards] Failed to apply skull texture

Cause: A basehead-<base64> material is truncated or malformed.
Fix: Paste the whole base64 value again.

Player data

Console: Failed to load data for <uuid> or Failed to save data for <uuid>

Cause: The player's file in playerdata/ is unreadable or the folder is not writable.
Fix: Check folder permissions and free disk space. Do not delete the file: it holds that player's progress.

Console: Player data writes are still running after 30 seconds

Cause: On shutdown the plugin waits up to 30 seconds for pending saves, and the disk was too slow.
Fix: Check the disk. Progress made just before the stop may not have been saved.

Gold or yellow text shows up in the accent colour

Cause: Legacy &e and &6 codes are remapped to colors.accent on purpose.
Fix: Set the colour you want in colors.accent, or write hex codes directly.