Channels
format, scope, rules
One suite, not ten plugins
The complete communication suite for Minecraft servers.
Public chat, channels, private messages, pings, ChatItems, bubbles, bridges, moderation, locales, and network support designed as one coherent system.
- Paper 1.21.11
- Velocity networks
- MiniMessage
- Discord + Telegram
Communication Suite Preview
channel aware
Paper + Velocity
Pings
sound + actionbar
Bridges
Discord + Telegram
Paper
Velocity
Paper
ChatItems
held items, inventory, armor
Latest release
CoreChatX 2026.2.4 tightens Discord console logs, private messages, and proxy routing.
The 2026.2.4 release adds batched Discord console logs, stricter nickname controls, per-event Discord mirror configuration, ChatItem previews in private messages, and fixes for Discord inbound prefixes, expired item inspections, and Velocity console replies.
Discord console
Console logs are batched instead of spammed
Paper and Velocity can edit the latest bot log message until the configured size limit is reached, split after other users post in the channel, and format each line with configurable monospace and timestamp settings.
Private messages
ChatItems now work in /msg and /reply
Configured ChatItem tokens such as [i], [item] and
[inv] are rendered in private messages, including cross-server
preview routing through Velocity.
Proxy bridge
Discord routing waits for the right data
Discord inbound messages now wait for async LuckPerms data before delivery, Velocity event mirrors can be configured per event, and console command replies render translatable Velocity output as readable text.
Core feature set
Five pillars of a cleaner server communication stack.
CoreChatX keeps chat-related features in the same system, so formatting, privacy, routing, rich interactions, and bridges can agree with each other.
Core Chat System
A polished public chat foundation with global, local, staff, and network-wide communication, join, quit, and first-join messages, plus message cleanup and sanitization before rich components reach players.
Smart Channels
Global, local, staff, network-wide, role-based, and custom channels can define permissions, formats, scope, mentions, ChatItems, chat bubbles, and bridge export rules from one centralized channel model.
Mentions & Custom Pings
Player mentions, @Player behavior, exact-name matches, custom ping triggers, sound and actionbar notifications, per-player toggles, staff-friendly rules, and cross-server awareness built into the message flow.
Interactive ChatItems
Clickable previews for held items, shulkers, armor, hotbar, inventory, and ender chest contents. In network mode, lightweight snapshot references can retrieve previews on demand through Velocity, while Discord bridge output can attach rendered inventory images and interactive single-item inspection menus.
External Bridges
Optional Discord and Telegram bridges support inbound and outbound messages, per-channel routing, bridge targets, per-channel bridge format overrides, PlaceholderAPI-aware Discord output, role-aware inbound messages, and safe message handling.
Rich Chat Formatting
Kyori Adventure and MiniMessage support lets trusted server templates use colors, gradients, hover text, click actions, suggested commands, copy actions, and reusable component patterns across chat surfaces.
Private Messaging & Privacy
Direct messages, replies, social spy, ignore controls, PM toggle, delivery feedback, staff bypass rules, and cross-server private messages live inside the same communication and privacy model.
Built-in Moderation
Everyday chat controls include mute, unmute, global chat mute, clear chat, anti-repeat, anti-caps, word filtering, staff bypass permissions, and moderation behavior that works inside the chat layer.
Interactive Keywords
Tokens such as [discord], [rules], [store], [vote], and [map] can become clickable, permission-gated MiniMessage components with hover text, commands, URLs, copied text, and channel restrictions.
Chat Bubbles
Optional overhead bubbles display processed chat above players with channel and world rules, player toggles, sneaking and invisibility checks, duration, wrapping, stacking, distance limits, and cleanup.
Player Controls
Players can manage communication preferences through settings, ping toggles, PM toggle, channel switching, bubble visibility, locale selection, and ignore controls that can follow backend switches.
Locale Support
Per-player locale selection, locale override files, and fallback behavior help multilingual communities keep player-facing wording consistent with the server's own voice and expectations.
Velocity Network Support
Network mode can carry group-isolated chat, group-local cross-server PMs, player settings, global completions, TAB entries, mention metadata, custom ping metadata, and ChatItem preview references across matching backends.
Paper & Velocity Support
CoreChatX targets Paper 1.21.11 backends and Velocity proxy networks with separate Paper and Velocity runtime jars. The shared common module is internal and is not installed directly.
MiniMessage & PlaceholderAPI
Trusted server-controlled templates can combine MiniMessage with PlaceholderAPI where installed and enabled. Legacy color codes returned by placeholders are converted before rendering, while raw player chat bodies do not parse PlaceholderAPI.
Why CoreChatX
One coherent system for the messages players actually use.
Server chat becomes harder to maintain when every feature comes from a different plugin. CoreChatX brings the communication experience into one visual language, one permission model, one player settings flow, and one network-aware layer.
One Communication Layer
Public chat, PMs, channels, pings, bridges, moderation, rich interactions, and player controls are managed as parts of the same product instead of a scattered plugin stack.
Feature-Aware Channels
Channels can affect formatting, mentions, ChatItems, bubbles, bridge export, permissions, and delivery scope, so routing decisions stay clear and consistent.
Built for Real Networks
Standalone Paper servers and Velocity networks are both supported, with network-aware chat, synced settings, group-local cross-server PMs, global completions, and remote ChatItem access.
Setup and compatibility
Clear modes for standalone servers and networks.
CoreChatX ships separate runtime jars for Paper and Velocity. Choose the setup that matches your server shape, then use the configuration guide for exact keys and restart boundaries.
Standalone
Paper Server
Install the Paper jar on a single Paper backend. Network transport stays inactive and server communication stays focused on that backend.
- Paper 1.21.11 target
- No Velocity module required
- Single-server communication stack
Network
Velocity Network
Install the Paper jar on participating backends and the Velocity jar on the proxy.
Backends use unique server ids and join the CoreChatX group matching their Paper
deployment.network-channel.
- Single or comma-separated Velocity channels
- Group-local cross-server PM routing
- Synced communication settings
Paper standalone
Velocity ready
Separate runtime jars
Resources
Docs that help you configure the system, not guess at it.
Hub
Documentation Hub
Structured entrypoint for product overview, installation, configuration, FAQ, and operational notes.
ProductProduct Overview
A complete product view for server owners, including features, commands, admin experience, verified state, and future direction.
SetupInstallation Guide
Standalone Paper and Velocity network installation paths, artifact rules, and validation steps.
ConfigConfiguration Reference
Complete config file reference with defaults, missing-key synchronization, runtime data, reload rules, and troubleshooting.
FAQComplete FAQ
Full FAQ for setup, formatting, channels, bridges, storage, and common problems.
OpsTroubleshooting
Startup, reload, network routing, bridge, PlaceholderAPI, ChatItems, bubble, and data-file checks.
FAQ preview
Answers before you start configuring.
These answers are intentionally short. Use the FAQ and configuration guide when you need exact file names, keys, and operational details.
Do I need Velocity?
No. CoreChatX works on standalone Paper. Velocity is only needed for cross-backend features such as network channels, group-local cross-server PMs, synced settings, global completions, proxy join/leave, and remote ChatItem previews.
Does CoreChatX work on standalone Paper?
Yes. Install the Paper jar on the Paper server and use STANDALONE mode. The Velocity jar is not required for a single backend setup.
Does it support PlaceholderAPI?
Yes, where PlaceholderAPI is installed, enabled, and used inside supported server-controlled templates. Raw player-written messages do not parse PlaceholderAPI.
Does it support Discord and Telegram?
Yes. Both bridges are optional and support inbound and outbound messages, per-channel format overrides, and explicit routing when configured. Telegram also supports forum topic routing through Bot API long polling.
Are ChatItems supported across a network?
Yes. In network mode, rendered chat carries lightweight snapshot references and retrieves the needed preview on demand through Velocity.
Where do I configure the plugin?
Paper config lives under plugins/CoreChatX/. Velocity config lives under plugins/corechatx/. Runtime data files are live state and should be backed up before manual edits.
Also try
More CoreX plugins for the same server stack.
Each project stays focused, so you can add only the systems your Paper server actually needs.
Armor
CoreArmorX
Vanilla+ armor upgrade paths, netherite skins, metadata-safe conversions, and YAML control.
Tools
CoreToolsX
Vanilla+ tool upgrade paths, material skins, protected crafting, and admin-controlled recipes.
Cases
CoreCaseX
Structured player reports, staff triage, evidence, replies, notes, and resolution workflows.
Extraction
CoreExtractionX
YAML-driven block extraction, block replacement, natural drops, and configurable extra item drops.
Ready to upgrade server communication?
One suite. One system. Cleaner server chat.
Build a more consistent communication layer for players and a more manageable setup for admins.