Tags
Creators
Details
Licensed MIT
Published 3 years ago
All versions
v8.0.7-1.20.1-Forge
Release
[FORGE] [1.20.1] IllagerInvasion-v8.0.7last year 1.8M
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
[8.0.7-1.20.1] - 2025-02-14
Changed
- Allow invokers to spawn in high tier raids (disabled by default)
[v8.0.6-1.20.1] - 2024-09-12
Fixed
- Fix
Illusioner::onSyncedDataUpdatednot calling super method
[v8.0.5-1.20.1] - 2024-04-24
Fixed
- Fix parts of the underground labyrinth structure sometimes being exposed on the surface
- Fix some labyrinth hallways rarely being flooded
[v8.0.4-1.20.1] - 2024-01-24
Changed
- Necromancer now drops zombie and skeletons heads as a rare drop
Fixed
- Fix crash on Skull Bolt impact
- Fix firecaller setting themselves on fire and not fleeing from iron golems
- Fix basher stun not updating
- Fix alchemists poising themselves
[v8.0.3-1.20.1] - 2023-11-05
Changed
- Protection enchantments can now be upgraded in the imbuing table
Fixed
- Fixed labyrinth hallways occasionally being flooded
[v8.0.2-1.20.1] - 2023-08-18
Added
- Added a config option for disabling the yellow invoker boss bar
Fixed
- Fixed occasional crash when alchemists are spawned in a structure during world generation
- Fixed villagers not fleeing from new illager enemies
- Fixed endurance trim doubling the rate at which food is drained instead of cutting it in half
[v8.0.1-1.20.1] - 2023-08-11
Changed
- Added illagers to the
numismatic-overhaul:the_bourgeoisieentity type tag
Fixed
- Fixed necromancer summoning particles not rendering
[v8.0.0-1.20.1] - 2023-07-20
- Initial release
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:jSV9w0J5:h3xEIiW8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jSV9w0J5:h3xEIiW8"
}

