AlphaGravesHelpTroubleshooting

Troubleshooting

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

On this page

Startup
Graves and claiming
Visuals
Permissions

Start with the server console. AlphaGraves logs a specific line for most of these problems. Each card gives the symptom, the likely cause and the fix.

Startup

Console: AlphaGraves 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: [Panel] Could not reach the panel

Cause: Your host blocks outgoing HTTPS, DNS fails, or the panel is down.
Fix: The plugin keeps running in this case, unless the server was already marked pending or blocked. Allow outgoing HTTPS to the panel address in panel.api-url.

Console: Migrating config from vN to vM or Moved messages.yml to lang/messages.yml

Cause: Normal after an update. The plugin added new config sections and moved your messages file.
Fix: Nothing to do. Do not edit config-version by hand.

Graves and claiming

A player died and got no grave at all

Cause: One of: the world is in world-settings.disabled-worlds; the death kept the inventory (keepInventory); or a physical grave was needed but the world is in no-fallback-worlds or fallback-grave.enabled is false, so the items dropped normally.
Fix: Check those settings. See Mechanics → What happens on death.

A player cannot claim a grave that costs money

Cause: They cannot afford it, Vault or an economy plugin is missing, or the withdrawal failed. All of these deny the claim.
Fix: Install Vault and an economy plugin, or change claim_cost.type. See Claim costs.

Player is told the grave's data cannot be read

Cause: The stored items could not be decoded, for example items from a plugin that was removed. The console logs Grave … cannot be decoded — data left untouched in playerdata/<uuid>.yml. Nothing was charged or deleted.
Fix: Restore the plugin or server version the items came from, then let the player claim again. Keep the file as it is until then.

Console: Grave … expired but cannot be decoded — kept on disk for an admin to recover

Cause: A physical grave ran out of time and its items are unreadable, so the plugin neither dropped nor deleted them.
Fix: Same as above. The record stays in playerdata/ until it can be read.

Console: Corrupted player data for <uuid>. Creating backup.

Cause: A player file failed to load. It was renamed to <uuid>.yml.corrupt-<timestamp> and the player got a fresh profile.
Fix: Open the renamed file, repair the YAML if you can, and copy the slots back. The original is never deleted.

Auto-claim does nothing

Cause: The player has not turned it on in /graves settings, or lacks alphagraves.graves.autoclaim.
Fix: Check the setting and the permission. The scan runs every check_interval_ticks (100 ticks by default). Items that do not fit in the inventory are dropped at the player's feet, with a chat message.

Visuals

The hologram or marker is not visible from a distance

Cause: They are only shown inside grave-visual.view-range-blocks (default 32) and grave-hologram.view-range-blocks (default 16).
Fix: Raise the values and run /agraves reload.

Console: Failed to apply skull texture

Cause: The basehead-<base64> value in grave-visual.display-item is truncated or malformed.
Fix: Paste the whole base64 string again. See Custom skull textures.

Console: Invalid sound name in config

Cause: A name under sounds: is not in the Bukkit Sound list for your Minecraft version.
Fix: Use a valid name, or none to turn the sound off.

Permissions

A rank slot does not unlock after granting "bypass3"

Cause: The node is spelled alphagraves.graves.bybass3, with "by", not "bypass".
Fix: Copy the exact node from Permissions.