All versions
1.20.1-0.11.4
Release
Mine Mine no Mi - 1.20.1 - 0.11.4last month 13.1K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
0.11.4
Bug Fixes
Abilities
- Fixed punch ability damage not being applied
- Fixed the fishman bonuses for damage and toughness not existing
- Fixed the following punch abilities with no cooldowns:
- Eleclaw
- Magma Coating
- Spar Claw
- Netsu Enhancement
- Vulcanization
- Fixed the following abilities not properly generating their blocks:
- Great Cage
- Awase Baori
- Torikago
- Fixed Oil Covered entities not exploding when set on fire
- Fixed breakable effects (such as frozen) instantly breaking themselves
- Fixed Kami-E's cooldown sometimes reaching years
- Fixed El Thor's destruction not being destructive enough
- Fixed Black Hole locking up after first usage
- Fixed Liberation not absorbing blocks generated by other abilities other than black hole
- Fixed Overheat not destroying any blocks
- Fixed the lightning effect caused by Haoshoku Haki: Infusion not being visible while holding a weapon
- Fixed the disabled overlay on the ability bar not being visible if the ability was in any other state prior
Others
- Fixed a server crash when burning a flag
- Fixed a server crash when trainers would attempt spawning next to a player with no selected fighting style
- Fixed the missing bullet icon in tooltips
- Fixed the structure spawn chance configs not working at all
- As a small note, due to the logic change and the overall improvements of 1.20.1 these configs were defaulted and should now be 75% by default
- Fixed the
/ability awakensubcommand not being available after enabling the config - Fixed NPCs still being able to attack while affected by swing blockers (most stuns / handcuffs etc)
Optional dependencies
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:AWGqBEjs:FBQOkYT6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AWGqBEjs:FBQOkYT6"
}


