Yet Another Zombie Survivors Torments Guide

Torments at a glance

Torments arrived with Version 1.0 as optional, extra-difficult challenges. The official release states that they are not part of the achievement system and offer bragging rights rather than progression rewards. It also places them in the Hall of Torments tab within the Achievements interface. That separation is the most important planning fact: Torments are not required to complete the game’s normal achievement list.

Added in

Version 1.0

Number added

28 Torments

Where to find them

Hall of Torments tab in the Achievements interface

Achievement requirement

Not required for 100% achievement completion

This page does not assign a tier or a hidden reward to any Torment. The official announcement only confirms their optional challenge role, location, and separation from achievements. Check the current in-game text for an individual objective, condition, or version change before treating it as a repeatable route. A difficult optional challenge deserves a more precise record than a broad community label.

Keep completion goals separate

Players commonly approach the Achievements interface with one of two goals: finish Steam achievements or take on optional high-difficulty challenges. Torments belong to the second goal. The release notes explicitly say they are not connected to the achievement system, so a player working only on achievement completion should not assume a Torment is blocking progress. This simple distinction prevents an unnecessary detour into a harder activity.

Use the Achievement Guide and Tracker for Steam-list planning. Use the Hall of Torments when you deliberately want a challenge with no stated progression payoff beyond bragging rights. If a UI label changes after a patch, preserve the version and exact wording rather than carrying an older category name forward. The category boundary is stable; individual challenge details still need current verification.

Read each challenge before choosing a squad

The official release describes Torments as very tough but does not publish individual rules in the launch announcement. A build cannot honestly be recommended from the category name alone. Before entering one, read the current objective, arena, and mode information in the game. Then select a squad test that addresses the stated condition instead of importing a generic endgame composition.

Keep the test narrow. If the question is whether a squad has enough room to move, use a consistent arena and difficulty. If it is whether a named condition is met, record the exact condition, version, and what happened. Avoid calling a team successful simply because it survived a different challenge. A reproducible note is more valuable than a context-free result.

Prepare a clean attempt

An optional challenge is the wrong place to discover whether an unlock or interface setting is missing. Confirm the selected mode and map before starting, then make sure the purpose of the run is clear. Boss Rush, for example, is a separate Version 1.0 mode with its own Hardcore-by-map prerequisite and ten-minute Final Boss deadline. Add it to a Torment plan only when the current challenge calls for that context.

The same applies to mission and progression systems. Mission completion grants Friendship, while Torments are explicitly not achievement requirements; neither statement creates an undocumented Torment reward. Keep the record honest by separating entry conditions, run choices, and outcome. This makes it possible to compare two attempts without silently changing the goal halfway through.

Record a result that can be reviewed

For every serious Torment attempt, capture the current game version, title of the challenge, arena, difficulty, squad, and the reason the run ended or succeeded. Add a screenshot of the current objective when you are ready to turn the note into a public guide. Do not invent damage thresholds, spawn patterns, or unlock rules from a one-off result. Those fields need the live interface or a repeatable test.

This process also makes patch maintenance easier. If a later update changes a mode, ability, or map condition, a versioned record shows exactly which earlier attempt it may affect. The wiki can then update a single Torment dossier rather than spreading stale advice across general achievement and build pages. Clear provenance is part of the guide’s practical value.

Torment checklist

1. Open the Hall of Torments through the Achievements interface.
2. Confirm that the goal is an optional challenge, not a Steam-achievement requirement.
3. Read the current objective and map or mode context before selecting a squad.
4. Keep the first attempt focused on one question and log its version and outcome.
5. Publish a build recommendation only after the conditions and result can be reproduced.

The verified answer is deliberately short: there are 28 optional Torments, they live in the Hall of Torments, and they are not needed for achievement completion. The rest belongs to current, per-challenge evidence. This guide gives players a clean way to reach that evidence without confusing optional difficulty with mandatory progression.