Compatibility
Minecraft: Java Edition
Platforms
Tags
Creators
Details
Teleport requests, refined.
A polished, safety-aware
/tpaexperience for modern Paper and Folia servers - simple for players, powerful for server owners.
NexTPA replaces clumsy teleport commands with a clean request flow that feels native to your server. Players send a request, choose from clickable chat actions, and teleport with a configurable delay, effects, and protection. Everything important is ready from the first launch; everything else is yours to customise.
Built for a better player experience
- One clean flow —
/tpaand/tpaherewith clickable Accept and Deny buttons directly in chat. - Clear request control — review every pending request with
/tpalist, then accept or deny exactly the player you choose. - Updates without surprises — an optional, one-time Modrinth check tells administrators when a compatible stable release is available.
- Respect player choice — players can pause incoming requests or block individual players at any time.
- No awkward teleports — configurable delay, movement and damage cancellation, action bar countdown, and particles.
- Safety when it matters — warn about, or prevent, teleports near the void, dangerous falls, lava, or hostile mobs.
- Made for busy servers — request expiry, cooldowns, and queue limits keep chat and gameplay under control.
Made for modern servers
NexTPA is designed for both Paper and Folia. Teleport timers, request expiry, player messages, and request queues are scheduled safely for Folia's multi-region architecture while remaining seamless on Paper.
| Platform | Supported Minecraft versions | Required server Java |
|---|---|---|
| Paper | 1.21–26.3 | Java 21 for 1.21–1.21.11; Java 25 for 26.1–26.3 |
| Folia | 1.21–26.3 | Java 21 for 1.21–1.21.11; Java 25 for 26.1–26.3 |
Spigot, Bukkit, and proxy platforms are not supported.
Install in seconds
- Download the latest NexTPA JAR.
- Place it in your server's
pluginsfolder. - Restart the server.
- Edit
plugins/NexTPA/config.ymlandmessages.ymlonly if you want to customise the experience. - Use
/tpa reloadafter changing either file.
Existing config.yml, messages.yml, and data.yml files are compatible
with updates from NexTPA 1.0 and later.
Commands and permissions
| Command / feature | What it does | Permission |
|---|---|---|
/tpa <player> |
Request to teleport to a player | nextpa.tpa |
/tpahere <player> |
Request that a player teleports to you | nextpa.tpahere |
/tpaccept [player] |
Accept a specific request, or your oldest pending request | nextpa.accept |
/tpdeny [player] |
Deny a specific request, or your oldest pending request | nextpa.deny |
/tpalist |
View pending requests with time remaining and clickable actions | nextpa.list |
/tpacancel [player] |
Cancel an outgoing request | nextpa.tpa |
/tpatoggle |
Enable or disable incoming requests | nextpa.tpa |
/tpablock <player> |
Block or unblock a player's requests | nextpa.tpa |
/tpa reload |
Reload NexTPA settings and stored data | nextpa.admin |
| Update notifications | Receives a notice when a compatible NexTPA update is available | nextpa.update (default: OP) |
Player permissions are enabled by default. nextpa.admin and nextpa.update
default to server operators. Grant nextpa.update to non-OP staff if they
should also receive update notifications.
Configure the details, keep the simplicity
The default configuration is balanced for survival gameplay. Change only what your server needs:
| Setting | Default | Purpose |
|---|---|---|
cooldown-seconds |
15 |
Wait time between successful requests |
request-expire-seconds |
60 |
Time before a request expires |
limits.max-outgoing |
3 |
Maximum active outgoing requests per player |
limits.max-incoming-queue |
5 |
Maximum pending requests per player |
teleport.delay-seconds |
3 |
Delay before teleporting; use 0 for instant teleports |
safety.enabled |
true |
Enables destination safety checks |
update-checker.enabled |
true |
Enables one Modrinth check after startup |
Every player-facing message, button, hover text, colour, prefix, action bar,
and particle effect is configurable. NexTPA supports both legacy & formatting
and hex colours such as ὀff.
Built-in Modrinth update checker
NexTPA already knows its official Modrinth project, so there is no slug, project ID, or URL to configure. The checker is enabled by default; disable it with:
update-checker:
enabled: false
It checks Modrinth once after startup, only reports a newer stable version that
matches the active Minecraft version and Paper/Folia platform, and never
downloads or installs files. The console is notified, and players with
nextpa.update receive one notification per available version during each login
session. Set enabled to
false to make no outbound Modrinth request.
For each Modrinth release, use a SemVer version_number such as 1.4.1 and
tag the exact supported Minecraft versions plus the appropriate paper and
folia loaders. The checker intentionally ignores releases that do not match
the running server.
Anonymous usage metrics
NexTPA includes bStats project 34625 to understand aggregate server adoption
and supported-version usage. It uses only bStats' standard metrics and adds no
custom charts or NexTPA-specific telemetry. NexTPA does not submit player names,
player UUIDs, chat, worlds, configuration values, server addresses, or other
identifying data as bStats metrics. bStats itself processes a connection IP
temporarily for rate limiting, as described in its privacy policy.
Server owners can opt out globally for every bStats-enabled plugin by setting
enabled: false in plugins/bStats/config.yml. See the
bStats server-owner documentation and
privacy policy for the standard metrics
and privacy details.


