All versions
1.0.9
Release
Hyper (Bosses & More) 1.0.93 years ago 58
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Forge
Supported environments
Client and server
Changes
Update Changelog:
-Made most Hyper Mobs fair to other mobs, dealing extra magic damage instead of void damage (aside from Hyper Warden)
-Improved Hyper Enderman's texture
-Improved Hyper Strider's texture
-Improved Hyper Blaze's model
-Slightly increased Hyper Blaze's speed
-Slightly increased the chance for Hyper Strider to summon their minions with an additional visual effect
-Slightly decreased Hyper Strider's firing speed and made it give off particles
-Netherbrick Golem now despawns naturally after a short while
-Updated Netherbrick Golem's immunities
-Updated Infernal Charge
-Renamed Flare to Blazing Scrap
-Updated Hyper Wither's and Super Zombie's increasing damage system
-Nerfed the amount Hyper Wither and Super Zombie can lifesteal
-Updated Hyper Wither's death explosion and made it not delete their drops on death
-Super Zombie is now slightly slower during the thunder wave attack to look more accurate
-Made Hyper Wither use the teleportation attack against other mobs less often
-Slightly reduced the chance for Hyper Creeper to use the explosion blast attacks
-Super Skeleton now can deal an additional amount of damage depending on chance
-Slightly nerfed Mad Snowman
-Slightly reduced the chance for Buffed Creeper to revive
-Buffed Hyper Creeper's damage
-Added a slight visual effect to Hyper Creeper landing/idling
-Increased the time Hyper Warden is slowed on spawn
-Slightly increased the chance for Hyper Witch to use the beams
-Slightly increased the chance for Super Skeleton to use the soul blast attack
-Slightly reduced the chance for Super Skeleton to use the explosion fall attack
Bug Fixes & Misc:
-Removed excess textures and procedures to reduce the mod size
-Fixed Invasion Flag mobs not taking knockback
-Fixed Hyper Creeper's Charged Variant having a spawn egg
-Fixed Hyper Wither occasionally launching themselves into the air
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:4x4b2R5n:TlExQ4sK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4x4b2R5n:TlExQ4sK"
}

