NeoForge compatibility is version-specific. The safe rule is to follow the loader target written on the exact Botania release instead of assuming that a Forge build and a NeoForge build are interchangeable.
Start with the Minecraft version
Loader support is tied to Minecraft versions. A Botania build for one Minecraft version cannot be assumed to work on another, even when the version numbers look close.
Check the loader target carefully
Loader support changes across Minecraft versions. Treat Forge and NeoForge as separate targets unless the exact build you are using explicitly supports your chosen loader.
Do not rename or convert loader files
Changing a filename does not convert a Forge mod into a NeoForge mod. The code and dependency metadata must support the loader you are using.
Match every required dependency
Dependencies also have loader-specific builds. A correct Botania JAR paired with the wrong dependency variant can still fail during startup.
Use a separate test instance
Create a clean launcher instance for compatibility testing. Add Botania and only its required dependencies first, verify that a new world loads, and then add the rest of your mod list.
Read the log when the loader rejects a mod
Loader errors usually identify a missing dependency, unsupported version range or incompatible mod type. The first clear dependency or version message is more useful than later stack traces caused by the same failure.
When a modpack is involved
Use the loader and versions defined by the pack unless the pack author documents an upgrade path. Manually replacing one core mod can break scripts, recipes or integrations even if Minecraft starts.
Practical rule
Do not assume a Botania file supports a Minecraft version or loader unless that exact combination is stated for the build you are using. Keep the loader, dependencies and Minecraft version aligned.
Related Botania guides
Continue with the full guide library, the installation checklist or the troubleshooting guide.