WorldFinder 0.2.1 - Vanilla fallback restoration

WorldFinder 0.2.1 restores the vanilla reference behavior that should remain available regardless of which other mods are installed. When no compatibility addon handles custom world generation, WorldFinder must continue to display what the corresponding vanilla Minecraft version would generate for the entered seed.

What happened

WorldFinder tied parts of its vanilla structure catalog too closely to its ability to inspect the active world-generation environment. Mod-owned generation resources could be mistaken for changes to Minecraft's vanilla data, while remote servers had no integrated-server resource manager to inspect.

In both cases, WorldFinder incorrectly discarded part of its own vanilla fallback. This was a general compatibility defect in WorldFinder, not a problem caused by any particular content mod.

This caused three visible regressions:

• the singleplayer seed was no longer detected automatically in an otherwise supported vanilla Normal world;
• Village, Ancient City, Trial Chambers, Pillager Outpost, and Trail Ruins disappeared from the structure filter list;
• the same five filters remained unavailable on remote servers even when the correct seed was entered manually.

What changed

WorldFinder now keeps its version-specific vanilla reference engine available independently from the installed content mods. It also distinguishes between:

• definitions owned by another mod;
• resources that actually replace vanilla entries in the minecraft namespace;
• live generators and biome sources that differ from the supported vanilla Normal profile.

Mod-owned definitions no longer invalidate a vanilla world merely by existing. Real vanilla world-generation replacements and unrecognized active generators still prevent unsafe automatic seed reuse. With a manually entered seed, WorldFinder keeps displaying its clearly defined vanilla reference instead of claiming that it reproduces unsupported custom generation.

On multiplayer and in unsupported world-generation environments, WorldFinder now keeps its complete vanilla structure catalog and loads the exact templates bundled with the running Minecraft version. A manually entered seed therefore produces the normal vanilla reference map without requiring WorldFinder on the server.

If a mod or server changes world generation, a compatibility addon can replace or extend that baseline. Without such an addon, WorldFinder deliberately continues to show the vanilla behavior for the selected Minecraft version rather than hiding filters or pretending to reproduce the custom generation.

Updating

Replace WorldFinder 0.2.0 with the matching 0.2.1 JAR for your Minecraft version and loader. No compatibility addon, configuration change, server-side installation, or manual cache cleanup is required to restore the vanilla reference behavior.