# ReturnMe
An addon for AuthMe, for Bungeecord, that saves the last server the player was on and then reconnects them to it once the player logs back onto the server and logs in.
## How to use?
1. Download the latest release of the plugin.
2. Put the downloaded file into your plugins directory.
3. Restart your server.
4. Head to “plugins/ReturnMe/config.yml” and configure the plugin to your liking!
5. Once you’re done configuring, restart your server again!
## Permissions
`returnme.use` – If enabled, this permission is used to allow players or groups to be returned to their last location.
## Reporting Issues
If you run into an issue whilst using my plugin, feel free to [open an issue](https://github.com/RealTriassic/ReturnMe/issues) and please explain the issue you’re experiencing thoroughly with reproduction steps. Make sure to attach your config.yml alongside your report and a stacktrace of the error, if any.
ValioBungee
# ValioBungee: The RedisBungee Limework’s fork
The original project of RedisBungee is no longer maintained, so we have forked the plugin.
RedisBungee uses [Redis](https://redis.io) with Java client [Jedis](https://github.com/redis/jedis/)
to Synchronize players data between [BungeeCord](https://github.com/SpigotMC/BungeeCord)
or [Velocity*](https://github.com/PaperMC/Velocity) proxies
This project is distributed under Eclipse Public License 1.0
You can find it [here](https://github.com/proxiodev/RedisBungee/blob/master/LICENSE)
You can find the original RedisBungee is by [astei](https://github.com/astei) and project can be
found [here](https://github.com/minecrafter/RedisBungee) or spigot
page [here, but its no longer available](https://www.spigotmc.org/resources/redisbungee.13494/)
Recon
# Recon: The Next-Generation Remote Control tool for Minecraft
**Recon** is a modern, secure, and reliable REST API-based alternative to the traditional Minecraft RCON protocol. Designed for stability and ease of integration, Recon solves the common issues associated with RCON, such as connection drops, permission management difficulties, and inconsistent response handling.
The name **Recon** stands for three core principles:
– **Re**liable-con: Built for stability. No more random connection drops.
– **Re**sponse-con: Guaranteed command execution feedback.
– **Re**st-con: Uses a standard REST API (HTTP/JSON) for effortless integration with any modern platform.
## Key Features
– **🚀 REST API Protocol**: Ditch the clunky RCON packets for clean, standard HTTP requests.
– **🔒 Security**: Every request and response is encrypted using **AES**. Includes Nonce and Timestamp validation to prevent replay attacks.
– **👥 Per-User Permissions**: Manage API access for multiple users with individual settings for:
– Whitelisted IP addresses.
– OP privilege toggling.
– Execution as a specific player.
– **📥 Command Queue**: If a player is offline when a command is sent, Recon can queue it to execute immediately upon their next login.
– **🌍 Multi-Language Support**: Built-in support for Arabic, German, English, Spanish, French, Hindi, Indonesian, Japanese, Portuguese, Russian, and Chinese.
– **🏗️ Multi-Platform Clients**: Ready-to-use client libraries for **PHP, Java, Python, JavaScript, TypeScript, Go, and Dart**.
– **⚡ High Performance**: Supports Paper, Folia (asynchronous) environments.
## Installation
1. Download the latest `Recon.jar` and place it in your server’s `plugins` folder.
2. Restart the server to generate configurations.
3. Configure the HTTP port (default: `4161`) and other settings in `config.yml`.
4. Use the `/recon` command in-game to create your first API user.
## API Specification
Recon listens for `POST` requests at the root path (`/`).
## Mobile Application
Recon is the Next-Generation Remote Control tool for Minecraft—an RCON alternative designed for both players and admins. 🚀
This plugin includes a function to automatically generate individual connection profiles for every player. These profiles allow players to enjoy a more streamlined gameplay experience by leveraging the application’s shortcut capabilities. ✅
Shortcuts can be uploaded to the cloud and shared by entering an ID. ☁
> **Important**:
> This application is a smartphone client for Recon. To use it, you must first install the Recon plugin on your server.
Get it on [Google Play](https://play.google.com/store/apps/details?id=net.enabify.recon) or [App Store](https://apps.apple.com/us/app/recon-remote-control-mc/id6759136210).
## License
Copyright (c) 2026 Enabify. Licensed under the MIT License with additional restrictions regarding mobile application distribution. See [LICENSE](https://github.com/yamak493/Recon?tab=License-1-ov-file#readme) for details.
> **Note**: Redistribution of this software as a mobile application on any digital app store is exclusively reserved for Enabify.
Raknetify
# Raknetify
A Fabric mod / BungeeCord plugin that uses RakNet to improve multiplayer experience significantly
under unreliable and rate-limited connections.
# Features
– Higher reliability and lower latency under unreliable and rate-limited client connections.
– Uses RakNet’s multiple channels with priorities to achieve higher responsiveness.
– Supports ViaVersion client-side and ViaVersion server-side. (MultiConnect compatibility is unknown)
**PvPIndex Battles** is a competitive PvP plugin for Paper, Folia, Purpur, Spigot, BungeeCord, and Velocity servers. It adds a full **1v1 duel and ranked matchmaking system** with per-mode **ELO ratings**, persistent global leaderboards, battle replays, and a moderation suite – all synced to [pvpindex.com](https://pvpindex.com) so your players’ rankings persist across the entire network.
– **10 ranked game modes** – Crystal, Sword, Pot, NoDebuff, Soup, Axe, Mace, Boxing, Sumo, UHC – each with independent ELO ladders and separate leaderboards
– **1v1 matchmaking queue** – fully configurable 54-slot GUI with per-mode ELO, countdowns, and automatic arena teleportation
– **Cross-server duels** – `/battle challenge [mode]` works standalone or routes through a Velocity or BungeeCord proxy
– **Network-wide tab completion** – proxy broadcasts all online players so `/battle challenge ` shows names from every backend server
– **Battle replay system** – frame-by-frame recording, reviewable in-game with `/pvpmod replay `
– **Arena pool** – procedural, schematic, and world-copy generation strategies; four bundled schematics included
– **Moderation suite** – player reports, local bans, federated network-wide bans, real-time spectating
– **PlaceholderAPI integration** – ELO, rank, win/loss, queue state, and active mode placeholders for scoreboards and tab lists
– **Fully configurable messages** via `messages.yml`
– **HMAC-signed payloads** – battles are cryptographically signed before submission; the API rejects anything tampered with
– **Open ELO formula** – K=32 trust-weighted implementation published under MIT at [github.com/PVP-Index/battle-validator](https://github.com/PVP-Index/battle-validator)
– **Folia compatible** – runs on Folia, Paper, Purpur, Spigot, and Bukkit (1.21+)
—
## Requirements
| Requirement | Version |
|—|—|
| Java | 21+ (25+ for Paper API 26.1.x) |
| Paper / Folia / Purpur / Spigot | 1.21.x or 1.21.4+ (API 26.1.x) |
| Velocity or BungeeCord *(optional)* | Velocity 3.x / BungeeCord 1.21+ |
| PlaceholderAPI *(optional)* | 2.11+ |
| PvPIndex API key | Free at [pvpindex.com](https://pvpindex.com) |
—
## Installation
### Paper / Folia / Purpur / Spigot
1. Drop `PvPIndexBattles-.jar` into `plugins/`.
2. Start the server, configs are generated automatically.
3. Stop the server, then add your API key to `plugins/PvPIndexBattles/config.yml`:
“`yaml
api:
api_key: “your-api-key-here”
server:
id: “my-server”
“`
4. Restart and run `/pvpindex` to confirm everything loaded correctly.
### Velocity / BungeeCord *(optional)*
Drop `PvPIndexBattles-velocity-.jar` into your proxy `plugins/` folder and configure `plugins/pvpindex-battles/config.properties` with the same API key and shared secret as your backend servers.
→ Full proxy setup guide: [docs.pvpindex.com/server_owner/proxy-setup](https://docs.pvpindex.com/server_owner/proxy-setup)
—
## Commands
### `/battle` Players
| Command | Description |
|—|—|
| `/battle` | Open the matchmaking mode selection GUI |
| `/battle challenge [mode]` | Send a duel challenge |
| `/battle accept ` | Accept a challenge |
| `/battle decline ` | Decline a challenge |
| `/battle leave` | Leave the queue or forfeit an active battle |
| Command | Permission | Description |
|—|—|—|
| `/pvpmod watch ` | `pvpindex.mod` | Spectate a live battle |
| `/pvpmod replay ` | `pvpindex.mod` | Play back a recorded battle |
| `/pvpmod report ` | `pvpindex.mod.report` | Report a player |
| `/pvpmod ban ` | `pvpindex.mod.ban` | Ban a player from battles |
| `/pvpmod unban ` | `pvpindex.mod.ban` | Unban a player |
—
## PlaceholderAPI
| Placeholder | Returns |
|—|—|
| `%pvpindex_elo%` | Overall ELO rating |
| `%pvpindex_elo_%` | ELO for a specific mode |
| `%pvpindex_rank%` | Global ladder position |
| `%pvpindex_wins%` | Session wins |
| `%pvpindex_losses%` | Session losses |
| `%pvpindex_kd%` | Win/loss ratio |
| `%pvpindex_in_battle%` | `true` / `false` |
| `%pvpindex_queued%` | `true` / `false` |
| `%pvpindex_queued_mode%` | Current queue mode or `none` |
| `%pvpindex_battle_type%` | Display name of the active mode |
The ELO validator is published under [MIT](https://github.com/PVP-Index/pvpindex-battles/blob/main/LICENSE). See [LICENSE](https://github.com/PVP-Index/pvpindex-battles/blob/main/LICENSE) for the plugin itself.
PunishManager
# PunishManager
**Discord Announces, Multi Lang Support, GUI on Bungee/Velocity/Spigot, All Common Punishment Commands**
# About
PunishManager offers you many features you need to create a quality environment on your server. It has general ban and mute commands. It has optional Discord features.
# Features
+ UUID support for online and offline mode.
+ All commands can be used by name or uuid.
+ You can punish players who have previously joined your server but are offline.
+ It has multi-language support. Messages are sent to players in their chosen language. If there is no language file in the player’s language, the messages in the default language file you specified will be used.+
+ Advanced tab completions.
+ When a player is punished, you can send embed messages to a specific channel in discord.
+ Placeholders for all punishes to be able to use values such as “name of player punished, operator name of punish, type of punish, remaining time of punish, server where punish occurred”.
+ You can use mysql or a local database if you want.
+ You can prevent players that you specify in the configuration from being punished.
+ If you want, you can show the names of everyone who has entered the server before in the tab completions.
+ You can ban commands you don’t want players to use while muted.
+ All disconnect messages are customizable.
+ You can see the current status of the player with the /check command.
+ You can quickly reload the plugin’s configuration single commands.
+ A handy gui for general management(requires Protocolize)
+ You can prevent the use of punish commands against players you specify to prevent undesirable situations.
+ It works on both Bungeecord, Velocity and Spigot with a single jar file.
+ For proxy servers, you only need to put the plugin in the Bungeecord plugin folder.
+ Command to import punishes from other plugins.
# GUI Feature
+ Players can change the plugin language for themselves.
+ Staff can reload the plugin.
+ Staff can manage punishes.
# Important Informations
+ For the GUI feature, the Protocolize plugin must be installed on your bungeecord server.
# Commands
+ punish : Punish Punish the player with predefined templates via a gui.
+ ban [reason]: Ban a player.
+ tempban
+ Spigot or Bungeecord
+ Java 1.8 or newer
+ Protocolize [Optional]
Wiki: https://mehmet27.gitbook.io/punishmanager
Help to translate: https://crowdin.com/project/punishmanager
Metrics Bungee: https://bstats.org/plugin/bungeecord/PunishManager/14772
Metrics Bukkit: https://bstats.org/plugin/bukkit/PunishManager/14913
Metrics Velocity: https://bstats.org/plugin/velocity/PunishManager Velocity/15231
# Contact and Support
If you need help with the plugin, you can contact me on our discord server.
Discord: https://discord.com/invite/MYjmmEqKvE
# NOTE
This plugin:
+ stores the ip addresses of your players.
+ can access your discord server for punish announcements.
+ uses bstats api for metrics.
+ connects to spiget api to check for updates.
+ automatically downloads the protocolize plugin for some platforms.
The reason why the jar file is large is due to many api used.
A solution will be produced for this in the near future.
PteroControl
# Pterodactyl Control – Minecraft Plugin
A powerful Minecraft plugin that allows you to manage your Pterodactyl game servers directly from in-game commands. Compatible with Velocity, BungeeCord, and Bukkit/Spigot/Paper servers.
## ✨ Features
### 🚀 Server Management
– **Start, stop, and restart** Pterodactyl servers via in-game commands
– **Execute console commands** on remote servers
### 🎯 Smart Autocomplete
– **Auto-completion** for Pterodactyl server names
– **Intelligent suggestions** based on available servers
– **Fast server lookup** with partial name matching
### ⚙️ Aliases
– **Enable/disable aliases** through configuration
## Discord
Can’t find what you’re looking for in the wiki?
Join the [Discord server](https://discord.gg/hNMvqruCuK) where you can get support or just hangout with the community.
## Metrics
[bStats](https://bstats.org) is used to collect anonymous usage data which is used to make decisions concerning the future of the plugin.
The collected data is publicly available and can be viewed here:
– [Bungeecord](https://bstats.org/plugin/bungeecord/ProxyUtils/18438)
– [Velocity](https://bstats.org/plugin/velocity/ProxyUtils/18439)
ProxyStaff
ProxyStaff is a customizable StaffChat for network. It works perfectly on Waterfall.
__Feature :__
– **No reload** config (instant changes) !
– **No command** !
– **Custom** prefix !
– **Global** and **per server** different chat !
– **Full server name** & **short server name** !
__Permission :__
– `proxystaff.global.send` Send a message to the global staff chat.
– `proxystaff.global.receive` Recieve the message of the global staff chat.
– `proxystaff.server.send.servername` Send a message to the staff chat relative on that server (Message will be sent on the server who players are on).
– `proxystaff.server.receive.servername` Receive the message of the staff chat relative on that server (Message will be sent on the server who players are on).
servername = Name of the server to use per permission server.
**What it does**
Network-wide **join/leave/switch** messages with per-player toggles, vanish support, LuckPerms/PAPI placeholders, and optional webhook ping.
> **Note:** This is a **proxy** plugin — install on **BungeeCord/Waterfall** or **Velocity** (not on Spigot/Paper).
**Works on**: BungeeCord/Waterfall, Velocity
**How to use**
1. Install on your **proxy** and restart to generate the config.
2. Customize messages/placeholders and (optionally) webhook settings.
3. Grant the view/toggle permissions as needed.
**Config (YAML)**
“`yaml
# ProxyPlayerNotify Config
# This config file contains settings for the ProxyPlayerNotify plugin.
# Use this file to customize the join/leave messages and permissions.
# Use n to create multiple lines/messages to players.
# Set message to “” to not send any message/empty.
# Network Join Message
# This message is displayed when a player joins the network.
# Placeholders available: %player%, %lp_prefix%, %lp_suffix%, %server%, %time%.
join_message: “%player% has joined the network (Logged in server: %server%) at %time%”
# Network Private Join Message
# This message is displayed only to the player who joins the network.
# It has a higher priority than the public join message.
# Placeholders available: %player%, %lp_prefix%, %lp_suffix%, %server%, %time%.
join_private_message:
– “&aWelcome, %player%!”
– “&bYou have joined the server %server% at %time%.”
– “Enjoy your stay!”
# First Join Message
# This message is displayed when a player joins the network for the first time.
# Placeholders available: %player%, %lp_prefix%, %lp_suffix%, %server%, %time%.
first_join_message: “%player% has joined the network for the first time on %server% at %time%”
# First Join Private Message
# This message is displayed only to the player joining for the first time.
# Placeholders available: %player%, %lp_prefix%, %lp_suffix%, %server%, %time%.
first_join_private_message: “&aWelcome for the first time, %player%!”
# Servers Switch Message
# This message is displayed when a player switches to a different server.
# Placeholders available: %player%, %last_server%, %server%, %time%, %lp_prefix%, %lp_suffix%.
switch_message: “%player% has switched from %last_server% and joined to the %server% server at %time%”
# Network Leave Message
# This message is displayed when a player leaves the network.
# Placeholders available: %player%, %lp_prefix%, %lp_suffix%, %last_server%, %time%.
leave_message: “%player% has left the network (Last server: %last_server%) at %time%”
# Delay for Join Messages
# This option sets the delay before sending the join message after a player connects.
# For example, join_message_delay: 49 will send the message after 49 ticks.
# Warning: Setting this value too low may cause messages not to be sent or be blank placeholder if the server name is not yet available.
join_message_delay: 45
# Delay for First Join Messages
# This option sets the delay before sending the first join message after a player connects.
first_join_message_delay: 10
# Delay for Private Join Messages
# This option sets the delay before sending the private join message to the joining player.
# For example, join_private_message_delay: 50 will send the message after 50 ticks.
# Warning: Setting this value too low may cause messages not to be sent or be blank placeholder if the server name is not yet available.
join_private_message_delay: 50
# Delay for First Join Private Messages
# This option sets the delay before sending the first join private message to the joining player.
first_join_private_message_delay: 10
# Delay for Switch Messages
# This option sets the delay before sending the switch message after a player switches servers.
# For example, switch_message_delay: 0 will send the message after 0 ticks.
switch_message_delay: 0
# Disable messages for vanished players (Currently supports PremiumVanish and SuperVanish)
disable_vanish_notifications: false
# Option to let players rejoin the server they were on before they left the network.
# If this is enabled, the player will be sent to the last server on join in which they were on before they left the network.
# If enabled, the message delay options would need to be increased so that the messages can get the server
join_last_server: false
# Enable MiniMessage format parsing for all messages
use_minimessage: false
# Permissions
# Use these settings to control who can see the join/leave messages.
# Enable permissions if you want to use permissions and want to use next two options.
# If permissions enabled Then if notify_message is true and the player doesn’t have ppn.notify permission, then their join/leave/message will not be sent.
# If permissions enabled Then if hide_message is true and the player doesn’t have ppn.view permission, then they won’t see the others’ join/switch/leave messages.
permission:
# Enable this if you want to use permissions and want to use next two options.
permissions: false
# Notify Messages
# If this is true and the player doesn’t have ppn.notify permission, then their join/leave/message will not be sent.
notify_message: false
# Hide Messages
# If this is true and the player doesn’t have ppn.view permission, then they won’t see the others’ join/switch/leave messages.
hide_message: false
# Server Names
# Define custom server names here. Players can join/leave/switch to the server using the custom names specified below.
ServerNames:
example: “example-1”
lobby: “Hub”
# Disabled Servers
# Define the backend servers (lowercase) where the join/switch/leave messages should not be sent.
# In simple words, no messages of this plugin will be sent to players on that server
# In short: No activity notifications are sent to players on these servers.
DisabledServers:
– “example-1”
– “other-backend-server”
# Private Servers
# Specify the private servers (lowercase) where if player joins, leaves, and switches from and to, notifications should not be sent.
# Think about them like admin servers
# When someone joins it, the whole proxy should not be notified about that because you kind of want to keep that server private/secret and not let the players know.
# In short: Activity notifications related to these servers are not broadcasted across the entire network.
PrivateServers:
– “example”
– “private-server”
# Limbo Servers
# Specify the limbo servers (lowercase) where player join, leave, and switch notifications should be managed differently.
# These servers act as pass-throughs most of the time and can be configured to adjust notification behavior accordingly.
# When a player joins a limbo server, no network-wide join notification is sent.
# When a player switches from a limbo server to a game server, it should send a join notification as if the player is joining the network for the first time.
# Conversely, when a player switches from a game server to a limbo server, it should send a leave notification as if the player is leaving the network.
# This configuration helps avoid unnecessary notifications and prevents stealthy movements between public and private parts of the network.
# In short: Join and leave notifications are sent based on transitions to and from these servers to manage network-wide notifications effectively.
LimboServers:
– “limbo-afk”
# Disabled Players
# Specify the players (lowercase) that should not send any notification messages.
# They will also will not recieve join_private_message.
# It is not recommended to use this feature and instead use permissions for each group/player
DisabledPlayers:
– “player1”
– “player2”
# Webhook
# Configure a webhook notification sent when a player joins the network.
# Placeholders available: %player%, %server%, %time%.
webhook:
enabled: false
url: “”
message: “%player% joined %server% at %time%”
# Send webhook as Discord embed (recommended). If true, the message above is used as the embed description.
use_embed: true
# Embed color as decimal RGB (e.g., 3447003 is Discord “blurple”).
embed_color: 3447003