Links
Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 2 hours ago
All versions
2.3.0+26.2-neoforge
Release
Chat Upgrade 2.3.02 weeks ago 19
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client-side
Client and server
Changes
- 增强:引入动画支持以提升聊天界面交互体验 (6c365e0a269602d93ecded1b0ec806b3361653ed)
- 增强:添加语音消息功能和快捷键支持 (ff8e72f19a172648bc1f04e0c0c91d5aedc8109c)
- 增强:添加聊天历史功能以支持消息记录 (dffaabcc9ae103186b16b436d0fd7ff37f7c17b9)
- 增强:添加屏幕边距功能以优化聊天面板布局 (74ddc71f5b1a685397a335e5e4436f0361413e79)
- 增强:实现私聊消息处理和附件支持 (ba26e8f2edca24621c3c481670d56122b1a64e2a)
- 功能:添加私聊功能和消息分组支持 (905d309711cbd2543fe0dfdbc5ce3ac15ef42193)
- 修复:修复表情包占位宽度异常和gif解析处理问题 (8b2a9ebd127b839d278d34aadc49948d6b3339be)
- 修复:修复缺失部分消息的问题 (356be79b57a876c8102bd813fdfefb36a5d3d6f9)
- 提醒:添加艾特和提醒功能 (e8537fee02ed1396070269f9f043fb3e13cf74fe)
- 界面:调整媒体卡片UI,添加资料页 (c4f1582500e664478dee6181aef0cf0858f1acd7)
- 维护:补齐源码文件末尾换行 (0fb584d18ac3b10d05e0ae398855c727afa4b0ad)
- 界面:添加紧凑媒体卡片支持,优化富媒体消息布局和交互逻辑 (cc25072ae46fc083e83ae02ddd005d2daadfa2f1)
- 优化:调整界面和修复文件选择器 (54180ab3bdb00e82041a8bfbc002d7c82fec7258)
- 优化:优化和调整布局 (17b476ae4ccb7b9ee6dea9bb03fb7838be0fee9f)
- 优化:重构聊天面板输入和外观配置,增强 TAKEOVER 模式下的输入框和消息渲染逻辑,支持自动高度和消息背景设置。移除冗余代码,简化右键菜单和悬停操作,确保消息交互一致性。 (f16db590808c8ef6e8647fad34aeb2a2c549b958)
- 重构:重做聊天外观配置和添加配置界面 (a37414fd55e51ba1d1576932ddf01117d8e0254f)
- 修复:ChatScreenRichInputMixin 只暴露“尝试更新附件拖拽”操作,统一容器路径负责事件排序与消费。该操作会自行校验左键、接管模式、附件状态和 ATTACHMENT_TRAY 所有权 (7b016404fd3f54bfb0876ff7a13a6e7375122de8)
- 修正:隔离兼容链路并补齐身份渲染 (89978adf8ae52323b81a47f5eebbfb13aa982206)
- 接管:完成完整聊天面板输入与统一交互基础 (bdfed449780b6ed7fcf852f84fa864cf51ff8541)
- 交互:实现类型化动作、右键菜单、文本选择与统一拖拽手势状态机 (571a5e02dd05b557f04f018d80e8157bc820f7d0)
- 主题:建立统一场景树和三套共享渲染内核的运行时主题 (6b19488f070d4aa12ccbaeafa93a0055a22df55a)
- 更新:实现消息分类、身份解析、默认头像和主题相关分组投影 (b5dbb0bac05c76455ef48bcb0305f9768eccfd18)
- 更新:升级消息/作者领域模型与回复、撤回增强协议及服务端权限校验 (662782c787a117f1a31d22481e91fc5700cdd424)
- 更新:建立 TAKEOVER 完整 surface 所有权、面板状态和持久化几何配置 (db66011ee2e474c32ab2dd867560800590702140)
- 去掉自动派生的versions/*/gradle.properties (0cdde3811988bdca2f08f67c57b262ff8f67340b)
- docs: 更新 README 和文档以反映媒体上传和命令的变化 (4694a43cc538a43e802b749dc1692527744f42c4)
- remove: 删除tool文件 (417a1a047bfc76f39986d097a0ff7aa4921ff24b)
- feat: 增强发布目标的构建配置 (b9e9f8e120efcb1cf2d7a0c233466cafb46c8a0b)
- feat: 增强聊天界面表情预览与渲染逻辑 (b419fe0c2cd031d21c1bcb827832bf184a2638f0)
- feat: 添加表情支持与管理功能 (81ced5631fce51ffda15edbc9186c40c5614865d)
- feat: 优化文件选择逻辑 (f873a95257aeb4cc736e165a78856cf7c075fbb0)
- feat: 更新构建工作流以支持目标和版本管理 (7401d8a63fb8e1ade64f2290eab28f751795594d)
- 更改表述 (a3f746f10d203196450ce895121b5f8a27ef8d22)
- 重构架构 (9da580c008807c53bc0c4aed343e8b6d92f03c49)
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:Af5aD8GN:Sng4tVP5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Af5aD8GN:Sng4tVP5"
}

