Tags
Creators
Details
2.0.0
Compatibility
Changes
Updated to NeoForge 1.21.1, Reworked/re-coded the mod entirely. Contains less content than previously, but is of higher quality. No longer relies on any dependencies.
Currently Has:
Petrification and De-petrification
- Supports petrification for ALL entities (including modded)
- Stops all inputs and item pickups. You cannot move or open your inventory
- Freezes animations in their last frames, and persists between rejoins
- Adds a stone texture over ALL entities
- Can be de-petrified by standing underneath "Dripping Guanostone" for a random amount of time
Functioning Medusa
- Requires a Hexagonal-Cut Diamond to power it
- Can be placed on the ground as a block
- Can be activated through a GUI or through chat
- Can activate even when it is an item on the ground, or inside inventories/chests
- Can choose the target entity to petrify
- Has a new, nice petrification visual
Mass Petrification Event
- Starts randomly, between 6000 to 24000 ticks from world creation
- Has a physical petrification wave travel across the world over the span of 1200 ticks
- Spawns a Medusa device within a 500x500 block radius of spawn
- Petrifies all players and villagers, even if players join later
Miracle Cave Generation
- Randomly generates a cave around the player after the Mass Petrification event
- The cave natively matches your surroundings
- Generates a "Dripping Guanostone" which will eventually set you free
Extensive Config File
- Can adjust the values of almost everything through configs
Commands
- Can run /gamerule doMassPetrification (true/false) to toggle the event
- Can run /gamerule spawnPetrified (true/false) to toggle if players spawn in petrified after the event
- Can run /drstonekos massevent start/stop to begin or end the Mass Petrification Event
- Can run /drstone depetrify to un-petrify yourself
MISSING (Things will be re-added in the future)
- No longer contains a way to make "Miracle Fluid", can only un-petrify through commands or the Miracle Caves
- Is missing all the other blocks and items that were added previously
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:neby8dsf:KVL3o6nu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:neby8dsf:KVL3o6nu"
}

