Description:
Hello!
I’d like to request a feature related to mute handling in Plasmo Voice when using a proxy.
Problem
Currently, when a player is muted, the mute applies only to the backend server they are connected to.
If the network uses a proxy (BungeeCord or Velocity), the player can still speak on other backend servers after switching.
This behavior makes moderation on multi-server networks inconvenient, as mutes are expected to be global across the proxy, not server-specific.
Expected behavior
If the server is running behind BungeeCord or Velocity, mutes should be handled on the proxy level, so that:
- A muted player is muted on all backend servers
- Switching servers does not remove or bypass the mute
- The mute state is synchronized across the entire proxy network
Suggested implementation (optional idea)
- Implement proxy-side mute storage and synchronization
- Detect proxy environment (BungeeCord / Velocity)
- Apply and check mute status globally instead of per-backend
Why this is important
- Improves moderation consistency
- Prevents mute bypass via server switching
- Essential for large networks with multiple backend servers
Description:
Hello!
I’d like to request a feature related to mute handling in Plasmo Voice when using a proxy.
Problem
Currently, when a player is muted, the mute applies only to the backend server they are connected to.
If the network uses a proxy (BungeeCord or Velocity), the player can still speak on other backend servers after switching.
This behavior makes moderation on multi-server networks inconvenient, as mutes are expected to be global across the proxy, not server-specific.
Expected behavior
If the server is running behind BungeeCord or Velocity, mutes should be handled on the proxy level, so that:
Suggested implementation (optional idea)
Why this is important