All versions
1.0.12
Release
StepCraft 1.0.127 months ago 27
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Dedicated servers only
Changes
StepCraft Mod - Update Changelog
Release: Incremental update (Minecraft mod only)
Key Highlights
- Extended the custom slot-placement fix from Claim Rewards to Day Steps.
- Added configurable status behavior for runtime status icons so they can be edited in layout config/editor.
- Added overlap support and editor targeting improvements for overlapped status keys.
- Added a configurable Day Steps entry icon template (
step_icon) for the repeated step-history items. - Improved editor help text for overlap controls and template-icon behavior.
Day Steps Updates
- Added configurable runtime status key:
day_steps_menu.status
- Day Steps now uses the same placement model as Claim Rewards:
- blocked-slot-aware placement
- state-aware status reservation
- status slot released when real day-step entries are shown
- Added configurable day-step entry icon template:
day_steps_menu.step_icon
- Day-step list entries now render using
step_icon(instead of hardcoded feather), including display components.
UI Editor Improvements
- Overlap handling improvements:
- Can cycle active target/top element for overlapped keys.
- Added explicit overlap helper text in tooltip instructions.
- Added special high-visibility editor notice for
day_steps_menu.step_icon:- clearly states slot position is template-only
- clarifies entries always start at first available slot
New/Updated Layout Keys
- Added:
claim_rewards_menu.status_empty - Added:
day_steps_menu.status - Added:
day_steps_menu.step_icon
Compatibility Notes
- Existing configs remain compatible.
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:gg5uSseU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eNk0ACQx:gg5uSseU"
}

