Tags
Creators
Details
1.2.0
Compatibility
Required content
Changes
1.2.0 — 2026-04-20
Added
- Voxy support — the mod now detects whether you have Distant Horizons or Voxy installed and offers to download the correct LOD package for your setup
- Creator & regional IP support — any
*.wynncraft.comaddress (e.g.igbarvonsquid.wynncraft.com) is now recognized and LODs are installed into the correct server folder automatically - Conflict detection — if both Distant Horizons and Voxy are installed simultaneously, a warning screen appears on launch explaining that only one LOD mod can be active at a time
- 5-second disconnect countdown — chat messages count down before the game disconnects to install LODs, so you know what is happening
- Updated LODs for Voxy — includes Fruma
⚠️ Distant Horizons LODs are not yet updated for Fruma. If you have explored Fruma on Wynncraft with Distant Horizons and would like to contribute your LOD files to the project, please reach out! You can open an issue on GitHub or contact me directly.
Changed
- LODs are now extracted directly into the existing IP-specific server folder instead of replacing the entire LOD data directory, so other servers' LOD data is never affected
- Installation and extraction now run on a background thread — the game no longer freezes or hangs during install
- Wynntils is now declared as a required dependency in the mod manifest
- Minimum one LOD mod (Distant Horizons or Voxy) is required to launch
Fixed
- Screen text (title and description) now renders correctly on all prompt screens
- Mod no longer crashes on launch when Distant Horizons is not installed
Compatibility
- Minecraft 1.21.11
- Fabric Loader 0.18.4+
- Wynntils 4.1.5+
- Distant Horizons 2.4.5-b-1.21.11 (optional)
- Voxy 0.2.13-alpha (optional)
Optional dependencies
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:Rau5VAYE:zyDU46j3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Rau5VAYE:zyDU46j3"
}

