Tags
Creators
Details
1.1.1
Compatibility
Changes
This bugfix release resolves a server-side compatibility issue that could prevent unmodded clients from joining servers running Spawner Fix.
Previous versions registered a custom command argument type for the spawner gamerules. On dedicated servers, Minecraft sends command registry data to connecting clients. Clients without the mod did not know this custom registry entry, which could cause a disconnect with a registry mismatch error.
-
Server-Side Join Fix: Unmodded clients can now join servers running Spawner Fix without registry mismatch disconnects.
-
Vanilla Command Arguments: Replaced the custom gamerule argument type with Minecraft's standard integer argument handling.
-
Safe Client Sync: Optional clientbound sync packets are now only sent to clients that support the Spawner Fix channels.
-
Spawner Range Behavior: Spawner activation range remains configurable and defaults to 128 blocks, matching normal mob spawning distance.
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:HdaDf8sL:SmFsCJot"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HdaDf8sL:SmFsCJot"
}

