Check the game version first
Identify the exact Minecraft version attached to your Forge profile. Choose a FallingTree release that lists that game version and Forge as the loader.
Verify the Forge profile
Launch Forge once before adding a new mod so the loader can create the expected folders and you know the base profile works. This separates loader problems from mod problems.
Install the Forge build only
Place the downloaded FallingTree Forge JAR in that instance’s mods folder. Keep only one FallingTree build unless the project documentation specifically instructs otherwise. Fabric and NeoForge variants should not be mixed into the Forge folder.
Start with a clean test
When troubleshooting, temporarily test with FallingTree and only its necessary environment rather than a large collection of unrelated mods. If that works, reintroduce other mods gradually to identify a compatibility conflict.
Keep worlds backed up
Configuration changes are usually safer than game-version migrations, but backups are still good practice. Copy important worlds before major loader, Minecraft, or modpack updates.
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.