All versions
0.1.20
Release
[FORGE]PoisonousPotatoUpdate-1.20.4-0.1.202 years ago 210
Compatibility
Minecraft: Java Edition
1.20.4
Platform
Forge
Supported environments
Client and server
Changes
0.0.X -> 0.1.20-Forge(Current):
-
Now Poisonous Potato Plant will always be in the bonus chest. -
In the config file you can configure to force bonus chests to appear (always 'Yes' when creating a world). This option is disabled by default. -
Fixed loot-tables in potato villages. -
Fixed sleep mechanics in the potato dimension. -
Fixed a bug where if you teleported from a potato dimension to an owerworld dimension while near a coliseum or potato village, a reverse portal would not be created. -
Now if you put a block on the poison path, it turns into terre de pomme instead of dirt. -
Fixed moon texture in potato dimension. -
Fixed giant texture. -
Fixed bugs related to toxifin (attack sounds and game crash when toxifin starts attacking someone). -
Now the textures of vanilla mobs will always work correctly in the potato dimension (Previously, the textures of mobs were broken if they were modified by other mods). -
Added missing tags for mobs. -
Fixed genearation in corruption biome (1.20.4). -
Data saving fixes -
Mega Spud name fixed -
Fixed crash on launch (1.20.4) -
Config fix -
Now Mega Spud summons minions correctly (In the center of the coleseum) -
Now you can adjust the volume of sounds adjust the volume of sounds made by mobs from this mod. -
Now Toxifins will not receive the poison effect when in poisoned water in the config file. -
Posion Farmland now properly turns to terred-de-pome whenever entities fall on it. -
Bug fixes -
Added missing advancement -
Fixed some advancements -
Potato blocks and items work properly with composter
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:27Y5MTTs:OV4kIzK7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:27Y5MTTs:OV4kIzK7"
}

