All versions
1.1.10
Release
More Vanilla 1.1.1023 hours ago 8
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
More Vanilla 1.1.10
- Hammers and excavators: the block outline now shows the whole 3x3 area that will be broken; sneak to break a single block
- Lucky block opening: the block shakes, glows green (good surprise), red (trap) or purple (neutral), then bursts before the event happens
- Advancements rebuilt: one readable tree with real milestones (gems, area tools, upgraded netherite, the Enderite Dimension, the dungeon, the four Void guardians, the Seal, the boss, the story, lucky blocks, exploration, horse training) instead of one advancement per tool tier
- Tooltips: every item has a short description; hold Shift for details (how to get it, how to use it, how to repair it)
- Removed "hold W" on items: Orwen's Guide opens from the guide book
- Excavators now dig 3x3 in every shovel block (gravel, clay, snow, soul sand...), not only dirt and sand
- Adapaxel: it now takes the shape of the right tool for the block you look at (pickaxe, axe, shovel or hoe), with a small click
- Enderite Boss telegraphs its attacks: new Ground Slam in both phases (three red zones fill up on the ground, then explode); the Shockwave shows its 7-block red ring filling up and a green safe gap; the Void Beam draws a purple strip on the ground while aiming. In phase 2 the slam warning is shorter and a second slam follows
- Enderite Dimension ambiance: each biome has its own fog, sky, particles and sounds (turquoise motes and distant chimes in the Enderite Lands, thick violet fog and swirling spores in the Enderzone, dark sky and falling ash in the Far End)
Optional dependencies
Any compatible version
Any compatible version
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:d2kWhzyy:fySMxAFl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:d2kWhzyy:fySMxAFl"
}

