3.0.0
Compatibility
Changes
Him - Herobrine v3 is a complete remake of the original mod from scratch. All systems have been rebuilt, optimized and improved, and new features have been added and changes have been made. Herobrine spawning is now on by default. Your challenge will be to obtain certain materials to perform a ritual to banish him from your world.
- The Caller block has been removed.
- Added the Notch Apple to replace The Caller. The Notch Apple is a mythic object from old Minecraft, removed from the game at one point and now brought back as the only element strong enough to combat Herobrine. To banish Herobrine back to the void (or bring him back once banished, if you dare), you must burn a Notch Apple by throwing it into a netherrack fire. The apple will bring him forth and destroy his physical presence in your world, freeing you.
- The Notch Apple is crafted as follows: an apple in the center, a nether star in the center of the upper row, a dragon head at the center of the bottom row, diamond blocks at the sides of the apple, and gold nuggets at the corners.
- Consuming a Notch Apple grants one hour of Strength II, Regeneration II, Fire Resistance and Absorption
- Rebalanced probability of each spawn type
- New spawn types added, and previous ones include new variance of effects and sounds
- More frequent spawns (every ~3 minutes by default)
- Added chance that Herobrine will watch you sleep
- Added /watch [player], where Herobrine watches from afar
- Added /spike [player] (as in spike your cortisol levels), where herobrine watches from afar and then lunges at you
- Added /hauntstate to check current spawn rate, time to next spawn and whether chase mode is active
- Added Chase mode, an event where spawns accelerate dramatically for a few minutes every so often
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:wClrSuYn:xWEuEJrd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wClrSuYn:xWEuEJrd"
}

