Links
Tags
Creators
Details
1.1.0
Compatibility
Changes
New
/sa unstacksplits the stacks of mobs WildStacker no longer stacks. Changing the WildStacker whitelist only affects new merges, so mobs stacked before stay stacked. This command splits them back:- each copy keeps the mob data, like color, variant and age
- copies are spread over the free blocks around the stack, at most 8 per block, so vanilla cramming doesn't kill them
- the stack name (like
x30 Cow) is removed, names from name tags are kept - stacks in chunks loaded later are split too, until the next restart, and logged
- Entities WildStacker can't stack, like armor stands, mannequins, players and NPCs, are skipped.
A stack only keeps one real mob, so mobs that were different before being stacked come back as copies of the first one.
Replace the old jar with this one. No config changes needed.
SHA-256: c3b64e9a16432bd33734c8079634a47b6ffad0ea574c848fbaff6199deb498d8
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:iNJpn9V2:Gtj47C5j"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iNJpn9V2:Gtj47C5j"
}

