Tags
Creators
Details
mc1.19.2-0.9.0
Compatibility
Changes
Lithium 0.9.0 is a large update that includes new block entity optimizations and fixes several issues. The block entity optimizations improve the performance of hoppers, shulker boxes, campfires, furnaces and brewing stands by skipping their tick when they can't do anything. Futhermore several small behavior changes were fixed and mod compatibility was improved.
Additions
- new: hopper, shulker box, campfire, furnace and brewingstand sleeping
- new: aggressive hopper sleeping with comparator, entity movement and inventory change tracking
- new: avoid sending comparator updates when there is no comparator nearby
- new: optimized hopper minecart item entity search
- new: system for hopper sleeping
- new: block entity ticker caches whether it is inside the world border
- new: use fastutil hashmap as blockentity ticker collection
Changes
- change: avoid implementing LithiumInventory in LockableContainerBlockEntityMixin (mod compatibility)
- change: stationary storage minecarts on rails no longer notify hoppers in every tick
- change: chest boats inside stationary minecarts do not trigger the movement tracking system all the time
- change: replace suffocation overwrite with inject (mod compatibility)
Fixes
- fix: math.sine_lut: slightly off sin() and cos() results
- fix: unpushable_cramming: crash when entity ids are not unique (related to Hypixel/Wynncraft server)
- fix: entity.skip_equipment_change_check: mob crossbow changes not sent to clients
- fix: entity.fast_powder_snow_check: use landing instead of stepping block state
- fix: block.hopper: run loot generation on chest boats when converting to lithium stack list
You can support me on patreon: https://www.patreon.com/2No2Name
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:Nba2vozh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gvQqBUqZ:Nba2vozh"
}

