Tags
Creators
Details
Licensed ARR
Published 3 weeks ago
Updated 3 days ago
All versions
26.2-0.85.0
Beta
exfilcraft 0.85.0 (26.2)last week 11
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
ExfilCraft v0.85.0
πΉ Bunkers and pillagers
- A bunker's boss now waits until you unlock your way in, instead of appearing as soon as anyone walks near. A bunker can no longer count as cleared without anyone having gone inside.
- Clear a bunker's garrison and it stays clear for the rest of the raid, and a restart can no longer stack a second one on top of it.
- Raid pillagers move 20% slower, so they are easier to shake off. Their pace is a server setting if you want it back. The mod's own illagers are unchanged.
- One pillager tower per raid now holds a caged Enraged Golem that bursts out when you get close, and more of them roam the Overworld.
πΊοΈ Raid map
- It shows everywhere you have ever explored now, so imprinting at the cartographer no longer turns your own map grey again.
π Contracts and villagers
- A contract taken from a villager in a raid lasts as long as the raid does. Extract or die, restock, and go back in with your progress intact.
- Plot residents greet you when you right-click them.
πΎ Minis
- Your mini can no longer swallow a mining swing, a block placement or an attack, and arrows pass through it. Crouch and right-click with an empty hand to put one away.
- The Mini Guardian is the Mini Elder Guardian now. Anyone who owns one keeps it.
π§ Fixes
- Buried treasure pays out at rusty chest grade instead of tier 2 bunker grade.
- Explosions can no longer destroy the block a flag stand's banner sits on.
- Squad mates can no longer hurt each other's pets or enlisted plot residents.
- Raid nights are short again, and the flag-stand garrison settings work.
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:969qON2e:31T48JIn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:969qON2e:31T48JIn"
}

