Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 3 months ago
Updated 3 days ago
All versions
2.3.0+mc1.20.1-forge
Release
Visual Creative Tab Editor 2.3.0 - 1.20.1 Forgelast week 60
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
2.3.0
English
- Add editable subcategories inside each creative tab. Left icon tabs select categories, show all items or show uncategorized items. Categories support names, icons, membership, ordering and deletion through the existing Save, Cancel and Undo workflow. Deleting a category keeps its items.
- Apply Ore styling to editor controls while retaining vanilla category tab textures. Join category tabs to the inventory frame and preserve native mod filter controls and their scrolling areas.
- Collapse tab and item drawers behind a small edge arrow by default. Book and chest buttons open the drawers; closing a drawer folds those buttons away.
- Add an editor button that disables or re-enables all item folding and saves the preference to
config/visual_creative_tab_editor/client.json. Existing group definitions are retained. - Fix creative-menu projection invalidation when other mods replace, filter or reorder the underlying item list.
- Preserve native mod filtering when cancelling an edit instead of selecting the same tab again and replacing its filtered contents.
- Place group expand/collapse markers in the upper-right corner during normal browsing and keep them separate from selection checkboxes while editing.
- Shared multiplayer layouts require the same mod version on both sides.
中文
- 新增创造标签页内的可编辑分类。左侧图标标签可切换分类、显示全部或显示未分类物品;支持名称、图标、成员、排序和删除,沿用保存、取消与撤销操作。删除分类保留物品。
- 编辑控件采用 Ore 样式,分类标签保留原版纹理并与物品栏边框连接;保留共装模组的原生筛选控件及其滚轮区域。
- 栏目和物品抽屉默认收起为贴边小箭头,展开后通过书本、箱子图标进入,关闭抽屉后重新收起入口。
- 编辑界面可一键关闭或重新开启全部物品折叠,并保存到
config/visual_creative_tab_editor/client.json;保留已有物品组定义。 - 修复其他模组替换、筛选或重排原生物品列表后,创造物品栏显示投影未及时失效的问题。
- 取消编辑时保留原生筛选结果,避免重复选择当前标签覆盖筛选后的内容。
- 普通浏览时将物品组展开、折叠标记放在右上角,编辑时与选择框错开。
- 联机共享布局时,客户端与服务端需使用相同模组版本。
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:wyfx33ZJ:SGRnMVtk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wyfx33ZJ:SGRnMVtk"
}

