Tags
Creators
Details
Licensed MIT
Published 10 months ago
Updated 1 hour ago
All versions
1.4.0+26.3-fabric
Release
Footsteps Trail 1.4.0 Fabric 26.31 hour ago 1
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
๐ฃ Footsteps Trail 1.4.0
โจ New
- Three footprint types: choose with
/footsteps type- Terrain (default): footprints are pressed into the ground.
- Surface: footprints are drawn on top of the block and take their look from what you walk on.
- Classic: flat markers in the shape and color you choose.
- Glow for Classic markers: a soft halo so your trail is easy to spot in the dark. Turn it on with
/footsteps appearance glow. - Settings screen: change every option in-game. Open it from Mod Menu on Fabric, or from the Mods list on Forge and NeoForge.
/footsteps help: lists every command with a short description.- Minecraft 1.21.1 support on Fabric.
๐ง Changes
- Toggle key is now
Zinstead ofB, to avoid clashing with backpack and minimap mods. You can still rebind it in Controls. - Simpler commands:
typeandsizeare now top-level (/footsteps type,/footsteps size). Shape, color and glow only apply to Classic footprints. - Placement modes removed: footprints are always placed on the ground now.
- Slime and honey: footprints on them now squish softly.
- Old settings carry over: if you had Realistic mode on, you get the Terrain type.
๐ Fixes
- NeoForge: fixed a crash when the mod was installed on a dedicated server.
- Broken config files: a broken or hand-edited config no longer crashes the game. The bad file is kept as
.brokenand defaults are used. Out-of-range values are corrected automatically. - Slime and honey: bouncing on them no longer uses up your footprint count.
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:gvzCipui:N4gDPtQ4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gvzCipui:N4gDPtQ4"
}

