AlphaGravesDocs v2.0.0
AlphaGravesStart hereInstallation

Installation

Get AlphaGraves running, and update it without losing a stored grave.

On this page

Requirements

WhatNeededNotes
Server softwarePaper or FoliaFolia support is declared in plugin.yml.
Minecraft1.21.1 or newerJars are built per Minecraft version, see Choose the right jar.
Java21 or 251.21.x servers use Java 21. 26.x servers use Java 25.
NetworkOutgoing HTTPSNeeded for server approval.
Vault, PlaceholderAPIOptionalSee Integrations.

Choose the right jar

Jars are built per Minecraft version, and the file name tells you which one:

AlphaGraves-<version>-mc-<minecraft>-java<java>.jar

AlphaGraves-2.0.0-mc-1.21.1-java21.jar
AlphaGraves-2.0.0-mc-26.2-java25.jar

Use the jar whose mc- part matches your server. A jar built for 26.x is compiled for Java 25 and will not load on Java 21.

Install

  1. Stop the server and put the jar in plugins/.
  2. Start it. The plugin creates plugins/AlphaGraves/ with config.yml, lang/messages.yml and the inventories/ layouts.
  3. Get approved. A new server is pending and the plugin stays off. The console prints your server id. Send it to AlphaStudio, wait for the approval, and restart. Details on Server approval.
  4. Check it. Run /agraves menu in game.

Update

  1. Back up plugins/AlphaGraves/. playerdata/ holds every stored grave.
  2. Replace the jar with the new one and restart. /agraves reload never loads a new jar.
  3. Let it migrate. On first start the plugin adds missing config sections, and moves an old messages.yml into lang/ keeping your edits. The console says when it does.
Upgrading from 1.x: license keys no longer exist. 2.0.0 asks the AlphaStudio panel for approval instead, and a server that has not been approved yet will not run the plugin. See Server approval before you update a live server.

Folia

AlphaGraves declares folia-supported: true. It uses the entity and region schedulers, including for auto-claim, so each player's items are handled on that player's own region thread.