Yet Another Zombie Survivors synergies work through unlocked permanent nodes and in-run requirements, not simply by putting three named Survivors into one squad. Version 1.0 expands every Survivor to four cross-character Synergies and adds new Synergy and passive nodes, making the current skill tree and card text essential evidence. Build around a shared damage tag, a control-to-damage sequence, or a repeatable critical and ability-frequency trigger, then verify every required card in the current client.
What version 1.0 officially confirms
Version 1.0 increases each Survivor's cross-character Synergies to four. Three of those Synergies relate to abilities, while a fourth works independently of that ability framework. The same update gives every character two additional Synergy nodes, two passive-enhancement nodes, and one passive node that affects the whole team while that character is present.
Those additions make permanent progression part of every accurate Synergy answer. A roster screenshot cannot show whether the necessary node has been unlocked, and an in-run squad cannot activate a condition that is absent from its progression tree. Check the current tree before planning a combination around a name seen in an older guide.
Why three characters do not guarantee a Synergy
Selecting the right Survivors is only one layer of the requirement. The corresponding permanent node generally needs to be unlocked, and the run may also require a named ability or another condition printed on the card. If any layer is missing, the expected interaction may never appear even though the final squad looks correct.
This is why a combination list without prerequisites is incomplete. Record the relevant character, unlocked node, required ability, card condition, and final effect instead of writing only three roster names. The same record also reveals whether a failed test came from randomness, missing progression, or a mistaken combination.
Framework one: concentrate shared damage tags
The collected research identifies Kinetic, Slash, Ice, Toxic, Fire, and Electric as examples of damage tags around which a squad can concentrate. In a longer Infinite or Endurance run, reinforcing the same tag across several weapons and abilities is usually a clearer route to connected benefits than collecting unrelated high-quality choices. The principle is concentration, not a claim that one named tag is always strongest.
Tank and Ghost form the recurring community example for a Slash direction through Sawblade and Thousand Cuts. Tank, SWAT, and Medic are presented as a Kinetic-and-sustain framework, while Huntress, Medic, and Engineer are a candidate Ice framework. Each trio still needs its current nodes and cards checked because the official announcement does not provide the full public table.
Framework two: connect control to damage
Control can create the time and space required for damage to remain effective. Freezing, slowing, decoys, and shields are the types of tools named in the collected framework, and they can be followed by a focused high-damage route. The important question is whether control addresses the threat that ends the run rather than whether it looks strong in isolation.
The Huntress, Medic, and Engineer candidate illustrates this logic through Ice-oriented control and team support. Engineer's barrier role can also matter when projectiles are the pressure the team cannot otherwise manage. Do not convert that role description into an exact effect or value unless the current in-game card supplies it.
Framework three: critical and ability-frequency triggers
Some builds connect frequent attacks or abilities with critical-focused support and triggered effects. This framework is most useful when the weapons and chosen nodes actually produce enough eligible events for the interaction to matter. A generic recommendation to stack speed or critical chance is not sufficient because different weapons may read attack speed and cooldown differently.
Use the weapon-upgrade guide to separate attack animation, burst behavior, and the interval between attacks before assigning an attribute to this framework. Then record which event activates the relevant Synergy card. This protects the build from a common error in which an attractive stat does not affect the weapon or trigger being tested.
Named combinations that still require verification
An unofficial 1.0 summary lists SWAT plus Tank plus Pyro, Huntress plus Medic plus Pyro, and Engineer plus Mechanic plus Ranger as squads capable of connecting several interactions. The collected official material does not publish the full names, node levels, prerequisites, or effects for those entries. 待确认：treat all three as an in-game checklist, not as a verified best-team recommendation.
The useful next step is to inspect every Synergy card offered during a current run. Capture the owning Survivor, prerequisite progression node, required ability, final effect, and client version in the same record. Publish a precise combination only after those fields agree with the current card rather than with a search-result summary.
How balance changes affect old combinations
A concept can remain valid while its strength changes. Version 1.0 reduces Tank's Sawblade Drone and Ghost's Kunai Dance final damage, so an older Slash combination cannot retain its previous numerical conclusion without retesting. The shared-tag structure remains a reasonable candidate, but the current result must come from the current version.
The same caution applies when an update changes range, firing arc, projectile behavior, or critical calculation. A combination that depended on coverage or event frequency may behave differently even when no Synergy node was renamed. Keep the version beside every result so a future balance change does not silently turn historical evidence into a current claim.
A reliable in-run selection process
Before the run, choose one Synergy framework and confirm that its permanent nodes are unlocked. During the run, develop one main weapon, recruit teammates through SOS, and read offered cards for the exact prerequisite instead of taking every option with a familiar tag. After the core is active, reinforce the same damage type or add control and recovery that preserve the build's operation.
If the required card does not appear, do not label the characters incompatible from one attempt. Record what was unlocked, which abilities appeared, and where the run ended, then repeat under the same conditions. This separates a missing requirement from ordinary run-to-run variation without inventing a probability or guaranteed acquisition order.
How to compare two Synergy builds
Hold the version, arena, mode, difficulty, leader, permanent progression, and measurement window steady. Record survival time, crowd pressure, elite or boss performance, defensive failures, and the actual Synergy cards obtained. A final damage number without those details cannot show whether one build had better card access, safer control, or simply a different upgrade sequence.
Use the best-team guide to select mode-specific candidates and the tier list to understand the roles being compared. Promote a combination only when repeated current-version runs reproduce its advantage and the card requirements are documented. Until then, label the result as community experience or 待确认： rather than turning a promising test into a guaranteed recipe.