1.12.27
Compatibility
Required content
Changes
-
Removed the Battle Clone skin URL download controls and client-side external skin download path, so custom clone skins now only come from local skin files and normal in-game skin syncing, due to a curseforge upload rejection issue.
-
Reworked the Battle Clone config screen into a cleaner tabbed layout with improved spacing, grouping, rule toggles, and battle-format selection styling.
-
Added
Random Walkingwith a configurable radius, letting Battle Clones roam around their placed anchor point and return properly when turned off. -
Added clearer rule tooltips, improved AI difficulty coloring, and expanded config-screen localization across the Battle Clone UI.
-
Added a global server config toggle for whether admins can edit other players’ Battle Clones, with server-side enforcement.
-
Restyled the server config screen to match the newer config-screen look while keeping the mod’s brown theme.
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:medEuFrY:gIkWgNOo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:medEuFrY:gIkWgNOo"
}


