To host Craft to Exile: Dissonance, use the pack’s dedicated Minecraft 1.15.2 Forge server files, run them with 64-bit Java 17, give the process about 4–8 GB of RAM, accept the EULA during first startup, and configure port forwarding before inviting players over the internet. Do not use the files for Craft to Exile 2, which is a different pack and Minecraft version.
Godlike.Host offers modded Minecraft server hosting with one-click modpacks, a built-in mod installer and up to three free backups a day.
Use the correct Dissonance files first
Craft to Exile: Dissonance is the older Forge-based pack. The project’s official files listing identifies Dissonance version 3.1.9 for Minecraft 1.15.2 and provides a separate server-pack download. Craft to Exile 2 is a different project line built for Minecraft 1.20.1. Its files cannot be substituted for Dissonance’s server pack.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The most common setup mistake is downloading only the client archive. A client installation can launch the game, but it does not provide the complete server layout, startup scripts, and server-side files required to host a world. Download the dedicated server files from the Dissonance project’s files page, and keep every player on the same Dissonance release and loader.
What you need before installing
- A 64-bit operating system on the machine that will run the server.
- 64-bit Java 17 installed and available to the server process.
- The Dissonance dedicated server archive for the Minecraft 1.15.2 release.
- At least 4 GB of memory available to the server; planning for 4–8 GB gives more room for several players, exploration, dimensions, and mod activity.
- Administrator access to create a folder, extract files, and allow the Java process through the operating system firewall.
- Router access if people outside your home network will connect directly.
- A matching Dissonance client installation for each player.
The project recommends at least 4 GB with custom arguments, while the practical planning range for this guide is 4–8 GB. Treat that as an allocation target, not a performance guarantee: the available sources do not publish an independent tick-rate test, FPS measurement, or player-capacity benchmark.
#1 Best Overall
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Download and prepare the server pack
- Open the official Craft to Exile: Dissonance files page and select the Dissonance 1.15.2 release. Confirm that the download is the separate server pack, not only the client files.
- Create a dedicated folder for the server. A short path such as
C:GamesDissonanceServeron Windows or~/servers/dissonanceon Linux or macOS makes later maintenance easier. Avoid placing the files inside a cloud-synchronised folder. - Extract the complete archive into that folder. Do not run the script from inside the compressed file, and do not move individual mods out of the supplied structure.
- Keep a copy of the original archive somewhere safe. It is useful when comparing files after an update or rebuilding the installation.
The extracted directory should contain the supplied startup script and the server files it calls. If you see only a launcher profile or a collection of client mods, you have the wrong download.
Install and verify Java 17 64-bit
Dissonance’s server instructions explicitly require Java 17 64 bit. A newer or 32-bit runtime can cause the script to fail, select the wrong executable, or leave too little addressable memory for a modded server.
Windows check
- Install a 64-bit Java 17 distribution from a trusted Java provider.
- Open Command Prompt and run
java -version. - Confirm that the output identifies Java 17 and a 64-bit virtual machine. If Windows reports that
javais not recognised, add the Java installation’sbindirectory to the system PATH or configure the supplied script with the full Java path.
Linux or macOS check
- Install a 64-bit Java 17 package using your operating system’s normal package method.
- Run
java -versionin a terminal. - Check that the selected runtime is Java 17 and 64-bit. If more than one Java version is installed, select Java 17 as the default or edit the script to call its absolute executable path.
Do this check before troubleshooting mods. A server that never reaches its first startup is often failing at the Java or script stage rather than inside Dissonance itself.
Start the server for the first time
Windows
- Open the extracted server folder in File Explorer.
- Double-click
run.bat. If Windows blocks the file, use the context menu to allow it or launch it from Command Prompt so the error remains visible. - Allow the first run to create the configuration, libraries, world directory, and other generated files.
- Read the console output. Stop and correct any Java, permission, or missing-file error before continuing.
Linux or macOS
- Open Terminal and change to the server directory with
cd. - Make the script executable if necessary, for example with
chmod +x run.sh. - Start it with
./run.sh. - Leave the terminal open while the first-run files are generated so you can read the complete error output.
The project’s operational instructions use run.bat on Windows and run.sh on Linux or Mac. Do not substitute the client launcher’s play button for these server scripts.
Accept the Minecraft EULA and complete first-run setup
On its initial launch, the server normally creates files and then stops or pauses until the Minecraft EULA is accepted. Follow the prompt shown in the console. If an eula.txt file appears, open it, read the linked agreement, and change the acceptance setting as instructed by the file. Save it in the same server directory.
- Stop the process if it is still running and waiting for the EULA.
- Open the generated EULA file and set the acceptance value to the required affirmative setting.
- Save the file without changing its name or extension.
- Run the same startup script again.
- Wait for the console to finish generating the world and report that the server is ready for commands before attempting to join.
First startup can take longer than later launches because libraries, configuration files, and world data are being created. Do not repeatedly kill the process while files are being written.
Crashes, 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 minuteWindows 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 reinstallSet memory and Java arguments sensibly
Dissonance’s project guidance calls for at least 4 GB with custom arguments, and a 4–8 GB planning range is appropriate for a self-hosted instance. The exact argument syntax is controlled by the supplied script or configuration. Use the existing script as the source of truth rather than replacing it with a generic vanilla command.
Choose an allocation
- 4 GB: a starting point for a small group and conservative world activity, provided the host machine has additional memory for the operating system.
- 6 GB: a middle setting when several players will explore, run machines, or use multiple dimensions.
- 8 GB: useful when the host has sufficient physical memory and the group expects heavier mod interaction.
Do not assign every gigabyte in the computer to Java. The operating system, file cache, voice software, and other services still need memory. If the server begins swapping or the whole machine becomes unresponsive, reduce the allocation or move the server to a machine with more physical RAM.
Change settings safely
- Stop the server cleanly using its console stop command rather than closing the window while the world is saving.
- Make a backup copy of the startup script before editing it.
- Change only the memory values or arguments you understand, preserving quotation marks and line breaks.
- Restart and watch the first several minutes of console output for invalid-argument or out-of-memory errors.
No independent benchmark establishes a guaranteed number of players, TPS value, or FPS result for Dissonance. Treat memory as a capacity and stability setting, not as a promise of a particular frame rate.
Make the server reachable by friends
Players on the same local network can usually connect using the host computer’s local address once the server is running. Internet players need a route from the router to the server machine. The Dissonance wiki directs administrators to modded-Minecraft Discord guidance for port-forwarding details because router interfaces differ by manufacturer and internet provider.
Local-network checklist
- Start the server and wait until it is ready.
- Allow Java or the server process through the operating system firewall when prompted.
- Give the host computer a stable local address, preferably through a DHCP reservation in the router.
- Have a player on the same network test the host’s local address before debugging internet access.
Internet checklist
- Identify the server computer’s local address and the listening port shown in the server configuration.
- Create a router port-forwarding rule that sends that port to the server computer’s local address, using the protocol specified by the server configuration.
- Permit the same traffic in the computer’s firewall.
- Check whether the internet provider uses carrier-grade NAT. If it does, ordinary router forwarding may not provide an inbound route.
- Give friends the public address and configured port, while keeping administrative credentials and the router login private.
Port forwarding exposes a game service to the internet. Keep the operating system patched, avoid forwarding unrelated services, use strong router credentials, and remove the rule when the server is no longer needed. If the router or provider prevents inbound connections, use a managed game host instead of repeatedly changing random settings.
Install the matching client and join
Each player should install the same Dissonance release through CurseForge, GDLauncher, or MultiMC. The installation wiki says the launcher supplies the required components on first launch and then asks the player to log in with a Minecraft account.
Rank #4
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
- Choose one supported launcher and install the Dissonance profile for the same release used by the server.
- Launch it once so the launcher can install its required components.
- Complete the Minecraft account login requested by the launcher.
- Confirm that the profile uses the Dissonance 1.15.2 Forge setup rather than a Craft to Exile 2 profile.
- Set the client’s memory high enough for the modpack while leaving memory for the operating system and other applications.
- Start the game, open multiplayer, and enter the server address supplied by the administrator.
Every participant must use the same modpack version and loader as the server. A mismatched client can produce missing-mod, incompatible-version, registry, or authentication errors before the player reaches the world. When a player cannot join, compare the exact profile version first, then inspect the client and server logs for the first error rather than the final disconnect message.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteWhat to do during the first session
Dissonance changes progression, recipes, loot, dimensions, and the quest structure, so a new player should not approach it like an unmodified Minecraft world. The official project page recommends remaining in the Overworld until level 15 while learning the Mine and Slash systems.
Use the quest log
Quest chapters provide the intended route through the pack’s systems. Read the quest log before crafting unfamiliar components; altered recipes mean a vanilla recipe guide may point to the wrong ingredients. The project describes chapters connected with technology and colony-oriented play, so progression is broader than basic shelter and mining.
Form a party
For cooperative play, create a party with /slash party. Confirm that everyone is in the same party before splitting up for quests or exploration. Party play also gives the group a shared way to decide when to leave the Overworld and begin testing additional dimensions.
Keep early goals modest
- Learn Mine and Slash combat and progression in the Overworld.
- Advance through the quest log instead of rushing into every dimension.
- Record unusual recipes and loot requirements for the group.
- Use a shared storage and backup routine before major exploration.
Self-hosting versus a managed server
Self-hosting costs no separate game-hosting subscription, but the administrator supplies the time, hardware, networking, backups, and troubleshooting. The project wiki also describes a managed-host path that can automate modpack setup. Choose based on who will operate the server, not only on the headline price.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →| Decision area | Self-hosted Dissonance server | Managed hosting |
|---|---|---|
| Initial setup | Install Java 17, download and extract the server pack, run the supplied script, accept the EULA, and configure the machine. | The provider may automate installation of the modpack and server instance; verify that it supports the exact Dissonance 1.15.2 release. |
| Monthly cost | No separate hosting bill, but the host machine uses electricity and requires administration. | A recurring charge; current pricing is not established here and must be checked with the provider. |
| Memory | You choose within the machine’s available physical RAM, planning around 4–8 GB for Dissonance. | Select a plan whose stated allocation meets the pack’s requirements; confirm whether advertised memory is dedicated. |
| Network access | You handle port forwarding, firewall rules, public addressing, and any carrier-grade-NAT limitation. | The provider normally supplies a reachable address, but confirm how access is exposed and protected. |
| Files and updates | Full control over the server folder, configuration, worlds, and update timing. | A control panel may simplify file transfer and updates; verify that you can pin the required Dissonance version. |
| Backups | You must schedule, test, and store backups outside the live world folder. | Backups may be included or paid; check retention, restore access, and whether backups are automatic. |
| Restarts | You create your own restart routine and must be present when the process fails. | Many hosts provide scheduled restarts and crash recovery; confirm what is included. |
| Support | Diagnosis is your responsibility, including Java, mods, firewall, and router issues. | Support scope varies. Ask whether staff support the exact Dissonance release or only the underlying panel. |
Before paying for a managed instance, verify current Dissonance support, the available RAM, storage limits, backups, update controls, and the provider’s policy for modded Forge packs. A generic Minecraft plan is not automatically compatible with this older pack.
Backups, updates, and routine administration
Back up before changes
- Stop the server cleanly so world files are closed.
- Copy the world directory and the server configuration to storage outside the live server folder.
- Label the backup with the date, Dissonance version, and any major configuration change.
- Keep more than one restore point and periodically test that a copy can be opened.
Update deliberately
Do not overwrite a working Dissonance installation with Craft to Exile 2 files or an unrelated Minecraft version. Read the project’s release notes, download the matching server pack, and preserve the existing world and configuration backups before replacing files. Have every player update the client profile to the same release before restarting a shared world.
Watch the console
During normal play, monitor repeated warnings, memory errors, and save failures. A clean shutdown, current backup, and documented Java version make recovery much easier than deleting files in response to a single warning.
Quick Recap
Troubleshooting by symptom
The script closes immediately
- Run the script from Command Prompt or Terminal so the error remains visible.
- Check that Java 17 64-bit is installed and that the script can find it.
- Confirm that the archive was fully extracted and that the script is in the expected server folder.
- Restore the original script if a memory-argument edit introduced invalid syntax.
The server asks for the EULA repeatedly
- Stop the process and check that the EULA file is in the server directory, not the download folder.
- Confirm that the acceptance setting was saved with the exact filename and extension.
- Ensure the account running the server has permission to write the directory.
Players on the same network can join, but friends cannot
- Recheck the router rule’s destination address and listening port.
- Allow the Java process through the operating system firewall.
- Test whether the internet connection uses carrier-grade NAT.
- Ask the remote player to use the public address, not the host’s local address.
A client reports missing mods or an incompatible version
- Compare the client’s Dissonance release with the server’s release number.
- Confirm that both sides use the Dissonance 1.15.2 Forge profile.
- Remove accidental Craft to Exile 2 profiles or unrelated mod additions.
- Read the first specific missing-mod or registry message in the log and correct that item before trying again.
The machine becomes unresponsive
- Check whether Java was given more memory than the host can spare.
- Reduce the allocation within the 4–8 GB planning range or move the server to a machine with more physical RAM.
- Close other memory-heavy applications and check disk space for world saves.
Final setup checklist
- Dissonance 3.1.9 for Minecraft 1.15.2 is installed on the server.
- The dedicated server pack, rather than only a client ZIP, was extracted.
- Java 17 64-bit is confirmed with
java -version. - The supplied
run.batorrun.shstarts the server. - The EULA was accepted after first-run files were generated.
- Memory is planned at 4–8 GB, with enough RAM left for the operating system.
- The firewall permits the server process.
- Port forwarding is configured for remote play, or a managed host is being used.
- Every player has the same Dissonance version and Forge loader.
- A clean backup exists before the group begins major progression.
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.
Recommended Free Tools
