Tags
Creators
Details
Licensed LGPL-3.0-only
Published 6 months ago
Updated last month
All versions
1.4.0
Release
華麥小幫手 HwamaiHelper 1.4.0last month 20
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Changes
HwamaiHelper 1.4.0
重要 / Important: 此版本開始必須安裝 MaLiLib
0.29.2或更新版本。 Starting with this release, MaLiLib0.29.2or newer is required.
中文更新說明
新增與調整
- 將主設定介面、自訂指令、暱稱編輯器及快捷鍵系統遷移至 MaLiLib。
- 改用 MaLiLib 管理設定選項與快捷鍵,提高介面與 Minecraft
26.2的相容性。 - 更新創造模式物品欄英文搜尋功能的 Minecraft
26.2相容處理。 - 更新安裝文件,明確標示 MaLiLib 為必要依賴。
修正
- 修正「自訂指令」與「暱稱編輯器」來回切換後,按下「返回設定」需要重複返回多層的問題。
- 現在不論在兩個頁面之間切換多少次,都能直接返回設定主畫面。
移除
- 移除「總是套用伺服器材質包」設定。
- 移除相關的材質包初始化、連線檢查及每 Tick 處理邏輯。
相容性與必要依賴
- Minecraft:
26.2 - Fabric Loader:
0.19.3+ - Fabric API:
0.154.0+26.2 - MaLiLib:
0.29.2+(必要) - Java:
25 - 執行環境:用戶端
English Changelog
Added and Changed
- Migrated the main configuration screen, custom commands, nickname editor, and keybind system to MaLiLib.
- Configuration options and keybinds are now managed through MaLiLib for improved Minecraft
26.2compatibility. - Updated the Creative inventory English search implementation for Minecraft
26.2. - Updated the installation documentation to clearly identify MaLiLib as a required dependency.
Fixed
- Fixed an issue where repeatedly switching between Custom Commands and the Nickname Editor created multiple navigation layers.
- The Return to Settings button now immediately returns to the main settings screen, regardless of how many times the two pages were opened.
Removed
- Removed the Always Apply Server Resource Pack option.
- Removed the related resource-pack initialization, connection checks, and per-tick processing logic.
Compatibility and Requirements
- Minecraft:
26.2 - Fabric Loader:
0.19.3+ - Fabric API:
0.154.0+26.2 - MaLiLib:
0.29.2+(required) - Java:
25 - Environment: Client-side
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:wUerqbhK:JSKmnzOI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wUerqbhK:JSKmnzOI"
}

