1.7.2
Compatibility
Changes
MCWild v1.7.2
Supported Versions: Minecraft 1.21.x (including 1.21.11) System Requirement: Java 21
This update focuses on stability and compatibility, introducing a new adaptive loading system that ensures smooth performance across all server software types, including standard Spigot and high-performance forks like Paper.
Update Highlights
Universal Server Support I have implemented a new adaptive chunk loading system.
- Paper/Purpur Users: The plugin utilizes true asynchronous loading for zero-lag teleportation.
- Spigot Users: Addressed a critical issue where the plugin would crash due to missing API features. The plugin now automatically switches to a "Safe Mode" on Spigot servers to prevent crashes.
Performance Optimization: Smart Biome Filtering For servers running in "Safe Mode" (Standard Spigot), generating new chunks can be demanding. I have added a pre-check system:
- The plugin now checks the biome type before generating the terrain.
- If the random location is an Ocean or River, the plugin skips the generation process entirely and retries immediately.
- This significantly reduces the "Can't keep up" warnings and lag spikes associated with generating water worlds.
Server Health Protection
- Throttle System: If a safe location is not found immediately, the plugin now waits briefly before retrying. This allows the server to recover and process other events, preventing TPS drops during mass teleportation.
- Generated Chunk Priority: The system prioritizes locations where chunks already exist on the drive, making teleportation instant in explored areas.
Bug Fixes
- Fixed a critical error regarding cooldown management that occurred when reloading the plugin.
- Resolved compatibility issues with the latest Minecraft 1.21.11 server jars.
Note: No configuration changes are required for this update.
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:YLa9NkRH:AUKytoog"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YLa9NkRH:AUKytoog"
}

