Proxied Warp
GitHub - Hangar - Modrinth - SpigotMC - Discord
Proxied Warp 允许玩家通过触发目标服务器上已有的传送插件(例如 Essentials 或类似插件),在 Velocity 网络中的服务器之间进行跨服传送。玩家无需手动切换服务器——Proxied Warp 会自动将其连接到目标服务器,并在该服务器上执行传送指令。
该项目由三个部分组成:
| 模块 |
功能 |
velocity |
在后端服务器之间转发传送请求,并在需要时将玩家连接到目标服务器 |
paper |
接收玩家的 /proxiedwarp 指令,并在连接成功后执行实际的传送指令。适用于 Paper 后端服务器。支持 MiniMessage 格式的消息样式 |
spigot |
与 paper 模块功能相同,但适用于 Spigot 后端服务器。消息使用传统的 Minecraft 颜色代码(&)而非 MiniMessage |
工作原理
代理服务器与后端服务器之间的通信通过共享的 Plugin Messaging Channel(插件消息通道)完成:proxied_warp:proxied_warp。
工作流程如下:
- 玩家执行指令 – 在后端服务器上,玩家调用已注册的指令,指定目标服务器和传送点名称(例如
/proxiedwarp lobby spawn)。
- 后端插件发送消息 – 插件(根据服务器类型选择
paper 或 spigot 模块)首先检查输入内容和权限,然后构建消息 <player> <server> <warp>,并通过通道以插件消息的形式发送给代理服务器。
- Velocity 插件处理请求:
- 检查指定的玩家和目标服务器是否存在。
- 如果玩家已经在目标服务器上,则直接转发消息。
- 否则,先建立到目标服务器的连接,待服务器切换成功后再转发消息。
- 目标服务器执行传送 – 目标服务器上的插件接收转发的消息,检查玩家是否在该服务器上在线,并使用给定的传送点名称执行配置的传送指令。
安装
- 将 Velocity 模块 作为
.jar 文件放入 Velocity 代理服务器的 plugins 文件夹中。
- 在玩家应能触发或接收传送的每个后端服务器上安装相应的后端模块:在 Paper 服务器上安装
paper 模块,在 Spigot 服务器上安装 spigot 模块。
- 重启代理服务器和相关后端服务器。
配置(Paper/Spigot 模块)
首次启动时,相应插件会生成一个包含以下默认值的 config.yml:
paper 模块:
command-prefix: warp
need-permission: false
whitelisted-servers: []
whitelisted-warps: []
aliases:
spawn: lobby
message:
usage: '<red>Usage:</red> /proxiedwarp <server> <warp>'
permission: '<red>You do not have permission to do that!</red>'
server-not-whitelisted: '<red>This server is not whitelisted!</red>'
warp-not-whitelisted: '<red>This warp is not whitelisted!</red>'
spigot 模块:
command-prefix: warp
need-permission: false
whitelisted-servers: []
whitelisted-warps: []
aliases:
spawn: lobby
message:
usage: '&cUsage:&r /proxiedwarp <server> <warp>'
permission: '&cYou do not have permission to do that!'
server-not-whitelisted: '&cThis server is not whitelisted!'
warp-not-whitelisted: '&cThis warp is not whitelisted!'
| 键 |
描述 |
command-prefix |
在目标服务器上执行的命令,用于实际将玩家传送至 warp 点(例如已安装的 warp 插件的命令)。 |
need-permission |
决定玩家是否需要显式权限才能对特定服务器使用 /proxiedwarp(参见 Permissions)。 |
whitelisted-servers |
允许作为目标的服务器列表。如果为空,则允许所有服务器。 |
whitelisted-warps |
允许触发的 warp 列表。如果为空,则允许所有 warp。 |
aliases |
定义 warp 别名的部分,将简单名称映射到目标服务器(例如 spawn: lobby)。 |
message.usage |
命令使用不正确时显示的消息。 |
message.permission |
缺少权限时显示的消息。 |
message.server-not-whitelisted |
服务器未列入白名单时显示的消息。 |
message.warp-not-whitelisted |
warp 未列入白名单时显示的消息。 |
在 paper 模块中,消息支持 MiniMessage 格式(例如 <red>、<bold>)。在 spigot 模块中,消息改用带有 & 作为格式化字符的旧版 Minecraft 颜色代码(例如 &c 表示红色),因为那里不可用 MiniMessage。
命令
后端服务器(Paper 或 Spigot)上提供以下命令:
/proxiedwarp <server> <warp>
/proxiedwarp <alias>
<server> – 目标服务器的名称,如 Velocity 配置(velocity.toml)中所注册的那样。
<warp> – 目标服务器上 warp 点的名称。
<alias> – 在 config.yml 中定义的别名,映射到特定的服务器和 warp。
该命令只能由玩家执行(不能从控制台执行)。
权限
如果在 config.yml 中将 need-permission 设置为 true,玩家需要拥有以下权限之一才能执行 /proxiedwarp <server> <warp>:
| 权限 |
效果 |
proxiedwarp.warp.* |
允许传送到所有服务器。 |
proxiedwarp.warp.<warp> |
允许传送到特定 warp(例如 proxiedwarp.warp.spawn)。 |
如果两者都缺失,玩家将收到在 message.permission 中配置的错误消息,并且请求不会发送到代理。
如果 need-permission 设置为 false(默认值),则不执行权限检查,每个玩家都可以为每个注册的服务器使用该命令。
要求
- Velocity 代理。
- 基于 Paper 的后端服务器(带
paper 模块)或基于 Spigot 的后端服务器(带 spigot 模块)。
- 每个涉及的后端服务器上都有一个可通过命令触发(而非通过 API)且其命令可输入到
command-prefix 中的 warp 插件。
- Java 版本 25 或更高版本。
已知限制
- Proxied Warp 本身不检查指定的 warp 是否实际存在——这仅由目标服务器上调用的 warp 插件进行检查。
Proxied Warp 允许玩家在 Velocity 网络内的服务器之间传送,通过在目标服务器上触发现有的 warp 插件(例如 Essentials 或类似插件)来实现。玩家无需手动切换服务器——Proxied Warp 会自动将他们连接到目标服务器,然后在那里执行 warp 命令。
该项目由三部分组成:
| 模块 |
任务 |
velocity |
在后端服务器之间转发 warp 请求,并在需要时将玩家连接到目标服务器 |
paper |
接收来自玩家的 /proxiedwarp 命令,并在服务器连接后执行实际的 warp 命令。适用于 Paper 后端服务器。支持消息的 MiniMessage 格式 |
spigot |
与 paper 模块功能相同,但适用于 Spigot 后端服务器。消息使用旧版 Minecraft 颜色代码(&)而不是 MiniMessage |
工作原理
代理与后端服务器之间的通信通过共享的 Plugin Messaging Channel 进行:proxied_warp:proxied_warp。
工作流程如下:
- 玩家执行命令 – 在后端服务器上,玩家调用已注册的命令,指定目标服务器和传送点名称(例如
/proxiedwarp lobby spawn)。
- 后端插件发送消息 – 插件(根据服务器类型选择
paper 或 spigot 模块)首先检查输入内容和权限,然后构建消息 <player> <server> <warp> 并通过通道作为插件消息发送给代理。
- Velocity 插件处理请求:
- 检查指定的玩家和目标服务器是否存在。
- 如果玩家已经在目标服务器上,则直接转发消息。
- 否则,先建立与目标服务器的连接,仅在服务器切换成功后才转发消息。
- 目标服务器执行传送 – 目标服务器上的插件接收转发的消息,检查玩家是否在该服务器上在线,并使用给定的传送点名称执行配置的传送命令。
安装
- 将 Velocity 模块 作为
.jar 文件放入 Velocity 代理的 plugins 文件夹中。
- 在允许玩家触发或接收传送的每个后端服务器上安装相应的后端模块:Paper 服务器上安装
paper 模块,Spigot 服务器上安装 spigot 模块。
- 重启代理和相关后端服务器。
配置(Paper/Spigot 模块)
首次启动时,相应插件会生成一个包含以下默认值的 config.yml:
paper 模块:
command-prefix: warp
need-permission: false
whitelisted-servers: []
whitelisted-warps: []
aliases:
spawn: lobby
message:
usage: '<red>Usage:</red> /proxiedwarp <server> <warp>'
permission: '<red>You do not have permission to do that!</red>'
server-not-whitelisted: '<red>This server is not whitelisted!</red>'
warp-not-whitelisted: '<red>This warp is not whitelisted!</red>'
spigot 模块:
command-prefix: warp
need-permission: false
whitelisted-servers: []
whitelisted-warps: []
aliases:
spawn: lobby
message:
usage: '&cUsage:&r /proxiedwarp <server> <warp>'
permission: '&cYou do not have permission to do that!'
server-not-whitelisted: '&cThis server is not whitelisted!'
warp-not-whitelisted: '&cThis warp is not whitelisted!'
| 键值 |
描述 |
command-prefix |
在目标服务器上执行的命令,用于实际将玩家传送到传送点(例如,已安装的传送插件的命令)。 |
need-permission |
决定玩家是否需要显式权限才能在特定服务器上执行 /proxiedwarp(参见 Permissions)。 |
whitelisted-servers |
允许用作目标的服务器列表。如果为空,则允许所有服务器。 |
whitelisted-warps |
允许触发的传送点列表。如果为空,则允许所有传送点。 |
aliases |
定义传送点别名的部分,将简单名称映射到目标服务器(例如 spawn: lobby)。 |
message.usage |
当命令使用不正确时显示的消息。 |
message.permission |
当缺少权限时显示的消息。 |
message.server-not-whitelisted |
当服务器未被列入白名单时显示的消息。 |
message.warp-not-whitelisted |
当传送点未被列入白名单时显示的消息。 |
在 paper 模块 中,消息支持 MiniMessage 格式(例如 <red>、<bold>)。而在 spigot 模块 中,由于 MiniMessage 不可用,消息使用传统的 Minecraft 颜色代码,以 & 作为格式化字符(例如 &c 表示红色)。
命令
以下命令在后端服务器(Paper 或 Spigot)上可用:
/proxiedwarp <server> <warp>
/proxiedwarp <alias>
<server> – 目标服务器的名称,已在 Velocity 配置(velocity.toml)中注册。
<warp> – 目标服务器上传送点的名称。
<alias> – 在 config.yml 中定义的别名,映射到特定的服务器和传送点。
该命令只能由玩家执行(不能从控制台执行)。
权限
如果在 config.yml 中将 need-permission 设置为 true,则玩家需要具备以下任一权限才能执行 /proxiedwarp <server> <warp>:
| 权限 |
效果 |
proxiedwarp.warp.* |
允许传送到所有服务器。 |
proxiedwarp.warp.<warp> |
允许传送到特定传送点(例如 proxiedwarp.warp.spawn)。 |
如果缺少这两项权限,玩家将收到在 message.permission 中配置的错误消息,且请求不会发送到代理。
如果 need-permission 设置为 false(默认值),则不会执行权限检查,每个玩家都可以为所有已注册的服务器使用该命令。
要求
- 一个 Velocity 代理服务器。
- 一个基于 Paper 的后端服务器(使用
paper 模块)或一个基于 Spigot 的后端服务器(使用 spigot 模块)。
- 每个涉及的后端服务器上都有一个可以通过命令触发的传送插件(不能通过 API 触发),且其命令可以填入
command-prefix 中。
- Java 25 或更高版本。
已知限制
- Proxied Warp 本身不会检查指定的传送点是否实际存在——这仅由目标服务器上被调用的传送插件进行检查。
Proxied Warp
GitHub - Hangar - Modrinth - SpigotMC - Discord
Proxied Warp allows players to teleport across servers within a Velocity network by triggering an existing warp plugin (e.g., Essentials, or similar) on the target server. The player doesn't need to manually switch servers – Proxied Warp automatically connects them to the target server and then executes the warp command there.
The project consists of three parts:
| Module |
Task |
velocity |
Forwards warp requests between backend servers and connects players to the target server when needed |
paper |
Receives the /proxiedwarp command from the player and executes the actual warp command after the server connection. For Paper backend servers. Supports MiniMessage formatting for messages |
spigot |
Same functionality as the paper module, but for Spigot backend servers. Messages use legacy Minecraft color codes (&) instead of MiniMessage |
How It Works
Communication between the proxy and backend servers happens via a shared Plugin Messaging Channel: proxied_warp:proxied_warp.
The process works as follows:
- Player executes command – On a backend server, the player calls the registered command with a target server and warp name (e.g.,
/proxiedwarp lobby spawn).
- Backend plugin sends message – The plugin (
paper or spigot module, depending on the server) first checks the input and permission, then builds the message <player> <server> <warp> and sends it as a plugin message over the channel to the proxy.
- Velocity plugin processes the request:
- Checks whether the specified player and target server exist.
- If the player is already on the target server, the message is forwarded directly.
- Otherwise, a connection to the target server is established first, and the message is only forwarded after the server switch succeeds.
- Target server executes the warp – The plugin on the target server receives the forwarded message, checks whether the player is online there, and executes the configured warp command with the given warp name.
Installation
- Place the Velocity module as a
.jar file in the plugins folder of the Velocity proxy.
- Install the matching backend module on every backend server where players should be able to trigger or receive warps: the
paper module on Paper servers, the spigot module on Spigot servers.
- Restart the proxy and the affected backend servers.
Configuration (Paper/Spigot Modules)
On first startup, the respective plugin generates a config.yml with the following default values:
paper module:
command-prefix: warp
need-permission: false
whitelisted-servers: []
whitelisted-warps: []
aliases:
spawn: lobby
message:
usage: '<red>Usage:</red> /proxiedwarp <server> <warp>'
permission: '<red>You do not have permission to do that!</red>'
server-not-whitelisted: '<red>This server is not whitelisted!</red>'
warp-not-whitelisted: '<red>This warp is not whitelisted!</red>'
spigot module:
command-prefix: warp
need-permission: false
whitelisted-servers: []
whitelisted-warps: []
aliases:
spawn: lobby
message:
usage: '&cUsage:&r /proxiedwarp <server> <warp>'
permission: '&cYou do not have permission to do that!'
server-not-whitelisted: '&cThis server is not whitelisted!'
warp-not-whitelisted: '&cThis warp is not whitelisted!'
| Key |
Description |
command-prefix |
Command that is executed on the target server to actually teleport the player to the warp point (e.g., the command of the installed warp plugin). |
need-permission |
Determines whether players need an explicit permission to use /proxiedwarp for a specific server (see Permissions). |
whitelisted-servers |
List of servers that are allowed to be used as a target. If empty, all servers are allowed. |
whitelisted-warps |
List of warps that are allowed to be triggered. If empty, all warps are allowed. |
aliases |
Section to define aliases for warps, mapping a simple name to a target server (e.g., spawn: lobby). |
message.usage |
Message shown when the command is used incorrectly. |
message.permission |
Message shown when permission is missing. |
message.server-not-whitelisted |
Message shown when a server is not whitelisted. |
message.warp-not-whitelisted |
Message shown when a warp is not whitelisted. |
In the paper module, messages support MiniMessage formatting (e.g. <red>, <bold>). In the spigot module, messages use legacy Minecraft color codes with & as the formatting character (e.g. &c for red) instead, since MiniMessage is not available there.
Command
The following command is available on the backend server (Paper or Spigot):
/proxiedwarp <server> <warp>
/proxiedwarp <alias>
<server> – Name of the target server, as registered in the Velocity configuration (velocity.toml).
<warp> – Name of the warp point on the target server.
<alias> – An alias defined in the config.yml that maps to a specific server and warp.
The command can only be executed by players (not from the console).
Permissions
If need-permission is set to true in config.yml, a player needs one of the following permissions to execute /proxiedwarp <server> <warp>:
| Permission |
Effect |
proxiedwarp.warp.* |
Allows warping to all servers. |
proxiedwarp.warp.<warp> |
Allows warping to a specific warp (e.g., proxiedwarp.warp.spawn). |
If both permissions are missing, the player receives the error message configured in message.permission, and the request is not sent to the proxy.
If need-permission is set to false (default), no permission check is performed and every player can use the command for every registered server.
Requirements
- A Velocity proxy.
- A Paper based backend server (with the
paper module) or a Spigot based backend server (with the spigot module).
- A warp plugin on each involved backend server that can be triggered via command (not via API), and whose command can be entered in
command-prefix.
- Java version 25 or higher.
Known Limitations
- Proxied Warp itself does not check whether the specified warp actually exists – this is only checked by the invoked warp plugin on the target server.
Proxied Warp allows players to teleport across servers within a Velocity network by triggering an existing warp plugin (e.g., Essentials, or similar) on the target server. The player doesn't need to manually switch servers – Proxied Warp automatically connects them to the target server and then executes the warp command there.
The project consists of three parts:
| Module |
Task |
velocity |
Forwards warp requests between backend servers and connects players to the target server when needed |
paper |
Receives the /proxiedwarp command from the player and executes the actual warp command after the server connection. For Paper backend servers. Supports MiniMessage formatting for messages |
spigot |
Same functionality as the paper module, but for Spigot backend servers. Messages use legacy Minecraft color codes (&) instead of MiniMessage |
How It Works
Communication between the proxy and backend servers happens via a shared Plugin Messaging Channel: proxied_warp:proxied_warp.
The process works as follows:
- Player executes command – On a backend server, the player calls the registered command with a target server and warp name (e.g.,
/proxiedwarp lobby spawn).
- Backend plugin sends message – The plugin (
paper or spigot module, depending on the server) first checks the input and permission, then builds the message <player> <server> <warp> and sends it as a plugin message over the channel to the proxy.
- Velocity plugin processes the request:
- Checks whether the specified player and target server exist.
- If the player is already on the target server, the message is forwarded directly.
- Otherwise, a connection to the target server is established first, and the message is only forwarded after the server switch succeeds.
- Target server executes the warp – The plugin on the target server receives the forwarded message, checks whether the player is online there, and executes the configured warp command with the given warp name.
Installation
- Place the Velocity module as a
.jar file in the plugins folder of the Velocity proxy.
- Install the matching backend module on every backend server where players should be able to trigger or receive warps: the
paper module on Paper servers, the spigot module on Spigot servers.
- Restart the proxy and the affected backend servers.
Configuration (Paper/Spigot Modules)
On first startup, the respective plugin generates a config.yml with the following default values:
paper module:
command-prefix: warp
need-permission: false
whitelisted-servers: []
whitelisted-warps: []
aliases:
spawn: lobby
message:
usage: '<red>Usage:</red> /proxiedwarp <server> <warp>'
permission: '<red>You do not have permission to do that!</red>'
server-not-whitelisted: '<red>This server is not whitelisted!</red>'
warp-not-whitelisted: '<red>This warp is not whitelisted!</red>'
spigot module:
command-prefix: warp
need-permission: false
whitelisted-servers: []
whitelisted-warps: []
aliases:
spawn: lobby
message:
usage: '&cUsage:&r /proxiedwarp <server> <warp>'
permission: '&cYou do not have permission to do that!'
server-not-whitelisted: '&cThis server is not whitelisted!'
warp-not-whitelisted: '&cThis warp is not whitelisted!'
| Key |
Description |
command-prefix |
Command that is executed on the target server to actually teleport the player to the warp point (e.g., the command of the installed warp plugin). |
need-permission |
Determines whether players need an explicit permission to use /proxiedwarp for a specific server (see Permissions). |
whitelisted-servers |
List of servers that are allowed to be used as a target. If empty, all servers are allowed. |
whitelisted-warps |
List of warps that are allowed to be triggered. If empty, all warps are allowed. |
aliases |
Section to define aliases for warps, mapping a simple name to a target server (e.g., spawn: lobby). |
message.usage |
Message shown when the command is used incorrectly. |
message.permission |
Message shown when permission is missing. |
message.server-not-whitelisted |
Message shown when a server is not whitelisted. |
message.warp-not-whitelisted |
Message shown when a warp is not whitelisted. |
In the paper module, messages support MiniMessage formatting (e.g. <red>, <bold>). In the spigot module, messages use legacy Minecraft color codes with & as the formatting character (e.g. &c for red) instead, since MiniMessage is not available there.
Command
The following command is available on the backend server (Paper or Spigot):
/proxiedwarp <server> <warp>
/proxiedwarp <alias>
<server> – Name of the target server, as registered in the Velocity configuration (velocity.toml).
<warp> – Name of the warp point on the target server.
<alias> – An alias defined in the config.yml that maps to a specific server and warp.
The command can only be executed by players (not from the console).
Permissions
If need-permission is set to true in config.yml, a player needs one of the following permissions to execute /proxiedwarp <server> <warp>:
| Permission |
Effect |
proxiedwarp.warp.* |
Allows warping to all servers. |
proxiedwarp.warp.<warp> |
Allows warping to a specific warp (e.g., proxiedwarp.warp.spawn). |
If both permissions are missing, the player receives the error message configured in message.permission, and the request is not sent to the proxy.
If need-permission is set to false (default), no permission check is performed and every player can use the command for every registered server.
Requirements
- A Velocity proxy.
- A Paper based backend server (with the
paper module) or a Spigot based backend server (with the spigot module).
- A warp plugin on each involved backend server that can be triggered via command (not via API), and whose command can be entered in
command-prefix.
- Java version 25 or higher.
Known Limitations
- Proxied Warp itself does not check whether the specified warp actually exists – this is only checked by the invoked warp plugin on the target server.
评论 0
登录后参与评分
还没有评论,来抢沙发吧