Tags
Creators
Details
0.2.1-1
Compatibility
Changes
WorldFinder 0.2.1-1 - Fabric 26.2 End structure hotfix
WorldFinder 0.2.1-1 is a dedicated hotfix for Minecraft 26.2 on Fabric. It fixes incomplete End structure searches that could affect End Cities, their ship variants, and End Gateways. The equivalent NeoForge builds were not affected.
What happened
On Fabric 26.2, WorldFinder's offline vanilla reference engine could retain an intermediate biome registry while preparing the End generator. When the structure scanner later validated an End City or checked the biome of an End Gateway candidate, some End biome references could not be resolved.
WorldFinder correctly kept every marker it had already proved, but the affected scan cell ended as a partial result. Users could therefore see valid End City markers while other expected cities or gateways were missing from the map.
This was a loader-specific initialization issue in WorldFinder. It did not change the seed, the world, or Minecraft's actual structure generation.
What changed
WorldFinder now rebuilds its End biome source from the finalized vanilla biome registry before starting structure searches. End City validation and End Gateway placement checks both use that finalized generator, preventing unresolved End biome references from interrupting the scan.
The partial result warning remains available for genuine failures and for intentional safety
limits on exceptionally large searches. This hotfix removes the incorrect Fabric 1.21.11 and 26.2
partial results caused by the End biome registry issue.
Updating
This update is recommended for every WorldFinder user on Minecraft 26.2 with Fabric. Replace the previous WorldFinder JAR with the matching corrected file:
worldfinder-fabric-26.2-0.2.1-1.jarfor Minecraft 26.2.
No configuration change, cache cleanup, world recreation, seed change, compatibility addon, or server-side installation is required. NeoForge users and users on other Minecraft versions do not need this loader-specific hotfix.
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:vY3ysdL3:n4R6nTEd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vY3ysdL3:n4R6nTEd"
}

