Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/qualk/take-care/llms.txt

Use this file to discover all available pages before exploring further.

When a new Minecraft snapshot or release is available you need to update version numbers in the versions catalog, upgrade Fabric Loom, regenerate the Gradle wrapper scripts, and adjust any source code that references renamed mappings or changed APIs. Because Take Care targets Meteor Client snapshots rather than stable releases, the Meteor dependency must also be updated in sync with the Minecraft version.
Always verify that a Meteor Client snapshot exists for the target Minecraft version before starting the update. If no matching snapshot has been published to https://maven.meteordev.org/snapshots, the Gradle dependency resolution step will fail and the project will not build.

​
Update process

1

Confirm a Meteor Client snapshot is available

Browse the MeteorDevelopment/meteor-client repository and check that a snapshot build targeting the new Minecraft version has been published. The snapshot version string follows the pattern <minecraft-version>-SNAPSHOT, e.g. 26.1.2-SNAPSHOT.You can also check the Maven repository directly at https://maven.meteordev.org/snapshots/meteordevelopment/meteor-client/ to see which versions are available.
2

Update gradle/libs.versions.toml

Open gradle/libs.versions.toml and update the relevant version entries. At minimum you will need to change minecraft, fabric-loader, and meteor. If the new Minecraft version uses different Yarn mappings, update yarn-mappings as well. If your addon depends on additional libraries listed under [libraries], update their versions there too.
gradle/libs.versions.toml
[versions]
mod-version = "0.1.0"

# Fabric (https://fabricmc.net/develop)
jdk = "25"
minecraft = "26.1.2"
fabric-loader = "0.19.3"

# Loom (https://github.com/FabricMC/fabric-loom)
loom = "1.16-SNAPSHOT"

# Meteor (https://github.com/MeteorDevelopment/meteor-client/)
meteor = "26.1.2-SNAPSHOT"
After saving, trigger a Gradle sync in your IDE (click the elephant icon in IntelliJ or run ./gradlew dependencies) to download the new dependency versions and detect any resolution errors early.
3

Update Loom to the latest compatible version

Fabric Loom must be compatible with the target Minecraft version. Update the loom entry in gradle/libs.versions.toml to the latest version listed on the Fabric Loom releases page. The loom version is referenced by the plugin alias in build.gradle.kts:
gradle/libs.versions.toml
# Loom (https://github.com/FabricMC/fabric-loom)
loom = "1.16-SNAPSHOT"
Change the value to the new Loom version and sync Gradle again.
4

Update the Gradle wrapper

The Gradle wrapper version should also be kept up to date. Run the wrapper update command for your platform, substituting <version> with the desired Gradle version:Unix / macOS / Windows (PowerShell):
Terminal
./gradlew wrapper --gradle-version <version> && ./gradlew wrapper
Windows (cmd.exe):
Terminal
gradlew.bat wrapper --gradle-version <version> && gradlew.bat wrapper
Running the command twice ensures both the wrapper properties file and the wrapper JAR are regenerated for the specified version. Commit the updated gradle/wrapper/gradle-wrapper.properties and gradle/wrapper/gradle-wrapper.jar files.
5

Adjust source code for Minecraft and mapping changes

Each Minecraft version may rename methods, fields, or classes in the Yarn mappings. Review your modules, commands, HUD elements, and mixins (takecare.mixins.json lists MixinESP, MixinTracers, and MixinParrot) for any references that no longer compile. Common areas to check:
  • Method names — Yarn mappings sometimes rename or move methods between versions.
  • Imports — package reorganisations can break existing import statements.
  • Mixin targets — class names and method descriptors in @Mixin, @Inject, and @Redirect annotations must match the new mappings exactly.
  • Event types — Meteor may rename or restructure its event classes between snapshots.
6

Check Meteor Client API changes

Review the master branch of MeteorDevelopment/meteor-client for breaking API changes that may affect your addon. Key areas to check:
  • meteordevelopment.meteorclient.systems.modules.Module — settings API, event subscription changes
  • meteordevelopment.meteorclient.commands.Command — Brigadier builder changes
  • meteordevelopment.meteorclient.systems.hud.HudElement — renderer API changes
  • meteordevelopment.meteorclient.addons.MeteorAddon — lifecycle method signatures
7

Build and test

Run the full Gradle build to confirm everything compiles and links correctly:
Terminal
./gradlew build
If the build succeeds, launch the Minecraft Client run configuration from your IDE to verify that the addon loads, modules appear in the module list, commands respond as expected, and HUD elements render correctly with the new Minecraft version.

Build docs developers (and LLMs) love

Get started for freeTalk to us