FAQ

No. It re-reads config.yml, messages.yml, and the inventory layout files. Java is compiled once at server start — any change to the plugin's actual code requires a full server restart.

Yes — folia-supported: true is declared explicitly, and scheduling is written against Paper's region/entity schedulers rather than the legacy Bukkit scheduler specifically so it works correctly under Folia's threading model.

Expected — PvP graves only trigger on a direct melee hit (sword, axe, fist). Projectile kills, fire, lava, fall damage, and everything else always go through the normal grave-slot system (or fallback, if every slot is on cooldown). See Mechanics → What happens on death for the exact priority order.

Check whether the death happened in a world listed under world-settings.no-fallback-worlds — physical graves are deliberately suppressed there, and items just drop naturally instead once every slot is full. Also confirm fallback-grave.enabled is still true.

Vault (plus an economy plugin) isn't installed, or the config change hasn't been reloaded yet. Without Vault, claim_cost.type: money is silently ignored rather than erroring — the grave just stays free. See Integrations → Vault.

Double-check the basehead-<base64> string in grave-visual.display-item is copied completely and correctly — a truncated or malformed base64 value falls back to a default appearance rather than erroring loudly. See Integrations → Custom skull textures.

Run /agraves reload — hologram/visual changes apply immediately afterward, even retroactively to graves that already exist in the world. Also confirm the list under lines (or pvp-lines) isn't empty, which hides the hologram entirely by design.

The actual node is spelled alphagraves.graves.bybass3 (no "p") — see Permissions → A note on naming. Copy the exact string rather than typing it from memory.