AlphaTPAStart hereInstallation

Installation

Get AlphaTPA running, and update it without losing player settings.

On this page

Requirements
Choose the right jar
Install
Update

Requirements

What	Needed	Notes
Server software	Paper or Folia	Folia support is declared. Countdowns tick on the traveller's own thread and the teleport is asynchronous.
Minecraft	1.21.1 or newer	Jars are built per Minecraft version, see Choose the right jar.
Java	21 or 25	1.21.x servers use Java 21. 26.x servers use Java 25.
Network	Outgoing HTTPS	Needed for server approval.
PlaceholderAPI, CMI, EssentialsX	Optional	See Requirements.

Choose the right jar

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

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

AlphaTPA-2.0.0-mc-1.21.1-java21.jar
AlphaTPA-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

Stop the server and put the jar in plugins/.
Start it. The plugin creates plugins/AlphaTPA/ with config.yml, lang/ and menus/players/.
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.
Try it. Run /tpa with a second player.

Update

Back up plugins/AlphaTPA/. data/players.yml holds every player's switches.
Replace the jar and restart. /alphatpa reload never loads a new jar.
Check the console. If a bundled menu or message file has a higher file-version, it replaces yours and your old copy is kept as *.old. The console warns when that happens.

Upgrading from 1.x: license keys no longer exist. 2.0.0 needs the server to be approved in the AlphaStudio panel, and an unapproved server will not run the plugin. Read Server approval before updating a live server.