All versions
3.0
Beta
Porky's Legacy: Era of Corruption V3.0.3338 months ago 491
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
This version was going to be 2.1.333, but after all the content I've added I decided to change it to V3.
CHANGELOG
ADVANCEMENTS
- Don't breathe!
- Expanded fate
BIOMES
- Corrupted Spores
- Hazed Plains
BLOCKS
- Hazed Log
- Hazed Wood
- Stripped Hazed Log
- Stripped Hazed Wood
- Hazed Stairs
- Hazed Slab
- Hazed Fence
- Hazed Fence Gate
- Hazed Door
- Hazed Trapdoor
- Hazed Button
- Hazed Pressure Plate
VEGETATION
- Flaming Hope
STRUCTURES
- Rotten Altar
- Campsite
- Abandoned Merch
- Strange Pole
ENTITIES
- K (It really isn't an entity inside the mod, perhaps; it was there since the beginning… Even I will say… It doesn't belong here)
EFFECTS
- Anguish
GAMERULES
- SafeMode
IMPROVEMENTS
- There's a fade on the screen now… Wow.
- It will be more difficult to entities (specially the melee ones) to found you if you're fully covered with fog. But not impossible.
- Corrupted entities now have a new super rare event.
- Soulbound can survive inside the new Corrupted Spores.
- Rottenmorphen it's a bit rare due to its spawn in the new Hazed Plains.
- Improved Sinber RNG related things in some behaviors.
- Fear events cooldown has been improved.
- Paranoid effects Cooldown/RNG has been improved
- Added Anguish effect as a secondary paranoia Effect
- Added a new mechanic related to the ominous wood, necroveil in the new Hazed Plains biome
- Now Corruptinies have a chance to generate the new Corrupted Spores biome.
BUGFIX
- Improved some character dunking again (Still Broken (Also tired of fixing it))
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:5VhtPKd6:ujQZvKWh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5VhtPKd6:ujQZvKWh"
}


