Repository navigation
[BUG] Multi Proxy #67
Description
Hello,
When we want to use multi proxy through docker we can't set one as server and other like client because the first one can be closed and a new one can be opnned after.
I can have server "manager" i already used it for all my server but it's a paper server so i suggested something simple.
Allow backends and velocity to be client and server. After that we will place our scripts on proxy side or paper side (where is the server it's more logical).
And after that create a new execute target like :
- id: "CURRENT_SERVER"
location: VELOCITY
For exemple i need to use this script :
version: 2
name: skyblock
description: Send the player to the Skyblock
enabled: true
aliases: [sky]
permissions:
enabled: true
silent: false
register:
- id: "login_01"
location: BACKEND
- id: "login_02"
location: BACKEND
- id: "login_03"
location: BACKEND
defaults:
run-as: PLAYER
execute:
- id: "CURRENT_SERVER"
location: VELOCITY
server:
target-required: false
schedule-online: false
timeout: 5s
delay: 0s
cooldown: 0s
args: []
commands:
- command: "skyblock"
Activity
[-][BUG} Multi Proxy[/-][+][BUG] Multi Proxy[/+]objz commentedon Feb 22, 2026
Well, your idea is not bad, but it creates more issues than it solves:
Also, this would basically change the whole architecture of the plugin. At that point I could just rewrite it completely with these heavy changes.
So I will implement proper Redis support instead. That means: WebSocket can be fully replaced by a Redis instance, but Redis mode is not enabled by default. But thanks for your issue