AlphaQuestsHelpTroubleshooting

Troubleshooting

The problems server owners actually hit.

On this page

Check the server console first. Each card gives the symptom, the likely cause and the fix.

Startup

Console: AlphaQuests 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: Skipping bad quest <file>: …

Cause: A quest file has an invalid id, a duplicate id, or a broken task. The rest of the quests still load.
Fix: Read the reason after the colon and fix the file. See Writing quests.

A chain problem is logged

Cause: A quest lists a requires id that does not exist, or two quests require each other.
Fix: Correct the id or break the loop, then run /aquests reload.

Console: Reward failed '…'

Cause: For eco give, no Vault economy was available or the deposit was rejected. For other lines, the format was wrong, for example a missing player name or an unknown item.
Fix: Install Vault and an economy plugin, or fix the line. See Rewards. The rest of the rewards still run.

Money rewards look larger than written

A player cannot accept another quest

Cause: They reached their quest limit, which is 1 by default.
Fix: Let them finish or cancel one, or raise the limit with a alphaquests.limit.<rank> permission. See Quest limits.

A quest is locked or cannot be repeated yet

Cause: It lists quests under requires that are not completed, it is not repeatable, or its cooldown is running.
Fix: Check %alphaquests_cooldown_<quest>% and the quest file. Staff can use /aquests reset.

Progress does not count

Cause: The target does not match. Targets are exact material or entity names, and an explicit target never matches an event without one. The quest may also not be active for that player.
Fix: Check the spelling of the target against the Bukkit name, and that the quest was accepted.

Players are told their data is loading

Cause: They ran a command right after joining, before their profile was read.
Fix: Try again in a moment. If it persists, check the storage settings, and with MySQL the database address and login.

Changing the storage provider does nothing