Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 3 months ago
Updated 3 days ago
All versions
2.2.0+mc26.2-neoforge
Release
Visual Creative Tab Editor 2.2.0 - 26.2 NeoForgelast week 8
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
English
- Adds automatic Bedrock-style item groups with distinct group and member cells and lower-right expand/collapse markers. Grouping is enabled by default and can be disabled in
config/visual_creative_tab_editor/client.json. - Adds group creation, names, icons, membership editing and whole-group dragging through the existing long-press editor. Group definitions use layout saving, server synchronization and undo history.
- Adds a Groups control panel for creating, editing and deleting groups and adding or removing members. Deleting a group keeps its items.
- Refreshes only creative-tab resources when initializing the generated world packs.
- Keeps NeoForge's fixed system tabs out of ordinary tab pages.
- Preserves native empty display slots used by section banners and aligns Propulsion's banners with item grouping and scrolling.
- Closing a creative inventory without an active edit preview no longer rebuilds tab contents and the search collection.
中文
- 新增基岩版风格的同类物品自动分组,使用独立组头、成员底色及右下角展开/折叠标记。默认开启,可在
config/visual_creative_tab_editor/client.json关闭。 - 在原有长按编辑器中新增分组创建、名称与图标修改、成员调整及整组拖动,沿用布局保存、服务端同步和撤销记录。
- 新增“物品组”面板,可新建、编辑、删除物品组及移入、移出成员。删除物品组时保留其中的物品。
- 初始化世界生成数据包时只刷新创造标签资源。
- NeoForge 的固定系统标签不再进入普通分页。
- 保留原生分区标题使用的空槽,并同步推进工程分区标题与物品分组、滚动的位置。
- 关闭创造物品栏时,没有活动编辑预览就不再重建标签内容与搜索集合。
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:2qCrg2p4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wyfx33ZJ:2qCrg2p4"
}

