Yet Another Zombie Survivors Wiki

Which wiki should you use?

The wiki.gg site is the strongest general reference found for Yet Another Zombie Survivors. Its pages cover Survivors, items, stats, modes, achievements, and the related Yet Another Zombie Defense game. That shared scope is useful, but it also means readers must check that a page is specifically about Survivors before applying its information.

A separate Fandom wiki exists and includes older details about permanent upgrades. It can fill gaps, but it appears to update more slowly than wiki.gg and should not outrank official 1.0 notes. Multiple similarly named “wiki” domains also publish highly repetitive build and tier-list copy, so several matching pages may still represent only one unverified source group.

The roster-count warning

The clearest example of version drift is the playable roster. An older wiki page says there are seven playable Survivors while its own list contains eight, but the official 1.0 announcement calls Ranger the ninth Survivor. The conflict is resolved in favor of the official release announcement: version 1.0 has nine Survivors.

That mismatch does not make every wiki page unusable. It does mean that exact counts, unlock levels, skill nodes, and balance-dependent recommendations need a date and version check. Pages created before August 20, 2026 may describe a valid Early Access state rather than the current game.

What official sources cover instead

Awesome Games Studio does not publish a conventional, complete developer-run wiki. Its official blog is the best source for release notes, major feature additions, and corrections, while Steam, Xbox, and PlayStation provide platform facts. Those store pages confirm the single-player format, supported hardware, features, languages, release dates, and the basic squad-and-synergy loop.

The full-release post is especially important because version 1.0 adds Ranger, Bio Lab, Boss Rush, the Survivors’ Camp, story and character missions, Friendship, Rank 5 trees, expanded synergies, new items, bosses, enemies, and achievements. A community page that omits these systems is incomplete for current play. Use the blog as the version baseline before reading deeper wiki entries.

How to verify a wiki claim

First identify whether the statement is a stable mechanic, a precise number, or a subjective recommendation. Stable concepts such as automatic aiming and three-person squads are confirmed by official store copy, while exact stat conversions often come only from community testing. Tier placements and “best” teams are opinions even when several guides repeat them.

Next check the page date, the game version, and whether independent sources actually agree. Mirror sites with nearly identical wording do not count as separate confirmation. If the official notes do not explain a current mechanic—such as the exact 1.0 behavior of Potato—the responsible label is 待确认 rather than a confident guess.

Useful reference destinations

Use wiki.gg when you need a structured community index, the official release blog when you need 1.0 changes, and the platform stores when you need availability or feature confirmation. Steam community guides can help with current player experiments, but their builds still reflect individual play styles and patch snapshots. The official r/YAZS community is useful for emerging issues that have not reached the wiki yet.

For achievements, the Steam store and official release notes establish the current total and the 1.0 additions, while achievement databases add completion estimates. For platform questions, prefer the matching platform holder’s store rather than a generic wiki entry. For Switch, use the confirmed “coming later” status and keep the exact date marked 待确认.

Bottom line

There is no single source that is both a complete wiki and fully current on every 1.0 detail. The best workflow is wiki.gg for navigation, official release notes for changes, and official stores for platform facts. That combination preserves the wiki’s depth without mistaking old community data for a developer guarantee.

This page follows that hierarchy throughout the site. Official statements are presented as verified, independent databases and guides are attributed, and unresolved version conflicts remain visibly pending. That is slower than copying a single page, but it prevents outdated roster counts and invented build claims from spreading.

How to use this information safely

Match every recommendation to the version and platform you are actually playing. A mechanic confirmed for version 1.0 is stronger evidence than an Early Access ranking, while a current platform store is stronger evidence than an undated availability page. When the topic involves balance, test the idea in the current client before spending permanent resources around it.

Separate a repeatable mechanic from a successful individual run. One video, Reddit post, or Steam thread can reveal a useful interaction, but it does not establish the best character, exact hidden value, or universal performance result. Reproduce the same condition and compare an independent source before turning the observation into a firm recommendation.

Treat time-sensitive details as snapshots. Prices, discounts, user-review percentages, community rankings, performance reports, and planned release windows can change after this research date. Platform features and developer announcements are linked below so the current state can be checked without relying on a copied number.

Editorial verification method

This guide gives official statements the highest weight for release dates, roster additions, platform features, and version changes. Community wikis and databases are used to organize mechanics or public records, while professional and player guides contribute attributed interpretations. Several near-identical fan domains are treated as one source group rather than artificial independent agreement.

Conflicts are resolved only when a stronger source directly answers the same question. The nine-Survivor roster is confirmed because the official 1.0 notes explicitly call Ranger the ninth Survivor, but Potato’s current behavior is not resolved because the official notes do not explain the item. An unresolved conflict remains marked 待确认 instead of being smoothed into confident prose.

No unsupported damage value, character, redemption code, release day, compatibility promise, or achievement total is added to fill space. Dates are written with their platform context, estimates are attributed to the database that calculated them, and player conclusions are labeled as community opinion. That evidence trail is what makes the answer useful even when the next patch changes the meta.