Yet Another Zombie Survivors Public Beta Guide

Public Beta is not the Stable build

Awesome Games Studio opened a permanent Public Beta branch after the 1.0 launch so interested players can help test upcoming fixes and improvements. It is an experimental Steam branch, not a replacement for the public Stable build. Keep the two labels separate when reading a guide: a Stable recommendation should name the Stable version it covers, while a Beta observation needs to say that it came from the public-beta branch.

Branch name

public-beta

Purpose

Test upcoming fixes and improvements with interested players

Stable build shown by this wiki

1.0.0c2

Important warning

Beta builds can be unstable and switching builds can cause issues

The official announcement does not turn every Beta download into a documented patch. It directs discussion to the Public Beta Test Steam forum, the dedicated Discord channel, and the in-game F8 feedback form. If a guide cites a Beta behavior, check those current channels and the game build before treating it as a Stable rule.

How to join the branch

1. Open Steam and find Yet Another Zombie Survivors in your Library.
2. Right-click the game and choose Properties.
3. Open Game Versions & Betas.
4. Select public-beta.

Steam downloads the branch only when it differs from the currently installed version. Seeing the Beta branch active in the Library is a useful first check, but it does not confirm that every outside build guide uses the same version. Record the branch and build shown in-game when testing a route.

How to return to Stable

Return to the same Steam menu and select Default Public Version. Steam will switch the installed branch when there is a difference to download. Do not describe this as an in-game balance setting: it is a Steam branch choice, so it changes which game build and fixes you are running.

The official guidance warns that Beta versions may be unstable and that moving between old and new builds can create issues. If a run, save, or performance problem begins after a switch, report the exact branch and build rather than assuming a normal Stable guide has become wrong.

Read guides with the correct version label

Use Stable pages for the normal public version and treat their displayed version as the scope of the advice. Beta pages should be clearly marked experimental, with their test date and branch. A Beta observation can be useful early evidence, but it does not replace an official Stable patch note or a repeatable Stable test.

For feedback or troubleshooting, use the channels named in the official announcement. The wiki can explain branch context, but it cannot verify an undocumented Beta change or recover a save. Keeping the Stable and Beta tracks separate lets useful testing exist without quietly turning temporary behavior into a permanent recommendation.