If leaving your base triggers a crash, preserve the logs and look for a NullPointerException involving IsoHutch.removeFromWorld and IsoAnimal.removeFromUpdateLists. For Stable 42.21, follow the acknowledged report and preserve the world. The 42.22 Pre-Release announcement now lists a fix for leaving a chunk while chickens are in a nest box; it does not establish that the fix is on Stable or explains every base crash.
Source review is not a game test or a guarantee for every patch, operating system or mod list. Record your exact game/server patch and relevant mods, then compare the author or official instructions linked below.
Choose Stable 42.21 or Pre-Release 42.22 before testing
The developer recommends most players stay on Stable while Pre-Release is tested. A minimum testing period is not a promised Stable promotion date. Do not move your only long-term world merely to try a reported fix.
An operator who chooses to test Pre-Release should back up first and keep the test save separate. Update the joining clients and server to the same intended branch/build; a version mismatch is a different connection problem.
| Installed branch / symptom | What the source establishes | Your next step |
|---|---|---|
| Stable 42.21; matching hutch/animal exception when leaving base | The older report and Support acknowledgement document this error branch. The Pre-Release fix is not proof of a Stable update. | Keep logs and backups; use the matching-error checks below. Verify both clients and server versions. |
| Pre-Release 42.22; leaving a chunk while chickens are in a nest box | The official announcement lists a fix for this specific multiplayer crash condition. | Record exact patch/branch and retest only in a separate backed-up copy. If it recurs, collect new logs rather than assuming the old diagnosis. |
| Animals die/disappear when an area unloads, without a process crash | The same announcement lists separate animal-death and full-hutch disappearance fixes. | Record survival/disappearance separately; it is not by itself evidence of a client/server crash. |
Source: The Indie Stone · Moving on Up: 42.22 Pre-Release · Official Pre-Release announcement · not Stable
Match the error before choosing this branch
Read the output around the first failure at the time you leave the base. Look for all three identifiers below together. A generic disconnect, startup failure, out-of-memory error or Workshop version message needs a different investigation. Record the full exception and surrounding lines rather than only the last termination message.
Error identifiers
java.lang.NullPointerException
IsoHutch.removeFromWorld
IsoAnimal.removeFromUpdateListsMatch these identifiers in your logs. These are diagnostic text, not commands.
Source: The Indie Stone · 42.21 multiplayer crash when leaving a base chunk · Player reports and Support Team acknowledgement
Separate a client exit from a server process crash
The thread contains both a client-return-to-menu account and terminated-process output. Use your own process status and timestamps to distinguish these paths. A server console without the same exception does not make the client log irrelevant.
| Observation | What to record / next check |
|---|---|
| One joiner returns to the menu; others remain connected | Collect that client’s output. Ask the operator whether the server process is still running. |
| Host player exits and the hosted session ends | Preserve both client and hosted-server output. Do not infer which failed first from the disconnected friends alone. |
| Dedicated process stops or restarts | Record its first exception, exit/restart time and provider status separately from the clients. The linked Host report does not prove the same cause on a dedicated server. |
Source: The Indie Stone · 42.21 multiplayer crash when leaving a base chunk · Player reports and Support Team acknowledgement
Record the setup and preserve the world
- Write down the complete game version and branch on each client and server. Record Host inside the game versus a dedicated program/provider, operating systems and whether the world was created before or after the update.
- Record enabled mods, required dependencies and any recent updates. Note the location, travel direction and whether the failure repeats when that area unloads. An installed mod is not proof that it caused the exception.
- After preserving the failure logs, stop the session normally where possible. Back up the complete world, active server profile and relevant configuration to a separate location. Keep the untouched backup out of the test workflow.
- Confirm that the backup is complete and that you know how to restore it before making changes. Do not delete chunks, reset the map, remove animals or strip mods from your only world to diagnose this problem.
Use an independent test instead of risking the only save
- Create a separate disposable profile/world on the same recorded build. Keep its data distinct from the original world and backup. Start with a supported vanilla configuration to obtain a comparison.
- Try the corresponding travel/unloading action and save the result. A new world that does not fail is only a comparison; it does not repair an older world or prove a specific mod responsible.
- If testing the existing world is necessary, use a separate copy and change one variable at a time. Keep a note of the full configuration and whether the exact exception returns.
- Test mods and dependencies in the disposable setup using their authors’ supported configuration. Avoid removing content from the original world simply to imitate a vanilla test. Stop if the test would require an uncertain save conversion or destructive edit.
What the chicken-hutch report does and does not establish
On October 4, a player reported that removing a chicken hutch let their group leave the base. That is a single reported workaround; it does not prove every hutch is defective or that removal will repair your save. On October 5, TIS_Ash of the Support Team acknowledged the issue and expected a fix in a later patch.
If you choose to investigate hutch involvement, confine the change to a separately backed-up test copy. Record the before/after error and preserve the original. The October 27 notes now announce a corresponding chicken/nest-box crash fix on 42.22 Pre-Release. They do not establish a repair on 42.21 Stable, a universal hutch cause or successful conversion of your existing world.
Source: The Indie Stone · 42.21 multiplayer crash when leaving a base chunk · Player reports and Support Team acknowledgement
Collect a useful support report
- Immediately preserve the logs from the failed session before repeated launches overwrite useful context. For Windows clients, the support thread asks for logs.zip in %UserProfile%\Zomboid. On other systems or with a custom data directory, locate the equivalent active Zomboid data location rather than assuming that Windows path applies.
- Collect the corresponding Host/server output and the affected client logs with matching timestamps. Include the full first exception, whether other players stayed connected and whether the server process actually terminated.
- Include exact patch/branch, Host or dedicated, OS, new versus existing world, mod/dependency list, reproduction route and the result of each independent test. Label any test you did not perform as untested.
- Before posting publicly, inspect the files for passwords, tokens and private addresses. Share through the support team’s requested channel and keep an original local copy.
Source: The Indie Stone · 42.21 multiplayer crash when leaving a base chunk · Player reports and Support Team acknowledgement
Prepare a report without sending it
The official guide directs crash reports to Support and asks users to search existing reports first. Its bug-report requirements include a new save with mods disabled; meet those requirements in a separate disposable setup, preserving your original world. Describe a modded or older-world crash honestly and distinguish it from any new vanilla reproduction.
Fill in the template below with your own observations. Mark comparisons you did not run as untested. Copying this text only prepares a local report; you decide whether and where to submit it.
Support report template
Title: [full patch] Crash when leaving base
Branch / client and server version:
Mode / Host or dedicated / OS:
Mods and dependencies:
Save created on / new or existing:
First exception and timestamp:
Client returned to menu or process stopped:
Other players still connected:
Reproduction steps:
Separate new vanilla test result (or untested):
Changes tested on a copy and results:
Client and server logs attached: Adapted reporting fields plus editorial crash diagnostics. Replace blanks before submitting; this page does not send a report.
Source: The Indie Stone · B42 Stable Bug Report Guide (2026) · Official QA reporting instructions
Decide whether to resume or wait
A successful comparison means the exact exception did not recur under the recorded test conditions. It does not establish a permanent fix. Before returning a changed copy to group play, check normal travel, clean shutdown, restart and world persistence, while retaining the untouched backup.
If the exact error continues, send the preserved evidence to support and avoid repeating destructive experiments. If the error changes, follow the new symptom. Use Workshop mismatch help for a content-version message and the dedicated-server checklist for setup or connection checks.
Choose the next branch
Sources & verification
Original checking steps are editorial recommendations. This site has not run a game test or inspected a local 42.21 installation. Source review and page update dates describe different work.
- The Indie Stone · Moving on Up: 42.22 Pre-ReleaseReviewed 4 November 2026. The October 27 announcement identifies Stable 42.21 and Pre-Release 42.22. It lists a multiplayer crash fix when leaving a chunk while chickens are in a nest box. This is source-reported availability on Pre-Release, not a tested fix for every base crash or evidence it is on Stable.
- The Indie Stone · 42.21 multiplayer crash when leaving a base chunkReviewed 12 October 2026. The original September 28 report includes the animal/hutch exception and terminated-process output. An October 4 player reports removing a chicken hutch; TIS_Ash (Support Team) acknowledges the issue on October 5 and anticipates a future patch. This thread does not establish a released fix or a universal cause.
- The Indie Stone · B42 Stable Bug Report Guide (2026)Reviewed 12 October 2026. Requests branch, version, mode, Host/dedicated, mod state, new-save reproduction and steps; crash reports belong in Support with logs. Read the current instructions before submitting.