ModernChatInjector

Minecraft 版本： 1.8.8 1.8.9 1.9 1.9.1 1.9.2 1.9.3 1.9.4 1.10 1.10.1 1.10.2 1.11 1.11.1 1.11.2 1.12 1.12.1 1.12.2 1.13 1.13.1 1.13.2 1.14 1.14.1 1.14.2 1.14.3 1.14.4 1.15 1.15.1 1.15.2 1.16 1.16.1 1.16.2 1.16.3 1.16.4 1.16.5 1.17 1.17.1 1.18 1.18.1 1.18.2 1.19 1.19.1 1.19.2 1.19.3 1.19.4 1.20 1.20.1 1.20.2 1.20.3 1.20.4 1.20.5 1.20.6 1.21 1.21.1 1.21.2 1.21.3 1.21.4 1.21.5 1.21.6 1.21.7 1.21.8 1.21.9 1.21.10 1.21.11 26.1 26.1.1 26.1.2 26.2

平台： bukkit paper spigot

标签： social utility

ModernChatInjector

A drop-in replacement for ChatInjector, now with built-in support for EssentialsX Chat 2.21.1+, as well as limited support for older
versions.

Usage

Install ModernChatInjector alongside PlaceholderAPI, any expansions you need, and your chat formatter of choice.
Then, add PlaceholderAPI placeholders within your chat formatting plugin using the following syntax:
{placeholder_name}.

Note that you need to use { and } around the placeholders, not % symbols like you might expect!

How does it work?

On EssentialsX 2.20.0 and above, ModernChatInjector hooks EssentialsX Chat's own chat events to ensure PlaceholderAPI
placeholders are injected into the message format when local/global chat is enabled.
This is necessary as the previous versions of ChatInjector relied on Bukkit events and protocol hacks, which aren't
fully compatible with current versions of EssentialsX Chat or Paper chat events.

If EssentialsX Chat isn't installed or if you're running older versions of Spigot or Paper, this plugin will fall back
to hooking Bukkit's AsyncPlayerChatEvent (as ChatInjector does), ensuring compatibility with other legacy chat
formatters.

Why isn't this built into EssentialsX Chat?

This provides support for PlaceholderAPI in "legacy" style chat formatting plugins, like EssentialsX Chat and
VaultChatFormatter, in the same way ChatInjector used to work.

We're planning a larger overhaul of EssentialsX Chat in a future version, which will include support for external
placeholders. Until that's ready, we don't want to guarantee support for a specific PAPI format that could change in the
future, as all server owners would then need to reconfigure their chat formats a second time.