0.0.7
Compatibility
Required content
Changes
Mobs:
Added converted horse
Added conjured animosity (only spawns naturally if shadow invasion is enabled)
Retextured and completely reanimated the converted human (conv villager and husk are going to be retextured and reanimated next update, and they will actually look different than the conv human)
Converted humans now have differing attack animations, and a new melee attack. The main melee attack now does 4 dmg instead of 5.
Changed the conv sheep’s attack a bit. Conv cow’s normal death places conv blood in a smaller radius.
Blocks:
Added molten meteoric rock
Added enormous bony segments and cracked enormous bony segments (will be used in the future for infection structures)
Added rly cool overlay for stepping in infestation
Enormous tendril segments and tendril segments no longer slow mobs down when stepped on
Converted webs slow down entities less
Retextured the converted egg
Items:
You now have to hold left control in order to see the mob classification when hovering over the spawn eggs.
Added a new classification category for the spawn eggs: style
Other:
Added the overmind.
Doubled the amount of meteor structure variants (from 3 to 6)
Completely revamped the division announcements, they now have custom colors and 5 text variants each.
Added the shadow invasion, the event is still WIP and will only trigger upon a command activating it.
Added 2 more systems to the status GUI, and replaced 1. Only 1 system is usable right now
Added a new command: phayriosis2_systems. Currently only used to turn on the shadow invasion.
Retextured all effects
Bug fixes: Fixed the missing texture leeching tendrils
Fixed optic stalks being solid and having incorrect bounding box size.
Fixed abhorrences making server logs when they despawn
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:sGdVXhFA:5aRtqSMa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sGdVXhFA:5aRtqSMa"
}

