All versions
0.3.0
Alpha
Omni-Mobs 0.3.0last year 197
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Changes
- Reworked Metapotent Flashfur.
- Substantially increased Metapotent Flashfur’s defence, as he doesn’t rely on the event bus anymore.
- Quadrupled Metapotent Flashfur’s size.
- Changed Metapotent Flashfur’s colours (light rays, lines, beam, etc) from pink and blue to purple and ice-blue.
- Added secondary moving ice-blue lines on Metapotent Flashfur, that move in the opposite direction to the purple ones.
- Reduced the intensity of the lines.
- Added a star visual effect around Metapotent Flashfur, in his light rays.
- Updated flash of white for Meta-Erasure. (It is smoother.)
- Renamed Meta-Erasure to Omni-Erasure.
- Updated the positioning of the bossbar.
- Updated the colour of the “Flashfur” text on the bossbar.
- Added “Metapotent” on the bossbar.
- Added Totality Boom move.
- Quadrupled the reach of Meta-Swipe (as he is quadruple size).
- Changed the minimum teleport range from 15 blocks to 60 blocks.
- Renamed Teleport to Meta-Teleportation.
- Made Metapotent Flashfur attack all living entities, instead of just monster entities.
- Added flash of white when you spawn Metapotent Flashfur in.
- Added camera shake when you spawn Metapotent Flashfur in.
- Added a sound when you spawn Metapotent Flashfur in.
- Added Event Bus Override.
- Replaced Metapotent Flashfur’s music.
- Old Song: Frantic Fast Forward by Nicholas Panek from Pixabay.
- Added Meta-Explode move.
- Made Metapotent Flashfur teleport 2.5x more often.
- Upgraded Boss entity defence.
- Made it harder to target Omni-Mobs entities by getting the registry name. It was done to prevent Mindustry Units from kicking players with Metapotent Flashfur in the world. I could have also banned /kick while Metapotent Flashfur was in the world, but it didn’t work as well.
- Made Flashfur’s anti-invulnerability stronger.
- Made it so the Entity Remover toggles the
die()method on shift right click. - Updated Entity Remover text.
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:6hI5AK5F:ZgMYlcqW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6hI5AK5F:ZgMYlcqW"
}

