Install Cauldron by matching the exact Minecraft and Forge version, preparing the installer and server files on your own computer, accepting the EULA, uploading the complete directory to your host, and starting the server with Java 8. Legacy Cauldron is not a modern all-version server: its documented support is limited to Minecraft 1.6.4 and 1.7.10. The procedure below keeps those version, Java, mod, and plugin requirements aligned so you can run Forge mods and Bukkit plugins together with fewer compatibility failures.
Godlike.Host offers modded Minecraft server hosting with one-click modpacks, a built-in mod installer and up to three free backups a day.
What Cauldron is—and which Cauldron project you need
Legacy Cauldron is a hybrid Minecraft server platform. It combines a Forge-based server with a Bukkit-compatible layer, allowing one server to load Forge mods and Bukkit plugins. That combination is the reason to use it: a conventional Forge server does not automatically provide Bukkit plugin support, while a conventional Bukkit server does not provide Forge mod loading.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →The name is also used by a separate, launcher-oriented Cauldron documentation project for creating and sharing vanilla or modded profiles. That project is not the legacy server JAR used for this installation. When downloading files, identify the server release and its matching installer rather than assuming every page titled Cauldron supplies a deployable server platform.
Forge’s old documentation describes earlier releases as archival. Treat a Cauldron server as legacy infrastructure: preserve a working backup, avoid changing Java or content versions casually, and verify every mod and plugin against the exact Minecraft release before replacing files.
#1 Best Overall
Supported Minecraft versions and the compatibility rule
| Component | Required alignment | Why it matters |
|---|---|---|
| Cauldron | Minecraft 1.6.4 or Minecraft 1.7.10 | Host Havoc’s June 9, 2026 installation guide identifies these as the supported legacy versions. |
| Minecraft server | The same release selected for Cauldron | A server built for one release cannot be repaired by adding files from the other. |
| Forge | The Forge build expected by that Cauldron release and your modpack | Forge APIs and internal names differ between legacy Minecraft versions. |
| Mods | Every mod must target the selected Minecraft/Forge combination | A mod for another release can fail during startup, world loading, or gameplay. |
| Bukkit plugins | Plugins must support the legacy Bukkit API exposed by your Cauldron build | Newer plugins may require API behavior unavailable on an old server. |
Choose the Minecraft and Forge combination first. Do not begin by downloading a random Cauldron JAR and trying to adapt a modpack afterward. If your pack is built for 1.7.10, all server files, mods, and plugins should be selected for 1.7.10. A 1.6.4 file is not an upgrade or a fallback; it belongs to a different software stack.
Java requirement
Use Java 8 for the documented Cauldron family. Contigo and Thermos both specify a Java 8u101 JDK or newer as a build requirement. In practice, use a Java 8 runtime for a released server as well, because legacy Forge code can fail under newer Java versions even when the server JAR itself appears to launch.
- Install a 64-bit Java 8 distribution when the operating system and available memory are 64-bit.
- Confirm that your hosting panel or startup service points to Java 8, not whichever Java executable happens to be first in the system path.
- Keep the Java 8 installation available during troubleshooting; changing runtimes while also changing mods makes the cause of an error harder to identify.
Java requirements for a different hybrid platform do not automatically apply to Cauldron. For example, Magma’s 1.12 documentation says Java 8 is required and that Java 9 or higher does not work with Forge 1.12. That statement concerns Magma’s Forge 1.12 stack, but it reinforces the broader rule: select the runtime documented for the exact platform and Minecraft version you are deploying.
Files you need before starting
Prepare the files for one version only. The installation workflow described by Host Havoc calls for an installer JAR, the matching server JAR, and a CauldronBukkit file. Your release may generate or bundle additional libraries and configuration files during installation.
- Cauldron installer JAR: run this on your own computer to create the server bundle.
- Matching Minecraft server JAR: use the server artifact expected by the selected Forge and Cauldron release.
- CauldronBukkit file: include the file supplied for the same version; do not substitute one from another build.
- Forge installer or Forge files: use the Forge release required by the Cauldron package and modpack.
- Java 8: required to run the legacy stack and, where applicable, its installer.
- Remote server access: FTP or a host file manager is needed to upload the completed directory.
Download plugins only from sources you trust, such as an established Bukkit or Spigot distribution page or the plugin author. A plugin archive can contain executable server code; do not treat an attractive download page or an unverified reupload as proof of safety or compatibility.
Step 1: Choose and document the exact stack
- Write down the target Minecraft version, Forge build, Cauldron build, mod list, and plugin list before installing anything.
- Check each mod’s release notes or download page for the same Minecraft version and Forge family.
- Check each plugin’s supported Bukkit API and legacy compatibility. Remove plugins that require a newer API than your server exposes.
- Decide whether you are installing a released Cauldron build. Most administrators should use a compatible release rather than compiling from source.
This inventory is useful when a server fails: you can identify whether the first change was a Java runtime, a Cauldron file, a mod, a plugin, or a configuration edit. Keep a copy of the list with your server backup.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchStep 2: Run the installer on your local computer
Cauldron’s documented workflow runs the installer locally first. Create a new working directory on your computer instead of placing the installer into an unrelated existing server. Put the matching installer, Minecraft server JAR, Forge files, and CauldronBukkit file where the installer can access them.
- Open a terminal or command prompt in the working directory.
- Use Java 8 to launch the Cauldron installer JAR.
- Allow the installer to generate its libraries, server artifacts, and configuration structure.
- Read the installer output for missing files or version errors before copying anything to a host.
The exact installer switches can vary by release, so follow the instructions packaged with your chosen build. Do not add arbitrary command-line options from a guide written for another Cauldron or Forge version. A successful local installation should leave you with a self-contained server directory that can be copied without relying on files hidden elsewhere on your computer.
Step 3: Build a clean server directory
After the installer finishes, gather the generated files into one directory. A 2026 setup description lists libraries, cauldron-1.7.10-server.jar, the Forge installer, minecraft_server.1.7.10.jar, eula.txt, and a run script in the working bundle. Names differ for 1.6.4, so use the names produced by your selected release rather than renaming files to match an example.
- Keep the
librariesdirectory beside the server files if the installer created it. - Keep the Cauldron server JAR and its matching Minecraft/Forge files together.
- Keep the run script in the same directory, then inspect it for the Java executable and JAR name it calls.
- Do not merge this directory with an old world, old libraries, or another Minecraft version until the new server starts cleanly.
- Copy the entire directory before adding optional mods, plugins, or custom configuration.
A clean directory gives you a known-good baseline. If you start with an old directory full of unknown configuration files, a failure may be caused by stale settings rather than the Cauldron installation itself.
Free tools Windows power users keep installed
One-click scans. No signup required.
Step 4: Accept the Minecraft EULA
Locate eula.txt in the server directory. Open it in a plain-text editor and change the agreement line to eula=true. Save the file without changing its name or extension.
The server will not start when eula.txt is missing or when the value remains false. If your host regenerates the file after every failed launch, stop the server, edit the newly created file, and start it again. Accepting the EULA is an administrative prerequisite; it does not resolve Forge, mod, plugin, or Java errors.
Rank #3
- The classic UNO card game builds fun on game night with a Minecraft theme.
- UNO Minecraft features a deck and storage tin decorated with graphics from the popular video game.
- Players match colors and numbers to the card on top of the discard pile as in the classic game.
- The Creeper card unique to this deck forces other players to draw 3 cards.
- Makes a great gift for kid, teen, adult and family game nights with 2 to 10 players ages 7 years and older, especially Minecraft and video game fans.
Step 5: Upload the completed directory
Once the local bundle reaches a clean baseline, upload the entire server directory to the remote machine. Host Havoc’s prerequisite specifically describes FTP or a hosting file manager for this transfer.
- Stop any existing process in the destination directory.
- Create a new directory for the Cauldron instance so files from another server cannot be mixed in accidentally.
- Upload the libraries directory, server JARs, configuration files, EULA file, and run script.
- Check that file names and capitalization survived the transfer.
- Set the host’s startup profile to use Java 8 and the run script or server JAR supplied by your Cauldron release.
- Keep the local copy unchanged as a recovery source.
Do not upload only the main Cauldron JAR. Missing libraries or the wrong working directory can produce errors that look like a broken server when the actual problem is an incomplete deployment.
Recommended Free Tools
Step 6: Start and test a minimal server
Launch the uploaded server with Java 8 and no optional mods or plugins beyond what the Cauldron package requires. Watch the console from the first line through the final startup message instead of closing it as soon as a window appears.
- Successful baseline: the process remains running, completes its world initialization, and accepts a local or permitted client connection.
- Missing EULA: the process stops and points to
eula.txt; verify the file exists and containseula=true. - Java or Forge exception: stop and verify the runtime before changing content. A newer Java executable is a common mismatch for legacy software.
- Missing class or library: compare the remote directory with the local installer output and re-upload missing files.
Join the server with a client using the same Minecraft version and the required client-side mods. Test a new world or a disposable copy before opening an established world to players. This separates installation problems from world corruption and from mod interactions.
Step 7: Add mods and plugins incrementally
After the empty or minimal server starts, add content in small groups. Restart after each change and keep the console log from the first failed launch.
- Install the required Forge mods for the chosen Minecraft and Forge version.
- Start the server and verify that the world loads and the client can connect.
- Add one Bukkit plugin, or one tightly related plugin group, and restart.
- Test the plugin’s commands and permissions before adding another.
- Back up the working directory and world after each stable milestone.
Some mods and plugins alter the same registries, events, permissions, or world data. Cauldron makes the two ecosystems available together, but it cannot make every combination compatible. A plugin that works on a modern Bukkit server may depend on APIs absent from this legacy environment, and a Forge mod may assume behavior that a Bukkit bridge changes.
Rank #4
- Now Minecraft lovers can play a special version of UNO!
- Same as Basic UNO but features Minecraft characters and includes special Creeper rule card. Draw this card and the other players have to draw three more cards from the pile!
- The goal is to get rid of all the cards in your hand.
- First player or team to 500 wins.
- When you're down to one card, don't forget to yell "UNO"!
Common installation failures and precise fixes
Wrong Minecraft, Forge, or Cauldron version
Symptoms include immediate startup exceptions, missing methods, rejected mod files, or a client that cannot complete login. Stop the server and compare the version recorded in every filename, installer message, mod manifest, and plugin requirement. Replace the out-of-family file with the matching release; do not try to fix a 1.7.10 server by dropping in a 1.6.4 JAR.
Java is too new or points to the wrong installation
Check the Java executable configured by the host rather than relying on the Java version installed for another application. Switch the instance to Java 8, then retest with the same files. If the error disappears, record the runtime in your server documentation so a host migration does not silently select a newer Java.
The EULA file is absent or unchanged
Confirm that the file is named exactly eula.txt, is in the server’s working directory, and contains eula=true. Editors that append an extra extension can create eula.txt.txt, which the server will not read.
A plugin is untrusted or incompatible
Remove the newest plugin and restart. If the server recovers, check the plugin’s stated Minecraft and Bukkit support and obtain it from a trusted Bukkit, Spigot, or author source. Never diagnose several newly installed plugins at once; you will not know which one caused the failure.
A mod or plugin changed configuration
Stop the server, back up the current configuration, and reset the suspect mod or plugin’s settings to defaults. Uranium’s troubleshooting guidance recommends removing unnecessary content, using a minimal environment, and resetting configurations while reproducing a compatibility issue. Apply that method here: reproduce with only the required stack, then restore additions one at a time.
The remote upload is incomplete
Compare directory listings and file sizes between the local working bundle and the host. Re-upload the libraries directory and server artifacts rather than copying isolated error messages into a search for a replacement JAR. A partial deployment can create a different error on every restart.
Compiling a Cauldron-derived project instead of installing a release
Source builds are for administrators who specifically need a project’s development branch or a build unavailable as a release. They add another layer of variables and are not the normal path for a first installation.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsContigo and Thermos document the following general pattern:
- Clone the project repository.
- Initialize its Git submodules.
- Run
setupCauldron. - Build with
./gradlew setupCauldron jar.
Uranium documents the same general setup-and-build approach. Use the project’s own Java 8u101-or-newer JDK requirement and build instructions, because Gradle, mappings, submodules, and patch sets can change between repositories. A successful build is not proof that every mod or plugin is compatible; it only proves that the source produced a server artifact.
When legacy Cauldron is the wrong choice
Do not choose legacy Cauldron for a new server solely because you want Forge and Bukkit functionality together. Its documented Minecraft coverage is narrow, and its surrounding documentation is archival. If your modpack targets a newer version, find a hybrid project that explicitly supports that version and verify it against your complete mod and plugin list.
Magma Forge presents itself as a Forge hybrid server implementing the Spigot/Bukkit API and documents an installation path for Minecraft 1.12: download a recommended release, place its JAR in a new directory, and run it with Java. That is an alternative to investigate for 1.12-era requirements, not a drop-in replacement for a Cauldron world. Check the project’s current release notes, Java requirements, mod compatibility, plugin compatibility, and migration guidance before moving a live server.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →| Decision factor | Legacy Cauldron | Newer hybrid candidate |
|---|---|---|
| Minecraft coverage | Documented for 1.6.4 and 1.7.10 | Must be verified for the exact target release |
| Mods and plugins | Requires legacy Forge mods and compatible Bukkit plugins | Check each mod and plugin against the candidate’s API and implementation |
| Java | Java 8 stack; build documentation specifies Java 8u101 JDK or higher | Use the candidate project’s documented runtime |
| Installation model | Local installer, generated files, then FTP or file-manager upload | Often a release JAR or host-specific installer, depending on the project |
| Maintenance context | Legacy and archival documentation | Confirm active maintenance from current releases before migration |
Backups, upgrades, and safe maintenance
- Back up the world, configuration directory, mods, plugins, libraries, server JARs, and startup script before every change.
- Label backups with the Minecraft, Forge, Cauldron, Java, mod, and plugin versions.
- Test upgrades on a copied instance, never on the only production directory.
- Keep the last known-good server bundle so you can roll back a failed Java, mod, or plugin update.
- Document who has console and file access, since plugins execute with server privileges.
Because this platform is old, preservation matters more than chasing an unverified replacement file. A reproducible backup lets you continue operating a stable instance while you evaluate a modern migration separately.
Quick Recap
Installation checklist
- Target Minecraft and Forge version selected and recorded.
- Cauldron release matches that exact legacy version.
- Java 8 is installed and selected by the host.
- Installer, server JAR, CauldronBukkit file, Forge files, and libraries are present.
- Installer was run locally and produced a complete working directory.
eula.txtcontainseula=true.- Complete directory uploaded by FTP or file manager.
- Minimal server starts before optional content is added.
- Mods and plugins are added incrementally from trusted sources.
- Backups exist before configuration changes and upgrades.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
