AlphaPracticeDocs v8.0.0
AlphaPracticeStart hereInstallation

Installation

Get AlphaPractice running. PacketEvents is required and must be installed separately.

On this page

Requirements

WhatNeededNotes
Server softwarePaper or a Paper forkThe default build targets Paper 1.21.11.
Minecraft1.21.11 or newerBuilds exist for 1.21.11, 26.1.2 and 26.2.
Java21 or 251.21.x servers use Java 21. 26.x servers use Java 25.
PacketEventsRequiredAn external plugin, loaded before AlphaPractice.
NetworkOutgoing HTTPSNeeded for server approval.

Choose the right jar

AlphaPractice-<version>-mc-<minecraft>-java<java>.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 PacketEvents

  1. Download a compatible PacketEvents build from its releases page.
  2. Stop the server and place both PacketEvents and AlphaPractice in plugins/.
  3. Start the server and check that PacketEvents loads before AlphaPractice. AlphaPractice declares it as a hard dependency, so the plugin will not start without it.
Do not shade PacketEvents into the jar. Keeping it external keeps the load order and compatibility correct.

Install

  1. Stop the server and put both jars in plugins/.
  2. Start it. The plugin creates plugins/AlphaPractice/ with config.yml, divisions.yml, ladders/, lang/ and menus/.
  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 approval and restart. See Server approval.
  4. Build arenas. See Arenas and ladders.

Update

  1. Back up plugins/AlphaPractice/, and your database if you use MySQL.
  2. Replace the jar and restart.
  3. Review the templates. config.yml carries a VERSION number. Upgrades keep your custom keys, including shop entries. Legacy text and menu files at the root are copied into lang/ and menus/ when the new location has none, and the originals are left in place.