Homestead Modpack Server: Requirements, Files and Crash Fixes

Published on

Set up a Homestead 2.0.1 server on Fabric 1.20.1 and Java 17 with the right server pack, then fix the crashes and chunk stalls from the pack's own tracker.

A Minecraft spruce taiga forest on a hillside beside a lake

Your Homestead world runs fine in singleplayer, but the server will not start, shuts down after a few minutes, or your friends walk into chunks that never load. Most of this comes down to a handful of causes that the pack's own GitHub tracker documents. This guide covers what a Homestead server needs, which server files to use since the 2.0.1 hotfix, and why a Homestead modpack keeps crashing, with fixes from that tracker. Everything was checked on 3 November 2026.

Quick answer: Homestead 2.0.1 runs on Minecraft 1.20.1 with Fabric Loader 0.19.5 and needs Java 17 or newer. Use the 2.0.1 server pack from the CozyStudios website: unlike the 2.0 pack on CurseForge, it bundles every mod the server needs. Its user_jvm_args.txt sets an 8 GB heap, and the team asks for 8 to 12 GB of RAM, more for 3 to 5 or more players. If your Homestead modpack keeps crashing, check in this order: the Java version, missing mods (the 2.0 CurseForge pack leaves out eight), client-only mods on the server, memory and the watchdog limit. Chunks that stop generating while TPS stays at 20 are a known open issue with C2ME and ocean structures.

What a Homestead Server Needs

ItemHomestead 2.0.1
Minecraft and loader1.20.1, Fabric Loader 0.19.5
Java17 or newer; the README recommends Eclipse Temurin 21 for servers
Heap in the files-Xms6G -Xmx8G in user_jvm_args.txt
RAM8 to 12 GB per the team's wiki, more for 3 to 5 or more players
Server filesHomestead-2.0.1-Server.zip, about 670 MB, from cozystudios.org
Ports25565 TCP for the game, 24454 UDP for Simple Voice Chat

Mojang's version file for 1.20.1 asks for Java 17, and the pack's start script refuses anything older with "Minecraft 1.20.1 requires Java 17 or higher". On memory, the README is milder than the wiki: it asks for "at least 6 GB of RAM available for the server (8 GB+ recommended)", while the wiki's Server Pack page says "at least 8-12 GB" and more for groups of 3 to 5 or more. Java needs memory beyond the heap, so a server with exactly 8 GB cannot run the shipped -Xmx8G safely. On our Homestead server hosting page we start at 8 GB with a heap of about 6.5 GB and suggest 12 GB, which fits the pack's own 8 GB heap with room for Java itself.

Which Homestead Server Pack to Download

Homestead 2.0 came out on 22 October 2026 and the 2.0.1 hotfix on 27 October. Where the server files live changed between the two:

  • 2.0 on CurseForge (Additional Files, Homestead-2.0-Server.zip) leaves out eight mods: Balm, CraftTweaker, Library Ferret, Sophisticated Backpacks, Sophisticated Core, Sophisticated Storage, TrashSlot and Wireless Redstone. Its start script downloads them on the first run. The developer confirmed in issue #469 that this is intended, because of licensing.
  • 2.0.1 has no server pack on CurseForge. Its changelog says the pack is listed on the CozyStudios website instead, "with all the mods needed. No external downloads, or .bat/.sh scripts needed." We read the zip's file list: all eight mods are in its mods folder, 305 jars in total.
  • Modrinth only has the .mrpack for players. In the 2.0.1 .mrpack, 78 client-only mods are marked as unsupported on servers.

Every player needs the same pack version as the server, so move the whole group to 2.0.1 together.

The 2.0.1 zip holds the Fabric launcher (fabric-server-mc.1.20.1-loader.0.19.5-launcher.1.1.2.jar), the start scripts, user_jvm_args.txt, an eula.txt set to false, and the config, defaultconfigs, kubejs, mods, patchouli_books and scripts folders.

Homestead Modpack Server Setup

On a Linux VPS or your own PC (install unzip first if your system lacks it):

java -version
unzip Homestead-2.0.1-Server.zip -d homestead
cd homestead
sed -i 's/eula=false/eula=true/' eula.txt
chmod +x startserver.sh
./startserver.sh

The script starts Java with @user_jvm_args.txt, writes a server.properties stub if none exists, and starts the server again 10 seconds after it stops. If systemd or a panel already restarts it for you, run export HOMESTEAD_RESTART=false first.

On a hosted panel, the README's steps are: upload the whole folder, pick Java 17 or newer, point the panel's custom jar setting at the Fabric launcher jar, accept the EULA and start. Two things change when the panel starts the jar instead of the script:

  1. user_jvm_args.txt is ignored. Java only reads it when started with @user_jvm_args.txt. Set the memory in the panel instead.
  2. The pack's server.properties values are missing. The script writes allow-flight=true, max-tick-time=180000, simulation-distance=6 and view-distance=10 only when it creates the file. Add them yourself.

allow-flight=true matters in a pack like this: with the default of false, players who stay in the air for 5 seconds get kicked. max-tick-time is the watchdog limit. Minecraft's default of 60000 milliseconds stops the server once a single tick takes a full minute, and the pack raises that to 3 minutes.

For voice chat, open UDP 24454 or give Simple Voice Chat a port your host allocates, set as port= in config/voicechat/voicechat-server.properties. Its config strongly advises against reusing the Minecraft port (port=-1), because UDP on that port is also used for server queries, and it warns that this may crash the server. More in our voice chat port guide.

Why Your Homestead Modpack Server Keeps Crashing

It stops before loading: wrong Java

The script prints "Minecraft 1.20.1 requires Java 17 or higher. Found Java 8" (or 11). A panel that skips the script fails with a Java error instead. Pick Java 17 or 21 in the startup settings.

Chests and backpacks are gone: missing mods

In issue #470, a server owner updated to 2.0 with the folder-replacing steps and found every Sophisticated Storage chest and backpack gone and its recipes missing. That matches the three Sophisticated mods the 2.0 CurseForge pack leaves out. Stop the server, restore your backup and use the 2.0.1 server pack, which bundles all eight.

It crashes at startup on a client-only mod

Issue #408 shows a server that would not start: "Could not execute entrypoint stage 'main' due to errors, provided by 'colorwheel_patcher'". The developer's answer was "Remove Colorwheel and Colorwheel patcher." Issue #438 describes one way such mods end up on a server: an older .mrpack export marked every mod as required on servers, so panel installers downloaded client-only mods too. In 2.0.1, both Colorwheel mods are marked unsupported on servers in the .mrpack and are absent from the server pack. If a panel installer built your server, compare its mods folder with the server pack's.

It reboots with no crash report: out of memory

In issue #446, a server restarted about once a day with "absolutely 0 logs", and the owner then found it was running out of memory at 10 GB. When the system or a container limit kills Java, it never gets to write a crash report. Keep -Xmx at least 1 to 1.5 GB below the server's RAM, look for exit code 137 in the panel and see our exit code 137 guide.

"A single server tick took 60.00 seconds"

That message comes from the watchdog. If your server.properties still says max-tick-time=60000, set the pack's 180000 and find out with spark what made the tick that long. A Nether watchdog crash in the 1.3 series (issue #402) went away with the next pack version, so update first. Our watchdog guide covers the rest.

Chunks stop loading but TPS stays at 20

Issue #474, still open on 3 November 2026: on a 2.0 server, chunks near players stop generating until a restart, and Streams Reflowing writes streamsreflowing-stall-*.txt dumps into the server folder. The reporter traced it to a C2ME deadlock when drowned from Repurposed Structures ocean structures spawn during world generation, and a Chunky pregeneration stalled at the same spot every time. The 2.0.1 server pack still ships C2ME and Repurposed Structures.

Their workaround is a data pack that turns off three Repurposed Structures ocean structures (the ocean village, ocean pyramid and ocean ancient city). With it, Chunky finished a radius of 1500. The pack already loads data packs through Open Loader, so from the server folder:

cd config/openloader/data
base=homestead-ocean-fix/data/repurposed_structures/tags/worldgen/biome/has_structure
mkdir -p $base/villages $base/pyramids $base/ancient_cities
echo '{"pack":{"pack_format":15,"description":"Homestead ocean structure workaround"}}' > homestead-ocean-fix/pack.mcmeta
for s in villages pyramids ancient_cities; do echo '{"replace":true,"values":[]}' > $base/$s/ocean.json; done

Restart the server. Those three structures no longer generate in new chunks. This is a player's workaround, not a fix from the team, so delete the folder once a pack update solves the issue. The pack's Chunky config does not resume after a restart, so type chunky continue to pick up a cut-off pregeneration (Chunky guide).

Long hitches when players open loot chests

Issue #472, also open: on a 12 GB 2.0 server, every Lootr chest or barrel caused a lag spike of 10 seconds or more, starting 15 to 45 minutes after startup. The reporter replaced Lootr with MyLoot and edited the Whispers of the Wilds quest chapter that refers to it. Confirm with spark first and test any mod swap on a copy of the world.

Fixed in 2.0.1

The hotfix lists "Fixed a crash on servers with Create's Tree Fertilizer" and a fix for Copycats+ removing textures on servers. If you see either on 2.0, update.

Updating to 2.0.1 Without Losing the World

The CozyStudios update guide: back up the world folder, delete config, mods, kubejs, scripts and patchouli_books, copy the same folders in from the new server pack, add back any mods you installed yourself, and start. Leave the world folder alone.

From 1.3.7, take more care: 2.0 removed Storage Drawers and Iron Chests: Restocked, and items in them "will be gone forever" unless you follow the migration steps in the 2.0 announcement first. Copper Age Backport blocks and items also disappear. More in our modpack update guide.

Finding the Cause Yourself

  1. Read logs/latest.log from the bottom up, plus the newest file in crash-reports/ if one was written. Our crash log guide shows what to look for.
  2. spark ships in the server pack. In the console, spark tps shows tick times, spark health --memory prints memory use, and spark profiler start --timeout 120 records two minutes and then gives you a link to the results.
  3. Still stuck? The developer asks for logs as an mclo.gs link. Post them in the GitHub tracker or the #issues channel on the CozyStudios Discord.

When the Game Crashes, Not the Server

If Homestead crashes on your own PC rather than on the server:

  • Video Settings closes the game on 2.0. The developer's fix was removing Sodium Options Mod Compat, and 2.0.1 removed it. Its changelog ties the crash to players who added EMF and ETF.
  • The game closes at launch on Linux. 2.0.1 adds GLFW X11 Fix for that crash.
  • Memory. The pack page says "Give it 6-8GB of memory. Stay within 6-10GB; more than that can hurt instead of help."
  • Low frame rate. Shaders come preloaded; turn them off in Video Settings.

FAQ

Why does my Homestead modpack keep crashing? If the server stops, read its log and check Java (17 or newer), mods missing from the 2.0 server pack, client-only mods, memory and the watchdog. If your game closes, update to 2.0.1, which fixes the 2.0 Video Settings crash and a Linux launch crash.

How much RAM does a Homestead server need? The team asks for at least 8 to 12 GB, more for 3 to 5 or more players. With the pack's 8 GB heap plus Java's own memory, 12 GB fits the pack as shipped.

Where do I download the Homestead 2.0.1 server pack? From the Server Pack page on cozystudios.org. CurseForge only has the 2.0 server pack, which lacks eight mods, and Modrinth has no server pack.

Does Homestead need Java 17 or Java 21? Either works. Minecraft 1.20.1 needs Java 17 or newer, and the README recommends Eclipse Temurin 21 for servers.

Can I update my Homestead 2.0 server to 2.0.1 without losing the world? Yes. Back up the world, swap in the five folders from the 2.0.1 server pack, keep the world folder and have every player update too.

Sources

All opened on 3 November 2026: