Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
All versions
mc1.19.2-v1.41.0
Release
Carpet TIS Addition v1.41.0 for mc1.19.24 years ago 74
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Changes
News
- Added rule
creativeNetherWaterPlacement, why not - Added rule
undeadDontBurnInSunlight, why not not - Added rule
instantBlockUpdaterReintroduced, bring back old behavior and have much logical logging messages for microtiming logger - Added TISCM network protocol, switch-able by rule
tiscmNetworkProtocol - Added rule
syncServerMsptMetricsDatausing tiscm protocol to sync server mspt metrics data to the client, which can be seen in the right bottom corner of the F3 debug screen - Added rule
flattenTriangularDistribution, make edge cases more likely to happen
Changes - Lifetime Tracker
- (1.19+) Lifetime tracker: Make item entity removal due to
InventoryOwner(villager, alley, piglin) picking up item work again
Changes - MicroTiming Logger
- Improved microtiming state change info and general block state displaying
- Updated setBlockState flag bit value descriptions. The full block state and related changes will be shown in the hover text for block state change events
- Put merged message indicator to the same line as the prev message
- (1.19+) Show advertise for rule
instantBlockUpdaterReintroducedif it's disable when enabling rulemicroTiming
Deprecate - Microtiming Logger
Since Microtiming dye marker provides good enough user experience, it's time for us to deprecate those legacy wool stuffs
- Deprecate non-
marker_onlyvalue of rulemicroTimingTarget - Make
marker_onlythe default value ofmicroTimingTarget
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:jE0SjGuf:lB3Us1r6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jE0SjGuf:lB3Us1r6"
}

