Recommended Free Tools
Use legacy Cauldron only when your modpack and plugins target Minecraft 1.6.4 or 1.7.10. It is a hybrid server platform that combines Forge mods with Bukkit plugins. Install the matching Cauldron and Forge files with Java 8, accept the EULA, upload the completed directory to your host, and test with no optional content before adding mods and plugins one at a time.
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 you need
Legacy Cauldron is a hybrid Minecraft server platform. Its defining feature is running Forge mods and Bukkit plugins together in one server instance. That makes it useful for older modpacks that need both systems, but it also imposes strict version limits: the documented legacy server builds support Minecraft 1.6.4 and 1.7.10 only.
As an Amazon Associate I earn from qualifying purchases.
Do not confuse those server JARs with the current Cauldron documentation homepage, which describes a launcher-oriented project for creating and sharing vanilla or modded profiles. That project is not a replacement name for the old Cauldron server files. Forge also labels its older documentation as archival, so procedures and libraries differ from modern Minecraft server setup.
Before downloading anything, write down the exact Minecraft version, Forge build, mods and Bukkit plugins your pack requires. A 1.7.10 server cannot be repaired by adding a 1.6.4 library or plugin later; every component must target the same legacy version.
#1 Best Overall
Check compatibility before installing
Supported Minecraft versions
| Component | Requirement | Why it matters |
|---|---|---|
| Legacy Cauldron server | Minecraft 1.6.4 or 1.7.10 | Those are the versions documented for the legacy hybrid platform. |
| Forge | The Forge release selected by your modpack for that Minecraft version | Cauldron must be built for the same Forge/Minecraft combination. |
| Mods | All must target the chosen Minecraft and Forge release | A mod for another game version will usually fail during loading. |
| Bukkit plugins | Plugins that support the selected legacy server/API | Modern plugin builds may require APIs unavailable in legacy Cauldron. |
| Java | Java 8; project documentation specifies JDK 8u101 or newer for builds | Newer Java runtimes can cause Forge or server startup errors. |
Keep separate directories for 1.6.4 and 1.7.10. Never merge their libraries, configuration files or generated worlds. Make a backup of any existing server before replacing a JAR or changing Java.
Confirm the Java runtime
Use a Java 8 installation for the documented legacy stack. Contigo and Thermos build documentation specify a Java 8u101 JDK or higher. For comparison, Magma’s 1.12 documentation states that Java 8 is required and Java 9 or later does not work with Forge 1.12; this illustrates why a legacy Forge server should use the runtime named by its project rather than the newest Java release.
Check the runtime on the machine where you will run the installer and on the final server host:
java -versionThe output should identify Java 8. If your host offers several runtimes, select its Java 8 option in the control panel or startup configuration. Installing Java 8 on your desktop does not automatically change the Java executable used by a remote host.
Files you need
The legacy installation workflow uses a set of version-matched files rather than a single universal download:
- The Cauldron installer JAR for the exact Minecraft/Forge version.
- The generated Cauldron server JAR (for example, a 1.7.10 build named
cauldron-1.7.10-server.jar). - The corresponding CauldronBukkit file, when supplied with that build.
- The Forge installer and the vanilla Minecraft server JAR required by the selected release (a 1.7.10 bundle can include
minecraft_server.1.7.10.jar). - The libraries directory and any files generated by the installer.
- An EULA file and a launch script.
Download plugins only from a trusted Bukkit, Spigot or plugin-author source, and verify that each download names your Minecraft version. Keep the original installer and downloaded files outside the live server directory as a recovery copy.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteInstall Cauldron locally
Run the installer on your own computer first, then deploy the completed server directory. This approach lets you inspect generated files and resolve missing dependencies before involving a hosting control panel.
- Create a new working folder. Use a path dedicated to the chosen version, such as
Cauldron-1.7.10. Do not place it inside another Minecraft server’s directory. - Place the matching installer and required server files in that folder. Keep the Forge installer, vanilla server JAR and Cauldron files together when the release instructions require them.
- Run the Cauldron installer with Java 8. From a terminal opened in the working folder, launch the installer using your Java 8 executable. The exact filename varies by release; use the name you downloaded.
java -jar <cauldron-installer-file>.jarReplace the angled-bracket filename with the real installer name; do not type the brackets. The installer creates or populates libraries and server files. If it exits with a Java or Forge error, stop and correct the runtime or version selection instead of copying partial output to the host.
- Review the generated directory. A usable 1.7.10 bundle commonly contains libraries,
cauldron-1.7.10-server.jar, the Forge installer,minecraft_server.1.7.10.jar, an EULA file and a run script. Names vary by release, but the files must all belong to the same version. - Run the generated server once. Use the supplied script or a Java 8 command that points to the generated Cauldron server JAR. The first run may stop while creating
eula.txt; that is expected until the EULA is accepted.
Accept the Minecraft EULA
Open eula.txt in the server directory and change the setting to:
eula=trueSave the file without changing its name or location. A missing file or a value of false prevents the server from starting. Start the server again and watch the console for a clean completion rather than closing it immediately after the first informational messages.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Upload the finished server to a host
- Stop the local test server. Copy the entire working directory, including
libraries, configuration files, the server JAR, EULA and script. Do not upload only the JAR; Cauldron relies on its generated libraries and supporting files. - Create an empty server directory on the remote machine. Use the host’s file manager or an FTP account. Keeping the destination empty prevents an older Forge or Bukkit file from being loaded accidentally.
- Upload the directory contents. Transfer in binary mode when your FTP client offers a choice, and preserve folder names and capitalization.
- Select Java 8 and the Cauldron launch target. In a control panel, choose the Java 8 runtime and set the startup JAR or command to the generated Cauldron server file. If the host uses a script, edit that script only after confirming the JAR’s exact name.
- Start without optional mods or plugins. Confirm that the remote console reaches a normal ready state. Only then copy in the modpack and plugin files.
Keep a zipped copy of the known-good directory before installing additions. It gives you a rollback point if a later plugin or configuration change prevents startup.
Host requirements and deployment planning
Cauldron needs a server destination that lets you upload files and choose an appropriate startup command. Before purchasing or configuring hosting, confirm that the provider offers FTP or an equivalent file manager, permits a custom server JAR or launch script, and exposes a Java 8 runtime. A host that only supplies a modern Java runtime or locks you to a different startup file may not be suitable for this legacy stack.
Ask the provider where the server’s working directory is located and whether the control panel can preserve subdirectories such as libraries, mods, plugins and config. Uploading only the visible JAR from a file manager is not enough. The generated libraries and supporting files are part of the installation. Keep the local copy until the remote instance has started successfully and you have confirmed that the console and in-game connection behave as expected.
No universal Cauldron hosting guarantee exists. Treat provider compatibility as something to verify against the exact 1.6.4 or 1.7.10 build, Java setting and mod/plugin list. A hosting comparison can help you evaluate file access and runtime controls, but do not assume that a provider supports Cauldron simply because it supports Minecraft generally.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →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.
Add mods and plugins safely
Install the Forge mods
Stop the server, place only the mods intended for the selected Minecraft/Forge version in the server’s mods directory, and start again. Add a small group or one mod at a time so the first failing addition is identifiable. Read the console for the mod ID and required dependency when loading stops.
Install Bukkit plugins
After the Forge-only test succeeds, stop the server and place compatible plugin JARs in the plugins directory. Start the server, check that each plugin enables successfully, then test its commands in game. A plugin that loads but targets a different API can still produce permission, event or world errors, so test its actual features rather than relying only on a green startup line.
Preserve configuration and world backups
- Back up the world,
config,mods,pluginsand generated server files before each change. - Record the versions of Cauldron, Forge, Java, every mod and every plugin in a text file.
- Change one variable at a time; do not update Java, Cauldron and several plugins in one maintenance window.
Common failures and the fastest fix
| Symptom | Likely cause | Action |
|---|---|---|
| Server stops immediately and mentions the EULA | eula.txt is missing or still says false. |
Set eula=true in the server directory, save it, and restart. |
| Forge errors appear before the world loads | Wrong Java version, Forge build or mismatched Cauldron files. | Verify Java 8, then re-check that Minecraft, Forge and Cauldron all target 1.6.4 or all target 1.7.10. |
| A mod fails to load with a version or dependency message | The mod targets another Minecraft/Forge release or needs a missing dependency. | Remove it, obtain the exact compatible build and add it back only after the base server starts. |
| A plugin is ignored or throws API errors | The plugin targets another Bukkit/Spigot API or game version. | Use a release that explicitly supports the selected legacy version; otherwise leave the plugin out. |
| The local server works but the hosted server does not | Files were omitted, the host is using another Java runtime, or the startup JAR is wrong. | Compare the remote directory with the local copy, select Java 8 and verify the launch target. |
| Errors continue after removing one suspect file | A configuration file or another add-on is retaining the conflict. | Move optional mods/plugins out, reset the relevant configuration to defaults, and reproduce the problem in a minimal installation. |
When diagnosing, capture the first meaningful error and the stack trace that follows it. Later messages often describe shutdown consequences rather than the original fault. Test the same change in a clean backup directory before applying it to a live world.
Compiling a Cauldron-derived project instead of installing a release
Most server owners should use a compatible release build. Source compilation is appropriate only when a project specifically requires it or you are maintaining a fork. The documented pattern used by Cauldron-derived projects such as Contigo, Thermos and Uranium is:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches- Install Git, a Java 8u101-or-newer JDK and the build prerequisites stated by the project.
- Clone the exact repository revision you intend to build.
- Initialize its submodules.
- Run the project’s setup task, commonly named
setupCauldron. - Build the server JAR with the Gradle wrapper.
git clone <repository-url>
cd <repository-directory>
git submodule update --init --recursive
./gradlew setupCauldron
./gradlew setupCauldron jarRepository-specific instructions take precedence over this pattern; task names and required environment variables can change. A successful build does not make arbitrary mods or plugins compatible, so apply the same version checks and minimal testing used for a downloaded release.
Migration, rollback and maintenance
For an existing server, do not overwrite the live installation immediately. Stop it cleanly, copy the world and the complete server directory, and perform the Cauldron test in a separate folder. Keep the old JAR, libraries and configuration together so you can restore the previous state if the new launch fails. A backup made after a failed conversion is less useful than one made while the original server is still known to work.
When moving from local testing to hosting, compare filenames and directory contents rather than assuming that a successful upload transferred everything. Check the Java selection again after every host change. If a later mod or plugin causes a failure, remove only that addition first; if the error remains, restore the known-good archive and reproduce the change in a minimal copy. This preserves the production world while you isolate the conflict.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →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"!
Because the platform and its Forge documentation are archival, record the exact download locations, version numbers and Java build used for a working installation. That record is valuable when a legacy file disappears or a replacement host uses different defaults. Avoid changing several components at once: a Java update, Cauldron replacement and plugin update in one maintenance window make the first cause difficult to identify.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Is Cauldron suitable for a newer Minecraft server?
No. Legacy Cauldron is not a general modern-server solution. Its documented coverage ends at 1.7.10, and its Forge documentation is archival. If your modpack targets a newer release, investigate a maintained hybrid project that explicitly supports that release instead of forcing Cauldron files into it.
For example, Magma Forge documents a 1.12 installation path: download a recommended release, put its JAR in a new directory and run it with Java. Its documentation states that Java 8 is required and Java 9 or newer does not work with Forge 1.12. Treat that as a separate platform, not as a drop-in Cauldron update. Check the project’s current release notes and test your exact mod and plugin list before migrating a production world.
| Decision point | Legacy Cauldron | Newer hybrid project |
|---|---|---|
| Minecraft coverage | 1.6.4 and 1.7.10 only | Depends on the project’s current releases; verify the exact target version. |
| Mods and plugins | Forge mods plus Bukkit plugins built for the same legacy version | Only the combinations explicitly supported by that project. |
| Java | Java 8; build documentation specifies 8u101 JDK or newer | Use the runtime stated in the alternative’s documentation. |
| Installation model | Local installer, generated files and FTP/file-manager upload | Often a release JAR or host-specific installer. |
| Maintenance | Legacy and archival documentation | Check current releases, issue activity and compatibility notes before committing a world. |
Practical pre-launch checklist
- Choose exactly 1.6.4 or 1.7.10.
- Match the Forge build, Cauldron build, mods and plugins to that choice.
- Install and select Java 8; use a Java 8u101-or-newer JDK when compiling.
- Run the installer locally and retain all generated libraries and files.
- Set
eula=truein the correct server directory. - Test a clean server before adding optional content.
- Upload the complete directory, not only the server JAR.
- Add mods and plugins incrementally, backing up the world before each change.
- Keep a known-good archive and a written version list for rollback.
- For newer Minecraft versions, choose a project that explicitly supports the target release instead of legacy Cauldron.
If all ten checks pass, Cauldron can provide the older Forge-plus-Bukkit combination it was designed for. The narrow version range and archival status are the boundaries to plan around, not problems that can be solved by mixing files from different releases.
Frequently Asked Questions
Can Cauldron run Forge mods and Bukkit plugins together?
Yes. That hybrid combination is Cauldron’s purpose, provided every mod, plugin, Forge build and Cauldron file targets the same Minecraft version and compatible API.
Does Cauldron work with Minecraft 1.7.10?
Yes. Legacy Cauldron builds are documented for Minecraft 1.7.10 and 1.6.4 only. Do not combine files from those two versions.
Which Java version does legacy Cauldron need?
Use Java 8 for the documented server stack. Contigo and Thermos specify a Java 8u101 JDK or newer when building derived projects. Confirm that both your local machine and host use Java 8.
Can I install Cauldron directly on my hosting panel?
The documented workflow runs the installer locally, then uploads the completed directory by FTP or file manager. Your host must allow the generated files, a custom startup target and Java 8.
Why does Cauldron stop before the world loads?
Check the first error for a missing or false EULA, wrong Java runtime, mismatched Forge/Cauldron files, or an incompatible mod. Remove optional content and reproduce the issue in a clean directory.
Is the current Cauldron launcher the same as the old server platform?
No. The current documentation homepage describes a launcher-oriented profile project. Legacy Cauldron server JARs are the hybrid Forge-and-Bukkit platform covered by this installation procedure.
Should I compile Cauldron from source?
Usually not. Install a compatible release. Compile only when maintaining a derived project or when its instructions require it, using the repository’s setup task and Java 8 build requirements.
What should I use for Minecraft versions newer than 1.7.10?
Use a maintained hybrid project that explicitly supports your target version. Magma Forge documents a 1.12 path, but it is a separate platform; verify current releases and your exact mod/plugin list before migrating.
The Bottom Line
Install legacy Cauldron only for a deliberately matched 1.6.4 or 1.7.10 setup. Use Java 8, run the installer locally, keep every generated library, accept the EULA, upload the complete directory, and add mods and plugins incrementally. For newer Minecraft releases, choose a maintained hybrid server instead.
Quick Recap
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.
