Links
Tags
Creators
Details
1.6.0
Compatibility
Changes
ROF-Carpet-Addition v1.6.0
✨ New Features:
Rules:
mergeExplosion: Merges the multiple explosions produced by merged TNT into a single one; the effects on entities stack077db466737dcdspawnStatisticSimplifyWhitelist: Skips the chunk lookup and the biome query inside the spawn statistic for whitelisted dimensions; defaults to{}(no dimension simplified)9ef2dcc- Note: the result stays identical to vanilla only when no biome of the world defines spawn costs
betterEnderPearlTicket: Replaces the vanilla loading ticket with a special loading ticket in certain cases; when ECM is not enabled, it only applies to pearls outside world height949ab0ablockingEnderPearlLoading: Makes a pearl's chunk loading block the main thread, reducing desync between pearl ticks and world ticks; the value is the maximum blocking time in milliseconds,0disables it949ab0a
Optimizations:
- Explosion optimization refactor: added an entity exposure cache
52a2fd4 - Merge TNT Next optimization: added the SafePlus mode, a safer merge mode than Safe
6737dcd
🔧 Changes:
- Unified rule naming:
optimizeRaycast→optimizedRaycast,optimizeItemMerge→optimizedItemMerge6737dcd - Ender pearl rule changes:
optimizeForcedEnderPearlTick(String, with1_21_2-/1_21_2+options) →optimizedEnderPearlTick(boolean);enderPearlForcedSync(boolean) →blockingEnderPearlLoading(int, milliseconds,0disables it)949ab0a - Language file cleanup: removed redundant
carpet.rule.*.nameentries.
[!IMPORTANT] Multiple rules were renamed and their value formats unified in this release, so old config keys will stop working and must be updated manually:
optimizeRaycast→optimizedRaycast,optimizeItemMerge→optimizedItemMerge,optimizeForcedEnderPearlTick→optimizedEnderPearlTick,enderPearlForcedSync→blockingEnderPearlLoading; themergeTNTOnlyNetherrule has been removed; list-type rules now need brace-wrapped values (e.g.{!minecraft:drowned}).
See the English rule documentation for a detailed description of every rule.
Full changelog: 1.5.6...1.6.0
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:YP8psfXu:IcFowqoA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YP8psfXu:IcFowqoA"
}

