Links
Creators
Details
1.0.6
Compatibility
Required content
Changes
Changelog
All notable changes to this project will be documented in this file.
v1.0.6 - The Feedback & UI Update
Note: While marked as compatible with Minecraft 1.20.1 - 1.20.4, this version has only been fully tested on 1.20.1.
✨ Added
- Sound Feedback for Chat Clicks: When you copy an item's information by clicking the
[Copy]or[Copy All]buttons in the chat, a confirmation sound will now play. - Enhanced Key Recorder: The screen for recording a new hotkey now provides immediate feedback:
- It visually displays the key or key combination as you press it.
- It plays a sound to confirm a successful recording.
- The "Confirm" button is now disabled until a valid key is pressed.
🐛 Fixed
- Config Screen UI Overlap: The "Record" and "Clear" hotkey buttons in the configuration screen no longer overlap with the "Save" and "Cancel" buttons. The entire hotkey configuration is now neatly integrated into the settings list.
♻️ Changed
- Complete UI Refactor for Settings: The hotkey configuration interface has been completely rewritten to use a proper custom entry within Cloth Config. This improves stability, correctly handles scrolling, and provides a much cleaner user experience.
- Version Compatibility: Marked as compatible with Minecraft versions
1.20.1through1.20.4.
v1.0.6 - 反馈与UI更新
注意:尽管已标记为与 Minecraft 1.20.1 - 1.20.4 兼容,但此版本仅在 1.20.1 上进行过全面测试。
✨ 新增
- 聊天点击声音反馈:现在,当您通过点击聊天中的
[复制]或[复制全部]按钮来复制物品信息时,会播放确认音效。 - 增强的按键记录器:用于录制新热键的屏幕现在提供即时反馈:
- 在您按下按键时,它会立刻显示出您所按下的按键或组合键。
- 录制成功时会播放音效。
- “确认”按钮在录制到有效按键前将被禁用。
🐛 修复
- 配置界面UI重叠:配置屏幕中的“录制”和“清除”热键按钮不再与“保存”和“取消”按钮重叠。整个热键配置功能现已整齐地集成到设置列表中。
♻️ 变更
- 设置界面的完全UI重构:热键配置界面已完全重写,使用标准的 Cloth Config 自定义条目。这提高了稳定性,正确处理了滚动,并提供了更清晰的用户体验。
- 版本兼容性:标记为与 Minecraft
1.20.1至1.20.4版本兼容。
Previous versions are not documented in this changelog.
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:I3oaVHmR:JRfdLdim"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:I3oaVHmR:JRfdLdim"
}

