Tags
Creators
Details
mc1.17.1-0.7.5
Compatibility
Changes
This release adds fixes for several issues introduced in previous Lithium versions. Besides a serious chunk save format incompatibility with 1.18 snapshots, a memory leak and a mistake in the hopper logic are fixed. It is recommended that all users upgrade to this release.
Worlds that were used with Lithium will have chunk corruption when upgrading due to the breaking save format changes in the 1.18 snapshots. The datafixer responsible for upgrading to the new format is missing (MC-239610), which leads to chunk corruption and regeneration.
If you have used Lithium in the past and you want upgrade your world to Minecraft 1.18 snapshots, you need to follow these instructions for each world to avoid severe chunk corruption:
Instructions to avoid chunk corruption when updating to 1.18 snapshots:
If you are upgrading a world that has never been used with Lithium, or you are upgrading to a version that includes a fix for MC-239610, you are likely to be unaffected by this issue. If you are unsure, follow the instructions anyway.
- Singleplayer instructions: Start the game with Lithium 0.7.5 installed. Instead of opening your world, select it in the list of worlds, press "Edit", press "Optimize World", then "Create Backup and Load". Wait for the world to load, this will take a long time depending on the world size. After closing the world you can upgrade it to a newer Minecraft version.
- Server Instructions: Make a backup of the world. Start the game with the launch parameter
--forceUpgrade=true, e.g. by launching the server.jar withjava -jar server.jar --forceUpgrade=true. Wait for the world to load, this will take a long time depending on the world size. After closing the server you can upgrade it to a newer Minecraft version.
The changelog is available on GitHub right here.
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:FHFKMKeu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gvQqBUqZ:FHFKMKeu"
}

