All versions
1.1
Release
Grand-Builder 1.1last month 27
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Changes
- 3D Effects
- Reworked UFO Invasion, Rift Bloom, Meteor Forge, Clockwork Drive, and Aurora Weave with animated 3D geometry instead of particle-based silhouettes.
- Added beams, orbiting shards, meteor trails, a moving clock mechanism, and glowing aurora curtains.
- Added brief camera shake, camera roll, and reveal flashes. Animations freeze when construction is paused.
- Herobrine and Charges
- Herobrine: appears beside the placement target, holds a block, places it with an animated arm swing, and teleports to the next location. Glowing white eyes and short-lived afterimages complete the effect.
- Builder Charge: flies along an arcing path and detonates, revealing the entire structure at once. The explosion features flying casing pieces, a 3D pressure shell, an expanding shockwave, and an animated structure reveal.
- New Build Modes
- Time estimates: the menu shows an approximate duration before construction starts and the remaining time during construction or dismantling.
- Lightning Strike: custom branching 3D lightning hits the placement target, causing a block to appear.
- Reverse Build: choose whether construction starts from the top, front, right, left, or back, relative to the structure’s orientation.
- Dismantle: the structure appears first, then gradually comes apart. Choose standard removal, Herobrine, lightning, or Builder Charge effects.
- Explosion options: Builder Charge can use a visual-only explosion or a destructive blast that damages the surrounding area. Destructive explosions require a separate warning confirmation.
- Mode-specific settings appear only when relevant, keeping the menu uncluttered.
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:vCeo0YXL:1wr7AyhO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vCeo0YXL:1wr7AyhO"
}

