Project Zomboid 42.22: Which Locked Doors Can a Crowbar Force?

Confirm the branch before trying the new interaction

The developer labels the crowbar changes as Build 42.22 on the Pre-Release branch and tells ordinary players to remain on Stable 42.21 while the update is vetted. Do not apply a pre-release mechanic to a Stable save just because a guide or video mentions Build 42.

1. Read the build/branch shown by your installed client before approaching the door.
2. If the client is on Stable 42.21, use its current in-game interaction options; this article does not promise the new force-open feature is present there.
3. If testing 42.22, use a disposable or backed-up world as the developer advises for Pre-Release.

References: The Indie Stone: Moving on Up — 42.22 Pre-Release · The Indie Stone: 42.21 Stable Released

Use the door type as the first decision

The official announcement lists locked windows, doors, garage doors and gates as force-open targets, but expressly excludes security doors and jail-cell doors. It does not publish a universal success chance or guarantee every map object with a lock prompt is eligible.

References: The Indie Stone: Moving on Up — 42.22 Pre-Release

Budget character strength and tool risk

The publisher says Burglar characters are quieter with a crowbar, Strength helps, and weaker characters struggle more. It also warns that repeated failure raises the chance of crowbar damage. Because no attempt counts or success percentages are given, do not treat a failed first attempt as evidence that a door is impossible—or a repeated attempt as risk-free.

1. Check the character and role context before choosing a high-stakes door; the notes describe tendencies, not guaranteed success values.
2. Use the right-click interaction once and read the live result rather than holding a repeated action blindly.
3. If the attempt fails, reassess the door type and your escape route before trying again; repeated failures carry additional tool-damage risk.
4. Keep another exit and a weapon plan. The article does not claim the noise is safe around nearby zombies or that the crowbar cannot break.

References: The Indie Stone: Moving on Up — 42.22 Pre-Release

Report a reproducible pre-release result

For a bug report, include the displayed build, branch, object type, character occupation/Strength context, exact interaction result and whether the crowbar condition changed. The Indie Stone directs bug reports to its official forums and says reports elsewhere may be missed. A reader-submitted report is not verified until independently reproduced; GamerWin does not present forum posts as its own tests.

References: The Indie Stone: Moving on Up — 42.22 Pre-Release · The Indie Stone Forums: Project Zomboid

Before you play

• I verified this client is on Pre-Release 42.22, not Stable 42.21.
• The object is not a security door or jail-cell door.
• I checked the character context and accepted that repeated failures can damage the crowbar.
• I have a safe route and will record the exact build and result if reporting a bug.

Frequently asked questions

Sources & revision notes

Editorial revision: November 5, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

1. The Indie Stone: Moving on Up — 42.22 Pre-Release (Official)

   Publisher instructions checked November 5, 2026. The page identifies Stable 42.21 and Pre-Release 42.22, recommends Stable for average players, explains the Steam branch path, and warns that a long-term save should be backed up before testing Pre-Release. It does not promise save compatibility with the final release.

2. The Indie Stone: 42.21 Stable Released (Official)

   Publisher release context checked November 5, 2026. It describes the path from Unstable to Stable and the 42.21 changes; use the live game title screen to confirm the build installed on a particular client.

3. The Indie Stone Forums: Project Zomboid (Official)

   Publisher-hosted community forum checked November 5, 2026. It separates general discussions, support, bug reports, updates and multiplayer. Posts are user submissions, not GamerWin testing or endorsements; follow the relevant forum rules and remove private data.