0.0.3
Compatibility
Changes
-
PRIDEIUM GEAR TWEAKS:
Increased durability from ~650 uses to 2500 uses on all prideium gear.
Can now cancel the bounce and aoe attack from the full prideium armor set bonus by crouching while mid-air
Prideium pickaxe now has a tunnel digging feature where right clicking a natural stone block or crouch-right clicking any mineable block digs out a 10 block long, 5x5 tunnel.
Prideium sword has a projectile which shoots out when right-clicking. When projectile hits entity, it does AOE damage in a 10 x 10 area which scales with amount of enemies hit and also heals, gives food and saturation with same scaling.
Prideium shovel digs everything a shovel can dig in a 3 x 3 square. Crouching while digging will make the shovel behave normally, albeit super fast since all the prideium tools are ridiculously fast by default. I know this is just the excavator from Tinker's Construct but name me a better feature to add to a shovel. I would've given it the Market Gardener effect from Team Fortress 2 but Minecraft already beat me to that with the Mace.
-
PRIDEIUM CRYSTAL MAJOR IMPROVEMENTS:
Now the prideium crystals will spawn on top, on the side of or under blocks instead of always spawning on the ground.
Added prideium crystals to the end.
Adjusted spawn rates of prideium crystals in all dimensions to, hopefully, make them more common while getting more common in later dimensions.
-
GOODBYE PAGE CAMEO:
Added new music disc and painting referencing the game Goodbye Page made by my good friends Thebluedash and coffeecode3d.
-
SMALLER FIXES:
Adjusted some spawnrates for my custom loot pools.
Added back the vanilla splash texts. Copy-and-pasted the splash texts a bunch to get a roughly 50-50 chance of a mod splash text or vanilla splash text showing. Added a couple of new splash texts too!
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:oimhit37:VZIbtudq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oimhit37:VZIbtudq"
}

