Proxy
Used for synchronizing multiple servers using BungeeCord/Velocity or Redis
INFO
This works on any platform where FlectonePulse is available. For Bukkit and Fabric servers.
⚙️ Setting
📂 Path config.yml → proxy
⚖️ Default
proxy:
clusters: []
bungeecord: false
velocity: false
redis:
enable: false
host: "127.0.0.1"
port: 6379
ssl: false
user: ""
password: ""clusters
List of clusters the server should connect to. Only used when proxy mode is enabled. If the list is empty, the server receives all messages from other servers
HOW TO USE?
Enter the cluster name on all servers where the message should be received and sent
clusters:
- "test_cluster"This way servers connect with each other and messages will only be between these servers
bungeecord
Enables connection with BungeeCord
HOW TO SET UP?
- Place the
FlectonePulse-bukkit.jarfile in thepluginsfolder onBungeeCord. Even if you have a Fabric server, you need to useFlectonePulse-bukkit.jaronBungeeCord - On all servers that should connect with
BungeeCord, enablebungeecord: truein FlectonePulse - The selected database must be
MySQLorPostgreSQL(i.e., server-based)
velocity
Enables connection with Velocity
HOW TO SET UP?
- Place the
FlectonePulse-bukkit.jarfile in thepluginsfolder onVelocity. Even if you have a Fabric server, you need to useFlectonePulse-bukkit.jaronVelocity - On all servers that should connect with
Velocity, enablevelocity: truein FlectonePulse - The selected database must be
MySQLorPostgreSQL(i.e., server-based)
redis
Used for communication between different servers. For user and password you can use environment variables, for example ${VALUE}
