Use the same Modded Together release, Minecraft version, NeoForge build and Java runtime everywhere. The current indexed release is Modded Together-1.3.6 HOTFIX for Minecraft 1.21.1, NeoForge 21.1.250 and Java 21. Install the matching server-pack archive rather than copying a client instance, and plan resources from player count and workload—not from the pack’s mod count alone.
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 Modded Together is and which release to use
Modded Together is a Minecraft Java Edition pack built around magic, technology, exploration and quest-driven progression. CurseForge describes its design as “Magic, technology and exploration, all designed to work together,” with systems intended for solo play or multiplayer. The project targets the adventure/RPG, quests, exploration, tech and magic categories and is owned by pitersonix.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft | Java & Bedrock Ultimate Collection | Windows Digital Code | $49.99 | Buy on Amazon |
| 3 |
|
Minecraft | Standard Edition | XBOX Digital Code | $19.99 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
At the time of the September 2026 project-page snapshot, CurseForge showed 137,495 downloads and an update dated September 28, 2026. The release you should select for a new installation is the one identified as Modded Together-1.3.6 HOTFIX.zip, dated September 24, 2026. CurseForge also lists a matching Modded_Together_server_pack.zip, dated September 28, 2026.
| Component | Value for the indexed 1.3.6 HOTFIX setup | Why it matters |
|---|---|---|
| Pack release | Modded Together-1.3.6 HOTFIX.zip | The client and server must use this exact file, not merely a similarly named version. |
| Minecraft | 1.21.1 | A different game version can prevent the loader or mods from starting. |
| Mod loader | NeoForge 21.1.250 | The loader build is part of compatibility; selecting only “NeoForge 1.21.1” may still choose the wrong build. |
| Java | Java 21 | Older or newer runtimes can produce class-version or startup errors. |
| Referenced mod projects | 510 | An analysis count for this pack file, not a memory requirement. |
| Client-only entries | 91 | These should not be copied into a dedicated server’s mods folder. |
| Server-only entries | 0 | The analysis did not identify entries labelled server-only. |
| Entries without a side label | 419 | Unlabelled does not mean safe to copy blindly; use the published server distribution. |
The 510-project figure indicates a substantial pack, but it is not an official RAM recommendation. The pack analysis itself warns against turning a mod count into a memory estimate.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
Prerequisites before you install
- Minecraft Java Edition. This pack uses the Java mod-loader ecosystem and is not a Bedrock add-on.
- A launcher that imports CurseForge packs. Install the pack as a separate instance so its mods and configuration do not mix with another profile.
- Java 21. Both the indexed client/server configuration and the required NeoForge setup use this runtime.
- A release decision. Ask everyone in the group to use 1.3.6 HOTFIX before anyone connects. Updating one machine while another retains an older archive is a common cause of mismatched-mod errors.
- Server storage and backups. Reserve space for the world, logs, configuration, generated data and backups before opening the server to players.
Do not add optional mods during the first installation. Establish a working, identical baseline first; only then make one controlled change at a time and keep a rollback copy.
Install Modded Together on each client
- Open a CurseForge-compatible launcher. Choose the option to create or import a modpack instance, then search for Modded Together.
- Select the exact release. Pick Modded Together-1.3.6 HOTFIX for Minecraft 1.21.1. Do not leave the launcher on “latest” if the server owner has selected a specific file.
- Keep the instance separate. Give it its own profile and directory. A separate instance prevents another pack’s mods, configs or resource files from being loaded accidentally.
- Confirm the loader. The profile should report NeoForge 21.1.250. If the launcher shows a different NeoForge build, correct it before launching.
- Set the Java runtime. Point the instance at Java 21. An installation that silently uses another Java executable may fail even though the pack files are correct.
- Allow the first launch to finish. A large pack can spend several minutes creating configurations and loading resources. Do not force-close it just because the first startup is slower than a vanilla launch.
- Join only after the server baseline is ready. Every player should compare the displayed pack version, Minecraft version and NeoForge build with the server operator’s values. Avoid manually adding or removing files to “make it work”; that creates a different instance.
If a launcher offers an update after you have joined a group, ask the server operator whether the server has been updated first. Client and server changes should be treated as one coordinated release.
Free tools Windows power users keep installed
One-click scans. No signup required.
Set up a dedicated Modded Together server
1. Obtain the matching server pack
Download the Modded_Together_server_pack.zip entry that corresponds to the selected 1.3.6 HOTFIX release. A server pack is preferable to copying a client installation because it is assembled for dedicated-server use. General CurseForge guidance warns that client-only files can crash a dedicated server.
Keep the archive with your backups and record its date. If several files have similar names, compare the Minecraft version, NeoForge build and release date rather than choosing by filename alone.
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
2. Prepare the runtime and an empty server directory
For the indexed release, configure Minecraft 1.21.1, NeoForge 21.1.250 and Java 21. Create an empty directory for the server, or select the server directory supplied by your hosting panel. Installing into an empty location makes it easier to see which files came from the server pack and avoids stale mods from an earlier attempt.
3. Extract or upload the server files
On a self-hosted machine, extract the server archive into the prepared directory. On a managed panel, choose the exact Minecraft and NeoForge versions first, then upload the server-pack contents. Depending on the release, the relevant folders can include:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →modsconfigdefaultconfigskubejsscriptsresourcepacksglobal_packs
Upload folders that are present in the server archive. Do not manufacture missing folders or replace them with files from a player’s client.
4. Do not copy the normal client directory blindly
The selected pack analysis reports 91 client-only entries, no entries labelled server-only and 419 entries without a side label. Those labels are useful context, but they are not a substitute for the published server distribution. Copying the entire client mods folder can load a class that exists only on the client and stop the dedicated server during startup.
Rank #3
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that is unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world full of surprises.
- SURVIVAL ADVENTURES — Face mysterious foes, travel across varied landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play solo or join friends in local split-screen and cross-platform play across console, mobile, and PC. Online multiplayer supports up to 8 players.
- COMMUNITY PLAY — Connect with players on community servers, or subscribe to Realms Plus (sold separately) to play with up to 10 friends on a private server.
5. Configure memory, the EULA and networking
For self-hosting, use the startup script included with the server package. Set the heap values in the pack’s JVM or variables file rather than inventing a different startup command. Accept the Minecraft EULA in the generated EULA file before the server will complete its normal startup.
Players on the same home network can normally connect using the host’s local address. Friends outside the home network need TCP port 25565 forwarded from the router to the server machine, plus a firewall rule that permits the server process. Exposing a port is a networking change: use a strong operating-system account, keep Java and the server files updated, and forward only the required port.
6. Start and verify the console
Run the supplied startup script or the panel’s start action. The first launch of a large pack can take several minutes while registries, configurations and world data are prepared. Wait for the console to report that startup has completed before connecting. Stop the server cleanly, make a backup, and only then begin normal play.
Keep the client and server identical
Most connection failures are synchronization failures rather than internet problems. Treat the following as one compatibility set:
Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
| Item | Client requirement | Server requirement |
|---|---|---|
| Pack archive | Modded Together-1.3.6 HOTFIX | Matching 1.3.6 HOTFIX server pack |
| Minecraft | 1.21.1 | 1.21.1 |
| NeoForge | 21.1.250 | 21.1.250 |
| Java | 21 | 21 |
| Mods and configuration | Launcher-generated pack files, unchanged | Server-pack files, with server-side configuration changes documented |
When one side is updated, update the other side as a planned change. Back up the world and configuration before replacing files so you can return to the last working combination.
How much RAM does a Modded Together server need?
A hosting listing for Modded Together describes 8–12 GB as typical usage and selects 12 GB for a small group with additional headroom for modded world generation and entities. That is provider guidance, not an official minimum, independent benchmark or guarantee. Use it as a starting range and adjust to your workload.
Recommended Free Tools
| Planning question | Effect on resource needs |
|---|---|
| How many players are online together? | More players create more entities, inventories, loaded chunks and network work. |
| How far is the view or simulation distance? | Higher distances keep more chunks active and increase generation and tick work. |
| Are players exploring new terrain? | New chunks are more expensive than revisiting an established area, especially during the first launch and early exploration. |
| How many entities or automation systems are present? | Machines, farms, mobs and item transport can raise sustained tick and memory pressure. |
| Have extra mods been added? | Added content changes the pack’s workload and invalidates assumptions based on the original distribution. |
The practical decision is to begin within the provider-stated range, monitor startup and play-session behavior, and change one resource variable at a time. Giving Java a larger heap does not fix a wrong loader, incompatible mod or client-only file.
Recognize memory and generation symptoms
OutOfMemoryError: Java heap space: increase the configured heap if the machine has physical memory available, or remove optional heavy additions. Check that the host is not enforcing a lower panel limit than the value in the JVM or variables file.- Very slow first launch: allow several minutes for a large pack. Repeated forced shutdowns can leave incomplete generated files and make diagnosis harder.
- Watchdog timeout during exploration: expensive world generation can block the server long enough to trigger the watchdog. Pregenerating chunks is a documented mitigation; do it before inviting the whole group and keep a backup first.
Self-hosting versus managed hosting
Self-hosting gives the owner direct control of files and avoids a recurring hosting bill, but the owner also becomes responsible for Java, operating-system updates, backups, router configuration and troubleshooting. A managed panel can install a pack with fewer manual steps, although the exact release, region, memory limit and backup policy must be checked before paying.
Best Value
- 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
| Factor | Self-hosted machine | Managed host |
|---|---|---|
| File control | Complete access to server files, scripts and backups. | Usually panel and SFTP access; permissions depend on the provider. |
| Setup effort | Install Java, extract the pack, accept the EULA, configure firewall/router and maintain the system. | Often a one-click pack install, followed by version and memory selection. |
| Recurring cost | No hosting subscription, but you supply hardware, electricity and internet service. | Monthly charge; price and included resources vary by region and plan. |
| Backups and rollback | You must schedule, store and test your own backups. | Some plans include snapshots or scheduled backups; verify retention and restore access. |
| RAM changes | Limited by the machine’s physical memory and other workloads. | Usually changed by moving plans or adjusting an allocation in the panel. |
| Release accuracy | You choose the archive directly and can preserve it for rollback. | You must confirm that the panel’s available file is the same 1.3.6 HOTFIX release. |
At access time, WinterNode advertised one-click Modded Together deployment, SFTP/file access, 12-hour backups and a listed $23.88-per-month 12 GB plan. Those are provider claims and a snapshot price, so confirm current pricing, location, renewal terms, backup retention and the exact pack file before ordering. BoxToPlay advertised one-click installation for Modded Together versions on Minecraft 1.21.1 NeoForge; verify that the panel offers the release your group selected rather than assuming every listed version is interchangeable.
Common errors and precise fixes
Attempted to load class net/minecraft/client/... for invalid dist DEDICATED_SERVER
The server is loading a client-only mod. Read the mod name in the error, stop the server, remove that named client-only file from the server’s mods directory, and restart. If the file came from a copied client folder, replace the directory with the published server-pack contents instead of deleting files at random.
UnsupportedClassVersionError
The Java runtime launching the server does not match the class version required by the pack. Select Java 21 for the indexed 1.21.1 setup, then confirm the panel or startup script is actually using that executable. Changing only the system’s default Java may not change the runtime selected by a hosting panel.
Missing or unsupported mandatory dependencies
The named dependency is absent, the loader build is wrong, or a file was replaced with one from another release. Restore the exact server-pack archive, confirm NeoForge 21.1.250, and install the dependency named in the log only when it belongs to the same pack release.
The client reports missing or mismatched mods
Reinstall the same Modded Together archive used by the server. Compare Minecraft 1.21.1, NeoForge 21.1.250 and Java 21 on both sides. Remove stray server mods and avoid copying a friend’s modified mods folder over the clean instance.
OutOfMemoryError
Raise the heap within the machine or plan’s available limit, then reduce optional heavy additions if the error persists. Check player count, view distance, active entities and new-chunk generation before concluding that the pack itself has a fixed memory requirement.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsUpdating safely and preserving a rollback
- Announce a maintenance window. Prevent players from changing the world while files are being replaced.
- Stop the server cleanly. A clean stop reduces the chance of incomplete region or configuration writes.
- Back up the world and configuration. Include the world directories,
config,defaultconfigs, scripts and any provider-specific files that control the instance. - Save the old pack archive. Keep the exact client and server files that produced the last working world.
- Update both sides together. Install the new release on the server and every client; do not allow a single player to remain on the previous file.
- Test before reopening access. Start the server, inspect the console for dependency or side errors, connect with a test client, and check a saved area before inviting everyone back.
- Roll back if necessary. Stop the server, restore the previous files and backup, and tell players to return to the matching client instance.
Pack changes can alter mod data, world generation or configuration. A rollback copy is therefore more valuable than simply keeping the newest archive.
Quick Recap
Pre-flight checklist
- Every player has the same Modded Together-1.3.6 HOTFIX instance.
- The server uses the matching Modded_Together_server_pack.zip.
- Minecraft is 1.21.1 on clients and server.
- NeoForge is 21.1.250 on clients and server.
- Java 21 is the runtime actually launching both sides.
- No full client
modsfolder was copied into the dedicated server. - Heap allocation fits the machine or hosting plan; 8–12 GB is treated as provider guidance, not a guaranteed minimum.
- The EULA is accepted and the console reaches completed startup.
- TCP port 25565 and the host firewall are configured only when outside players need access.
- A tested backup exists before version changes or optional mods are added.
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.
