Project Zomboid: 42.14.1 Unstable

Games News

The Indie Stone announced the release of 42.14.1 Unstable for Project Zomboid today via their Discord, website, and Steam page. You can shamble your way over to their Steam page for a look at the official patch message, here.

It has been awhile since our group has paid a good visit to the zombie apocalypse that is Project Zomboid. Right now though, we are certainly still content with our adventures in Return to Moria.

I suspect we will still have to pay it a visit at some point in the future. Much like our 7 Days to Die game play, we can generally only stay away for so long before the feral survival need comes to bare.

Scavenge well and stay safe, Survivors! -Hobbit

42.14.1 BETA HOTFIX Released

Note:
Players who want to remain on 42.13.2 can select the “outdatedunstable” Steam Beta to continue their game.

We will be removing the “42.13.1” Beta soon. Players who wish to remain on that version of the game are recommended to make manual backups.

As always it is recommended that you create a new save with no mods after updates. Updates fix bugs and introduce new changes that may not be compatible with any older saves, especially ones older than the last patch.

How do I subscribe to the Unstable beta branch?

Right-click PZ in your Steam library.
Select “Properties”.
Under “Game Version & Betas” select “Unstable”.

SP FIXES
– Fixed player getting stuck trying to leave cars
– Fixed vehicles attracting zombies from far away
– Fixed errors when pressing Avatar rotate buttons
– Fixed being able to select “Deaf” and “Hard of Hearing” together.
– Fixed not being able to drink tainted water from bottles, the option was missing from context menu

MP FIXES
– Fixed error with packet of type: SyncItemFields. Exception occurred when remote player equiped weapon in hotbar.
– Fixed NullPointerException error, occurred only when the Weapon Multi hit sandbox option is enabled.
– Fixed muscle strain from combat not synced in multiplayer

Leave a Reply

Your email address will not be published. Required fields are marked *