Tags
Creators
Details
mc1.19.3-0.11.0
Compatibility
Changes
Lithium 0.11.0 fixes a tiny difference in the collision code that was noticeable in some tnt duper designs. Furthermore a few bug fixes and mod compatibility improvements are included. Besides all of that, Lithium now uses a new system internally for the available configuration options. Now you can check out a description of all optimizations here.
Additions
- new: remove vanilla temperature caching
- new: add automatically generated lithium-mixin-config.md
- new: testcase: closing fence gate updates llama pathfinding
- new: Lithium API for hopper-like item transfer cooldown
Fixes
- fix: remove incorrect chunk ticket creation (#449) by ishland*
- fix: block.hopper.worldedit_compat: update hopper caching when placing block entities when world edit is loaded
- fix: block.hopper: broken interaction with modded non-BlockEntity Inventory blocks
- fix: incorrect ordering of collisions causing non-vanilla entity movement behavior
- fix: alloc.blockstate: allow State withTables using non Block/Fluid types
- fix: world.block_entity_ticking.sleeping: crash when /perf command prints position of sleeping block entity
Changes
- change: remove redundant FluidState caching in BlockStates that was added to vanilla in 22w42a
- change: lithium config mod override parsing can be used with and without mixin. prefix
- change: use
@Intrinsicannotation to improve mod compatibility - change: rename chunk.block_counting to util.block_tracking
- change: entity.collisions.movement: check block below entity before other collisions
- change: rename ai.poi.poi.tasks to ai.poi.tasks
- change: move mixin.world.block_entity_retrieval to mixin.util.block_entity_retrieval
- change: switch from old LithiumConfig system to mixin-config annotation system
- change: add null check in ChunkAwareBlockCollisionSweeper
- change: implement unused onEntryRemoved method in BitSet optimization for POI Storage
- change: entity.collisions.movement: handle external changes to list of collision shapes correctly
- change: disable
ai.nearby_entity_trackingbecause it reduces performance in normal worlds - change: ItemEntity and Inventory entities only notify movement trackers when hopper optimizations are present
- change: split ai.nearby_entity_tracking into ai.nearby_entity_tracking.goals and util.entity_movement_tracking
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:gvQqBUqZ:sMWkk4VU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gvQqBUqZ:sMWkk4VU"
}

