Proxy Support

Channels, private messages, nicks, warning points, /list, and tab-completion all work across proxy.

Supported Proxies

• BungeeCord/Waterfall — Install BungeeControl on the proxy
• Velocity — Install VelocityControl on the proxy
• RedisBungee (or forks) — Detected automatically

Keep ChatControl on your Bukkit servers.

Setup

Warning

MySQL database is required for proxy.

1. Install the proxy addon (above)
2. Enable database in mysql.yml and network in proxy.yml (both in plugins/ChatControlRed)
3. Set a unique Server_Name in proxy.yml for each server — must exactly match (case-sensitive) the name in your proxy config:

servers:
  survival:
    motd: 'Survival Server'
    address: localhost:25566
    restricted: false

Make sure server names match exactly with Server_Name in ChatControl's proxy.yml.

Velocity's velocity.toml:

[servers]  
  survival = "127.0.0.1:25565"

4. Restart. Proxy features are now active.

Tip

Some proxy features must be manually enabled in ChatControl's settings.yml.

Proxy Commands

• /vcreload / /bcreload — Reloads proxy-side config (use /chc reload for Bukkit-side)
• /me — Network-wide formatted message (configure in proxy settings.yml Me section)
• /say / /broadcast — Network-wide broadcast (configure in Say section)

Warning

If enabling /say or /me on proxy, disable or rename the same command in ChatControl on Bukkit servers.

Server Switch Messages

On proxy networks, you can show messages when a player switches between servers. Configure this in the messages/switch.rs file on the proxy side.

Switch messages use the same syntax as other messages (see Messages), with additional variables:

• {from_server} — The server the player is switching from.
• {to_server} — The server the player is switching to.

Players with the chatcontrol.silence.switch permission will have their switch message hidden.

To enable switch messages, add switch to Messages.Apply_On in the proxy settings.yml:

Messages:
  Apply_On: [join, quit, switch]

Forwarding Commands

Use /chc forward to send commands from a Bukkit server to the proxy or another server:

/chc forward proxy <command>
/chc forward <server_name> <command>

Security Restriction

By default, forwarding commands from the proxy console is disabled for security reasons. To enable it, set Enable_Forward_Command to true in the proxy settings.yml. This allows only the proxy console (not players) to forward commands to Bukkit servers.

Chat Forwarding

For servers on your network that do not have ChatControl installed, you can enable basic chat forwarding in the proxy settings.yml under Chat_Forwarding. This only relays raw chat messages — no filtering or formatting is applied on those servers.

Chat_Forwarding:
  Enabled: true
  To_Servers:
    - "minigame1"
  From_Servers:
    - "minigame1"

Clusters

You can group servers into clusters to limit data transmission (tab-completion, messages) only within the same cluster. Servers not listed in any cluster will be placed into a "global" cluster automatically.

Clusters:
  Enabled: true
  List:
    gameplay:
      - factions
      - pvp
    lobbies:
      - hub1
      - hub2

Redis Integration

If you have RedisBungee (or a fork like RedisBungee-Velocity) installed, we automatically detect it and redirect messages over Redis. You can disable this with Redis_Integration: false in the proxy settings.yml.

Proxy Settings Reference

The proxy settings.yml (inside your VelocityControl or BungeeControl plugins folder) contains these sections:

Section	Description
Server_Aliases	Map server names to display aliases
Messages	Enable join/quit/switch messages, set prefixes, configure ignored servers
Tab_Complete	Filter proxy command tab-completion suggestions
Chat_Forwarding	Relay chat for servers without ChatControl
Clusters	Group servers for scoped data
Integration.Parties	Party and Friends / Parties plugin integration
Say	Configure the /say broadcast command
Me	Configure the /me broadcast command
Enable_Forward_Command	Allow console forwarding from proxy
Make_Chat_Links_Clickable	Auto-clickable URLs on proxy
Redis_Integration	Toggle RedisBungee support
Debug	Debug categories: proxy, operator, redis, player-message

Proxy Permissions

Permission	Description
chatcontrol.silence.join	Hide join messages when player joins on another server
chatcontrol.silence.leave	Hide leave messages when player leaves from another server
chatcontrol.silence.switch	Hide switch messages when player changes servers
chatcontrol.bypass.silence.join	Still see hidden join messages
chatcontrol.bypass.silence.leave	Still see hidden leave messages
chatcontrol.bypass.silence.switch	Still see hidden switch messages
chatcontrol.command.forward	Use /chc forward (must be assigned on proxy too)

Troubleshooting

• Errors on server stop: Pending database operations. Harmless — ensure MySQL is responsive.
• Duplicate messages: Ensure only ChatControl handles join/quit/switch. Disable in the other plugin or remove from Messages.Apply_On.
• Tab-completion issues: Check Tab_Complete section in proxy settings.yml.
• Cannot forward commands: Set Enable_Forward_Command: true in proxy settings.yml (disabled by default for security).
• Messages missing on a server: Check Messages.Ignored_Servers and verify Server_Name matches (case-sensitive).

Additional Features

You can also forward commands to proxy using "then proxyconsole" in Rules and Messages and "/chc forward" command.

Proxy Command Rules

You can filter, block, and act on commands executed at the proxy level using the rules/command.rs file inside your BungeeControl or VelocityControl plugins folder. This works just like Bukkit-side Rules but runs on the proxy before commands reach any server.

The proxy command rules use the same syntax as Bukkit rules. Place rules in the rules/command.rs file inside the proxy plugin's data folder.

Available Operators

Operator	Description
match <regex>	Match commands against a regular expression
name <name>	Name this rule for identification
require sender perm <perm> [message]	Require sender to have a permission
require sender server <server>	Require sender to be on a specific server
require sender script <script>	Require a JavaScript condition
ignore sender perm <perm>	Skip rule if sender has this permission
ignore sender server <server>	Skip rule if sender is on this server
ignore sender script <script>	Skip rule if JavaScript condition is true
require perm <perm>	Shorthand for require sender perm
ignore perm <perm>	Shorthand for ignore sender perm
require playedbefore	Only match if the sender has played before. Requires Register_Joining_Players: true in settings.yml
ignore playedbefore	Skip rule if the sender has played before. Requires Register_Joining_Players: true in settings.yml
strip colors <true/false>	Strip colors before matching
strip accents <true/false>	Strip accents before matching
then deny	Block the command
then warn <message>	Send a warning message to the sender
then command <command>	Run a command as the sender
then proxy <command>	Run a command on the proxy console
then log <message>	Log a message to console
then kick <message>	Kick the player
then discord <channel> <message>	Send a message to Discord
then write <file> <message>	Write to a log file
delay <time> [message]	Global cooldown before running this rule again
player delay <time> [message]	Per-player cooldown before running this rule again
then abort	Stop processing further rules
disabled	Temporarily disable this rule

Example: Block /op on Proxy

match ^/op\b
ignore perm chatcontrol.bypass.rules
name /op
then warn &cThis command is not allowed.
then deny

Example: Audit Punishment Commands

match ^/(ban|mute|kick|warn)\b
name punishment-audit
then log {player} executed proxy command: {original_message}

Example: Restrict Command to Specific Server

match ^/creative\b
require sender server creative
then warn &cYou can only use this on the creative server.
then deny