Yet Another Zombie Survivors Achievement Tracker

What the tracker does

The tracker above is an account-free, local-first way to organize the Yet Another Zombie Survivors Steam achievement list. It includes the 229 achievement names and visible conditions from Steam’s public record; the official Version 1.0 release added 88 achievements, 64 of them in a new Story category. Search by an achievement name or phrase from its condition, filter by completion state, and tick only the entries you have personally confirmed. It never claims access to a Steam account or imports platform progress.

Its scope is intentionally narrow: identify an achievement, retain the public Steam condition, and mark a personal status in this browser. No login, platform profile, server-side player record, sync, or sharing feature is involved. This protects privacy and keeps the information under the player’s control. Steam’s own unlock notification remains the final proof that a run counted.

Use the Steam list as the source of truth

Start from the official Steam achievement list for the name and visible description. The supplied material includes older community guides, but even an updated guide can lag behind a patch or newly added Story entry. Mark a record as completed only after Steam or the current game confirms it. Use “needs verification” for an inferred route rather than turning it into a completed fact.

Version 1.0’s 88 new achievements make version notes particularly important. A route written before the full release may be incomplete even when its older achievement name remains valid. Keep the platform entry, your game version, and any relevant patch note together. That makes later corrections easy to audit.

Keep Torments in a separate list

The official release says the 28 Torments are optional and are not connected to the achievement system. They can be viewed through the Hall of Torments tab in the Achievements interface, but they are not part of 100% achievement completion. A tracker should therefore show them as a separate optional challenge list rather than blending them into Steam completion. Interface proximity is not the same as shared progress.

This distinction is useful when planning a session. Select Steam achievements when your goal is platform completion, and select a Torment only when you deliberately want a high-pressure challenge. The tracker should make that decision visible without evaluating whether a player’s build is strong enough. Difficulty advice needs its own current, versioned evidence.

A safe tracking workflow

Find the exact achievement in the tracker or Steam, then read its current description before starting a run. Identify any stated prerequisite such as an arena, Survivor, or mission, and tick it only after Steam or the game confirms the unlock. If a condition comes from a community post, treat it as an unverified lead instead of a completed fact. This keeps the tracker useful while the database is still expanding.

For item-linked achievements, keep rewards separate from effects. The official 1.0 notes say Curly Little Potato’s achievement reward changed to Easter Egg, but that does not prove every older item reference is current. Store the version of a reward change next to the note. The local record becomes more reliable than a memory of a past run.

Local storage boundary

The tracker works in the current browser only. Checked entries are saved in local browser storage on that device; opening another browser or clearing its site data starts a separate list. Clearing local progress in the tool removes only this site’s saved checkmarks. It cannot unlock, edit, read, or sync Steam achievement progress.

Use the page as a checklist for evidence, not as a substitute for Steam. The reliable facts are the public 229-achievement snapshot, Version 1.0’s 88 additions and 64 Story entries, and the separation of 28 Torments. Everything else should be tied to the live Steam text or recorded in-game proof. That is the right foundation for a privacy-friendly completion log.