Geyser Cross Chat
让通过 Geyser 服务器加入的基岩版玩家聊天,而无需为 Java 版玩家关闭安全聊天。
通过 Geyser + Floodgate 加入的基岩版玩家没有 Mojang 聊天签名密钥。当 enforce-secure-profile=true 时,原版游戏会因“缺少配置文件公钥”而拒绝他们的聊天消息。通常的解决方法是将 enforce-secure-profile=false。这虽然可行,但会导致所有 Java 版玩家收到“聊天消息无法验证”的警告,并且服务器不再要求对聊天进行签名。
Geyser Cross Chat 在保持强制签名的同时,以未签名方式中继基岩版的消息。
- Java 版聊天保持已签名且受强制执行。Java 版玩家没有任何变化。
- 基岩版聊天正常工作。他们的消息显示效果与其他玩家无异。
- 你的聊天格式依然生效。中继的消息会经过正常的 Paper 聊天事件,因此聊天格式化器、过滤器和禁言插件会将它们视为普通消息处理。
- 基岩版的
/msg、/tell、/w、/me、/say 和 /teammsg 命令也能正常工作。
- 不会导致踢出。基岩版聊天数据包永远不会被丢弃,因此服务器的消息确认与 Geyser 保持同步,没有人会因为“聊天验证失败”而被踢出。
工作原理
- 基岩版玩家发送聊天。数据包原样通过,以便原版游戏仍能处理其确认信息。
- 原版游戏因缺少配置文件密钥而拒绝该消息。GeyserCrossChat 向玩家隐藏此错误。
- 文本作为普通聊天事件再次发送,结果以未签名形式交付。
要求
- Paper 26.2+
- Floodgate
- PacketEvents
server.properties 中设置 enforce-secure-profile=true。如果关闭此项,插件将处于空闲状态,因为原版游戏已经接受基岩版聊天。
配置
# system: 纯系统消息,由你的聊天插件格式化。
# 始终显示,即使对将聊天设置为“仅命令”的玩家也是如此。
# disguised: 原版 /say 风格的数据包。尊重每个玩家的聊天设置,
# 但使用原版的 "<name> message" 外观,而非你的聊天格式。
delivery: system
# 必须对消息参数进行签名的原版命令。
signed-commands: [msg, tell, w, me, say, teammsg, tm]
注意事项
- 控制台仍会为每条基岩版消息记录
Failed to update secure chat state for <player>。该行来自原版游戏在拒绝消息时的日志输出,发生在 GeyserCrossChat 中继之前。
- 中继的消息是未签名的,因此像任何系统消息一样,无法通过 Mojang 的聊天举报系统进行举报。
Geyser Cross Chat 与 GeyserMC 无关联。
Geyser Cross Chat
Let Bedrock players chat on your Geyser server without turning off secure chat for Java players.
Bedrock players joining through Geyser + Floodgate have no Mojang chat-signing key. With
enforce-secure-profile=true, vanilla refuses their chat with "Chat disabled due to missing profile
public key". The usual fix is to set enforce-secure-profile=false. That works, but every Java player
then gets a "Chat messages can't be verified" warning, and the server stops requiring signed chat.
Geyser Cross Chat keeps enforcement on and relays Bedrock messages unsigned instead.
- Java chat stays signed and enforced. Nothing changes for Java players.
- Bedrock chat just works. Their messages show up like everyone else's.
- Your chat format still applies. Relayed messages go through the normal Paper chat event, so
chat formatters, filters and mute plugins treat them like any other message.
- Bedrock
/msg, /tell, /w, /me, /say and /teammsg work too.
- No kicks. Bedrock chat packets are never dropped, so the server's message acknowledgements
stay in sync with Geyser and nobody gets kicked for "chat validation failure".
How it works
- A Bedrock player chats. The packet goes through untouched, so vanilla still processes its
acknowledgements.
- Vanilla refuses it for lacking a profile key. GeyserCrossChat hides that error from the player.
- The text is sent again as a normal chat event, and the result is delivered unsigned.
Requirements
- Paper 26.2+
- Floodgate
- PacketEvents
enforce-secure-profile=true in server.properties. With it off, the plugin stays idle, because
vanilla already accepts Bedrock chat.
Config
# system: a plain system message, formatted by your chat plugins.
# Always shown, even to players who set chat to "Commands only".
# disguised: the vanilla /say-style packet. Respects each player's chat settings,
# but uses the vanilla "<name> message" look instead of your chat format.
delivery: system
# Vanilla commands whose message argument must be signed.
signed-commands: [msg, tell, w, me, say, teammsg, tm]
Notes
- The console still logs
Failed to update secure chat state for <player> for each Bedrock message.
That line comes from vanilla when it refuses the message, before GeyserCrossChat relays it.
- Relayed messages are unsigned, so like any system message they can't be reported through
Mojang's chat reporting.
Geyser Cross Chat is not affiliated with GeyserMC.
评论 0
登录后参与评分
还没有评论,来抢沙发吧