Installing a large content mod is straightforward when every file belongs to the same environment. Most problems come from mixing a correct mod file with the wrong Minecraft version, loader or dependency.
1. Choose the Minecraft instance
For the original project, start with a Java Edition 1.20.1 instance. Keep it separate from vanilla and from newer community-port profiles so you can change files without affecting other worlds.
2. Install the matching mod loader
Use the loader required by the compiled release you choose. Original public listings include Forge and NeoForge. Do not place a Fabric build into a Forge instance or vice versa.
3. Add required dependencies
Original Alex’s Caves documentation lists Citadel. Install the dependency version compatible with the same Minecraft and loader environment. Community ports may use different dependencies.
4. Place compiled JAR files in mods
A normal loader-based setup reads compiled mod JARs from the instance’s mods directory. A GitHub source ZIP is source material, not a direct substitute for a compiled release JAR.
5. Test before using an important world
Launch the game, confirm the mod list loads, create a temporary world and play long enough to verify startup stability. Then back up and open an important save only after the base setup works.
Next step
Return to the main compatibility section before downloading so you can compare edition, Minecraft version, loader and file type in one place.