QuickChat - Folia support and Redis v26.3

QuickChat - Features Overview

Redis Cross-Server (Global Synchronization)
Config:

Code:

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

Code:

/msg

and

Code:

/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:

Code:

[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:

Code:

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

Code:

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

Code:

/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 serve opposite purposes.

Recommendation:
Disable Redis in

Code:

redis.yml

if you want full isolation.

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.

We currently support SQLite and MySQL for storing data such as colors, styles, and ignored players.
I have tested everything and it appears to work 100% correctly. However, if you find any issues, please don’t hesitate to report them.

config.yml ------- the options were added in config.yml

We recommend making a copy of the file and generating a new one. Alternatively, you can generate a new file, copy the new section from it, and paste it into the existing file you already have on your server.

We have fixed an issue in the advanced color system. The system responsible for handling hexadecimal colors was not linked to the quickchat.colors permission, which allowed users without that permission to write using hexadecimal colors in chat.

This issue has now been fully resolved, and the permission is correctly enforced in both the advanced color system (hex) and the legacy color system.

We have fixed an issue with the mention system. When using a color from the color menu and mentioning a player, the notification was not being sent correctly. This issue has now been resolved, and mentions will notify properly.

We have fixed a typographical error in the chatcolors.yml file.

You must add an “R” to the following entry:

no-colors-pemission: ➝ no-colors-permission:

With this change, the message will work correctly after updating the file.

Additionally, we have added a new permission for styles:

quickchat.styles.all

This permission allows you to grant access to all styles in the color menu without needing to assign them one by one.