Collect the right Build 42 log
Use console.txt for a single-player game or client, coop-console.txt for a player-hosted server, and server-console.txt for a dedicated server. logs.zip preserves broader context from recent launches and is useful when official support asks for it.
- Back up the affected save, then reproduce the error once.
- Open the correct console file and find the first relevant
STACK TRACE. - Record the first named mod ID, file, class, setting, port, or memory message.
- Verify game files if the trace points to a missing base-game resource.
- If a mod is named, test without that mod and its dependencies on a new save. With a large list, remove half at a time.
- Reproduce the same action after each controlled change and compare the new log.
Choose a branch from the signature
- Workshop or mod not found: confirm the Workshop download, required items, Mod ID, and Build 42 compatibility.
- Lua or Java trace names a mod: update it, check its dependencies and incompatibilities, then isolate it on a new save.
- Missing base-game file: use Steam’s file verification before reinstalling anything.
- Out-of-memory or heap message: reduce the mod set and address memory allocation; file deletion will not solve that signature.
- Server setting named in the trace: change only that setting. A reported
DisguisedUsernamesorHideDisguisedUsernamesworkaround applies only to the matching role-related null-pointer trace.
Sources
PZwiki Tech Support — Current official-wiki reference for logs, verification, and mod isolation.
The Indie Stone forum: Build 42 console.txt case — Official Build 42 support case.
Build 42.20 hosting crash discussion — Community-confirmed example; use only when the signature matches.