All versions
1.0.9
Release
StepCraft 1.0.97 months ago 27
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Dedicated servers only
Changes
StepCraft Mod - Update Changelog
Release: Current update (Minecraft mod only)
Key Highlights
- Added UI title color code support (
&formatting like&f,&c, etc.) so custom menu titles no longer inherit default gray styling. - Added configurable chest GUI size (row count) per screen, including support for compact screens like Player Actions.
- Added support for
minecraft:hide_additional_tooltip={}so configured icons can hide vanilla/modded extra tooltip sections (stats, attributes, etc.). - Added step preview in the Steps icon lore so players can quickly see step info without always opening another screen.
- Added support for modded items in the icon selector (not limited to vanilla icons).
- Added hot reload support so config/UI updates can be reloaded without full server restart.
Commands Added/Updated
Reload
/stepcraft reload
Reloads StepCraft config/UI data live.
Steps Command Update
-
/stepcraft steps [username]
Opens the player step-history UI. -
Removed
/stepcraft today_steps.
UI Layout Commands (Admin)
/stepcraft ui_layout_config list_screens/stepcraft ui_layout_config list <screen>/stepcraft ui_layout_config set_slot <screen> <key> <0-53>/stepcraft ui_layout_config set_icon <screen> <key> <minecraft:item_id>/stepcraft ui_layout_config set_visible <screen> <key> <true|false>/stepcraft ui_layout_config reset <screen> [key]/stepcraft ui_layout_config editor <screen>
UI Editor Improvements
- Supports editing layout/position, icon, visibility, and name from in-game editor flow.
- Supports icon assignment from hotbar shortcuts.
- Supports searchable icon picker with modded-item results.
- Supports tooltip-hide behavior in editor flow (not command-only).
- Supports screen size editing workflows so editor view matches live layout constraints.
Notes
- This update focuses on admin customization speed, cleaner UI presentation, and better compatibility with modded item ecosystems.
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:eNk0ACQx:WOgwUTfI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eNk0ACQx:WOgwUTfI"
}

