BungeeJoinMessages

BungeeJoinMessages is a simple but powerful BungeeCord plugin for handling join, leave, server-switch, and first-time join messages across your network.

It works fine on a normal single-proxy setup, but it can also sync messages across multiple proxies using Redis if you run a larger network.

Features

• Custom join messages
• Custom leave messages
• Custom server-switch messages
• First-time join messages
• UUID-based first-join tracking
• %firstjoin_number% placeholder
• Redis support for multi-proxy networks
• Import existing players from playerdata or usercache.json
• Manual UUID import folder for restricted hosting panels
• PremiumVanish support
• Silent staff joins/leaves
• Server blacklist and whitelist modes
• Legacy & colors and hex colors
• Custom server display names
• Automatic config migration
• Automatic UUID data migration
• Full config-example.yml with real examples

Default Messages

SwapServerMessage: '&e%player%&r &8-> &7%to%'
JoinNetworkMessage: '&a>>&8 %displayname%'
LeaveNetworkMessage: '&c<<&8 %displayname%'

Example output:

>> Steve
Steve -> Survival
<< Steve

First-Time Joins

The plugin can detect when someone joins the network for the first time.

Example:

★ Steve has joined the network for the first time!

Players are tracked by UUID, so changing their username will not trigger another first-join message.

You can also use:

%firstjoin_number%

to do things like:

★ Steve is player #427 to join the network!

Existing Servers

If you're installing this on an existing network, you can import old player UUIDs so everyone doesn't show up as a new player.

Supported sources include:

world/playerdata/
usercache.json

You can also point the plugin to a custom file location.

For hosts that don't allow one server to access another server's files, the plugin creates:

plugins/BungeeJoinMessages/Old UUID ID/

Copy your old player data into that folder and the plugin can import it from there.

Multi-Proxy Support

If you run more than one BungeeCord proxy, BungeeJoinMessages can use Redis to sync:

• Join messages
• Leave messages
• Server-switch messages
• First-time join messages
• First-join UUID data

So if a player joins through Proxy 1, players connected through Proxy 2 can still see the message.

Redis is completely optional. You do not need it for a normal single-proxy setup.

Config Files

config.yml contains your actual live settings.

config-example.yml contains the full documentation and examples.

The example config is refreshed when the plugin is updated so it always matches the version you are running.

Commands

Command	Description
/fm fakejoin	Test the join message
/fm fakequit	Test the leave message
/fm fakeswitch <from> <to>	Test a server-switch message
/fm fakefirstjoin	Test the first-join message
/fm fakefirstjoin <number>	Test %firstjoin_number%
/togglejoinmessage	Toggle received messages
/bjointoggle	Alias
/bungeejoinreload	Reload the plugin
/bjoinreload	Alias

Installation

1. Put the JAR in your BungeeCord plugins folder.
2. Restart the proxy.
3. Edit plugins/BungeeJoinMessages/config.yml.
4. Use config-example.yml if you need help with any setting.

That's it for a normal single-proxy setup.

If you run multiple proxies, configure Redis on each proxy and use the same channel.

Credits

Original Creator: Tirco

The original project appears to be abandoned.

Modified & Maintained by: Gameitall

Current Version: 26.2 R7