"one-way" - Unidirectional isolation. Messages FROM the isolated world stay INSIDE it (other worlds don't see them). Messages FROM normal worlds CAN be seen by players in isolated worlds. Private messages (/msg) are NOT blocked in this mode. Ideal for arenas where you want players to stay informed but keep their own chat private. isolation-mode: "one-way"

We recommend deleting and regenerating world-isolation.yml

QuickChat - Features Overview

🌐 Redis Cross-Server (Global Synchronization)

Config: redis.yml

QuickChat includes Redis support to connect all your servers (Lobby, Survival, Skyblock, etc.) in real-time, creating a unified chat system across your entire network.

Features

• Global Private Messaging
  Use /msg and /r across all servers.

• Global Tab Complete
  Auto-complete player names from the entire network.

• StaffChat Across Servers
  Staff members can communicate from any server.

• Global Public Chat (Optional)
  Sync chat between all servers.

• Server Tags
  Show the origin server in messages.
  Example: [Skyblock] Player -> You: Hello

Notes

• Fully asynchronous system.
• Automatic Redis reconnection if connection is lost.
• No impact on main server thread.

🌍 World Isolation System

Config: world-isolation.yml

Designed for servers running multiple worlds (e.g. Survival + PvP arenas).

Features

• Per-World Chat Isolation
  Players only see messages from their current world.

• Example
  If arena_pvp is isolated:

  • Players inside only see messages from that world.
  • No messages from Survival.
  • Survival players don’t see arena chat.

• Private Message Control
  Option to block /msg between isolated worlds and global worlds.

Use Cases

• PvP arenas
• Minigames
• Competitive environments

⚠️ Important

• Do NOT use Redis Cross-Server and World Isolation together on the same server.
• They are designed for opposite purposes.

Recommendation:
If you want full isolation, disable Redis in redis.yml for that server.

✔ Compatibility

• Spigot / Paper
• Multi-server networks (BungeeCord / Velocity)
• Redis supported environments

Command: /mutechat Silences or enables the global server chat.

Main Permission: quickchat.admin.mutechat Description: Allows muting and unmuting the global chat. ⚙ Default: OP (operators)

Bypass Permission: quickchat.bypass.mutechat Description: Allows a player to send messages even if the global chat is muted. ⚙ Default: OP (operators)

Command: /chatsettings Opens the player's personal settings menu.

Permission: quickchat.chatsettings Description: Allows opening the personal configuration menu (global chat and private messages).

Bypass Permission: quickchat.bypass.mutechat

⚙ Configuration: This permission can be configured in: chat-mute/player_settings.yml

Default: quickchat.chatsettings If left empty (""): the command will be accessible to all players.

We have implemented an option for those using plugins that rely on Paper's chat event instead of Spigot's (# Use Paper's AsyncChatEvent instead of Spigot's AsyncPlayerChatEvent).

You can enable it in the "event-priority" section inside the config.yml file.

If you prefer, you can also add the option manually:

use-paper-event: false

Make sure it is placed under event-priority:.

Example:

event-priority: use-paper-event: true

This is useful if you don’t want to create a new config file. With this option, full support for Paper is provided.

We have implemented a StaffChat system, completely isolated from DiscordSRV, meaning messages will be fully private for staff members who have the following permission: quickchat.staffchat.

The command to use this channel is /staffchat.

Additionally, we have implemented a BossBar announcement system, which you can use to display information such as your server IP or store.

We recommend reloading the config.yml and messages.yml files.

With this, we conclude the MySQL integration, which is now fully stable. Additionally, a startup error that occurred in some versions of Minecraft has been fixed. The update is completely optional, although it is always recommended.