
MobPVP // CANCELLED
MobPVP transforms your Minecraft survival experience by assigning levels to every living creature in the game. Based on these levels, mobs gain different abilities, attributes, and loot chances, creating a more challenging and rewarding combat system.
Links
Tags
Creators
Details
3.1.7
Compatibility
Changes
MobPvP 3.1.7 Released!
Discover the new features of Reinforced Copper! Isn’t it wonderful to earn new advancements while playing? In this version, we’re adding new features to Reinforced Copper with Iron. With a few new weapons and bug fixes, the gameplay experience has been improved. Don’t forget to collect the new advancements!
New Features:
- Reinforced Copper Cannonball with Iron added
- "Güçlü Gibi Görünüyor..." and "Bu Neden Bu Kadar Ağır?" advancements added
Reinforced Copper Cannonball with Iron:
- Has about 10 hearts of impact damage
- Crafted with 1 Reinforced Copper Ingot with Iron
- Do not try to hit the Ender Dragon or End Crystals with this cannonball!
"Güçlü Gibi Görünüyor..." advancement:
- Granted when you obtain the Reinforced Dagger
"Bu Neden Bu Kadar Ağır?" advancement:
- Granted when you obtain the Reinforced Copper Ball
Fixes:
- Fixed Tiny Iron Golems having 300 health and being too slow
- Fixed #3: Bulwark boss drowning in water
- Updated the dungeon triggered when clicking on the Super Heart — it no longer traps you (also visible in the in-game panorama view)
Removed:
- The startup animation was removed since it didn’t fit the mod’s concept
- The fixed background image was replaced with a panorama that will update with each new MobPvP release
Please note that the newly added item currently only has English and Turkish language support. Similarly, all advancements are currently written only in Turkish. This will be fixed in future versions.
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:Ay6wGd6r:7fd5SJMy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ay6wGd6r:7fd5SJMy"
}
