BungeeJoinMessages
BungeeJoinMessages 是一款简单但功能强大的 BungeeCord 插件,用于处理跨网络中的加入、离开、服务器切换以及首次加入消息。
它在普通的单代理设置中运行良好,但如果你的网络规模较大,它还可以通过 Redis 在多个代理之间同步消息。
功能特性
- 自定义加入消息
- 自定义离开消息
- 自定义服务器切换消息
- 首次加入消息
- 基于 UUID 的首次加入追踪
%firstjoin_number% 占位符
- 支持多代理网络的 Redis 功能
- 从
playerdata 或 usercache.json 导入现有玩家数据
- 为受限的主机面板提供手动 UUID 导入文件夹
- 支持 PremiumVanish
- 静默显示工作人员(Staff)的加入/离开
- 服务器黑名单和白名单模式
- 支持传统
& 颜色代码和十六进制颜色代码
- 自定义服务器显示名称
- 自动配置文件迁移
- 自动 UUID 数据迁移
- 包含真实示例的完整
config-example.yml
默认消息
SwapServerMessage: '&e%player%&r &8-> &7%to%'
JoinNetworkMessage: '&a>>&8 %displayname%'
LeaveNetworkMessage: '&c<<&8 %displayname%'
输出示例:
>> Steve
Steve -> Survival
<< Steve
首次加入
该插件可以检测玩家是否首次加入网络。
示例:
★ Steve has joined the network for the first time!
玩家通过 UUID 进行追踪,因此更改用户名不会再次触发首次加入消息。
你还可以使用:
%firstjoin_number%
来实现类似这样的效果:
★ Steve is player #427 to join the network!
现有服务器
如果你是在现有的网络上安装此插件,你可以导入旧的玩家 UUID,这样所有人就不会都被识别为新玩家。
支持的来源包括:
world/playerdata/
usercache.json
你也可以将插件指向自定义的文件位置。
对于不允许一个服务器访问另一个服务器文件的托管环境,插件会创建以下文件夹:
plugins/BungeeJoinMessages/Old UUID ID/
将旧的玩家数据复制到此文件夹中,插件即可从中导入。
多代理支持
如果你运行多个 BungeeCord 代理,BungeeJoinMessages 可以使用 Redis 来同步以下内容:
- 加入消息
- 离开消息
- 服务器切换消息
- 首次加入消息
- 首次加入的 UUID 数据
因此,如果玩家通过 Proxy 1 加入,通过 Proxy 2 连接的玩家仍然可以看到该消息。
Redis 是完全可选的。在普通的单代理设置中不需要它。
配置文件
config.yml 包含你实际运行的设置。
config-example.yml 包含完整的文档和示例。
示例配置文件会在插件更新时刷新,以确保始终与你正在运行的版本匹配。
命令
| 命令 |
描述 |
/fm fakejoin |
测试加入消息 |
/fm fakequit |
测试离开消息 |
/fm fakeswitch <from> <to> |
测试服务器切换消息 |
/fm fakefirstjoin |
测试首次加入消息 |
/fm fakefirstjoin <number> |
测试 %firstjoin_number% |
/togglejoinmessage |
切换接收到的消息 |
/bjointoggle |
别名 |
/bungeejoinreload |
重新加载插件 |
/bjoinreload |
别名 |
安装
- 将 JAR 文件放入你的 BungeeCord
plugins 文件夹中。
- 重启代理。
- 编辑
plugins/BungeeJoinMessages/config.yml。
- 如果需要对任何设置提供帮助,请参考
config-example.yml。
对于普通的单代理设置,以上就是全部步骤。
如果你运行多个代理,请在每个代理上配置 Redis 并使用相同的频道。
致谢
原始作者: Tirco
原始项目似乎已停止维护。
修改与维护者: Gameitall
当前版本: 26.2 R7
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
- Put the JAR in your BungeeCord
plugins folder.
- Restart the proxy.
- Edit
plugins/BungeeJoinMessages/config.yml.
- 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
评论 0
登录后参与评分
还没有评论,来抢沙发吧