Tags
Creators
Details
Licensed Apache-2.0
Published 3 years ago
Updated 3 years ago
All versions
1.16.4v1.7.0
Release
IllagersPlus-1.16.4v1.7.03 years ago 70
Uploaded by
Compatibility
Minecraft: Java Edition
1.16.4–1.16.5
Platform
Forge
Supported environments
Client and server
Changes
Note: With the change to the config file, the old config wont work anymore. Remember to transfer your settings over to the new config and delete the old one!
- *Tweaked movement speed of all illagers to match that of vanilla illagers
- *Fixed the game crashing when removing this mod. Apparently its trying to look for enum values that dont exist when the mod is removed, so now raid wave members are added during world loading and removed during world unloading
- +Added the Ice Castle to the structure info class
- *Redid Structure Registration and mod config
- +Added an attack to the general that makes it so he spawns some reinforcements during raids or in the world when provoked
- *Fixed the Falling Ice Spike stuttering when, well, falling
- *New config now has a biome whitelist, blacklist and a biome category list for structures
- *Structure spawn dimension was changed from a blacklist to a whitelist
- +Added sounds to the falling ice and ice spike
- *Tweaked AI during reinforcements, and fixed the bossbar that appears, displaying the wrong max wave count
- +Added mixin to help with the fort crashing optimized spawning of entities to make up less lines of code
- *Made the necromancer's health stealing attack more deadly
- *The Frostmancer's attack was killing item entities. fixed that now
- *Structures will try not to spawn on top of each other or at spawn I think i fixed the fort crashing while generating
- +Added some cool effects while the necromancer attacks
- *Cleaned up some code
- +Added loot pools for the illager fort
- *Nerfed all loot pools
- *Increased the frequency of features spawning in the illager fort, to fill in those poor empty spaces ;n; but due to lag, decreased the number of illagers spawning per piece
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:HjDyU6dR:kUNPY9jX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HjDyU6dR:kUNPY9jX"
}

