Back up worlds and configuration
Before replacing files, copy important saves and any FallingTree configuration you want to preserve. This matters most when the update is part of a broader Minecraft or loader migration.
Check your current environment
Write down the Minecraft version and whether the instance uses Fabric, Forge, or NeoForge. Select an update that explicitly supports that same combination unless you are intentionally upgrading the entire instance.
Replace instead of stacking JARs
Stop the game or server, remove the previous FallingTree JAR, then add the new matching file. Keeping multiple versions in the same mods folder can cause duplicate-mod or resolution errors.
Review dependency changes
A new release can change compatibility or dependency expectations. Read the official version notes and loader metadata, especially when moving across major Minecraft or loader versions.
Verify configuration after launch
Start the updated instance and inspect the log for warnings. Test tree behavior in a safe area and confirm important settings still match your preferred balance.
Keep the rollback copy briefly
Do not delete the backup immediately after the first successful launch. Keep it until you have played long enough to confirm the update behaves correctly with the rest of your mod set.
Use a FallingTree file that matches both your Minecraft version and loader. Our download picker resolves files from the official Modrinth project instead of repackaging the mod.