Wuthering Waves Team Building Basics: Roles, Intro and Outro Pairing, and Pull Decisions

A team becomes easier to build when you can explain what each Resonator contributes and who should enter after them. Start with a damage plan, identify the assistance it needs, and assign the remaining places to those jobs. Then check whether your actual swaps deliver that assistance when it matters.

This version 3.6 guide uses the documented combat systems and roster to help you make those decisions. It covers role definitions, Intro Skill and Outro Skill pairing, element choices, Rover forms, launch-era options, and evaluating a new pull. Named examples stay within the available evidence: a listed element or weapon is useful information, but it does not establish a character's complete kit or a proven team pairing.

Identify the problem your team needs to solve

Before replacing a Resonator, describe the failure you are seeing. A team that cannot stay alive needs a different investigation from one that survives comfortably but spends its useful attack window preparing resources. Choosing another damage dealer before making that distinction can leave the original problem untouched.

Use a familiar encounter to observe your current team. Watch who takes damage, who remains active after their useful actions are finished, and whether the next Resonator can act immediately after entering. Keep equipment stable during this initial check so you can connect the result to your team decisions.

What you observe	First question to investigate	Practical response
Attempts end because a Resonator falls	Is survival support available, and are you using defensive actions?	Review sustain and practice dodges or parries before judging damage potential
A planned swap produces no Intro Skill	Did the outgoing Resonator have full Concerto Energy?	Watch the correct gauge during the preceding turn
The main attacker enters and then waits	Was their intended action ready before the handoff?	Reorder preparation so the incoming turn has a purpose
Several members need lengthy preparation	Are their turns competing for the same opportunity?	Test a simpler division of damage and assistance
A new member appears ineffective	Are their levels, skills, and equipment comparable?	Separate investment problems from composition problems

These are diagnostic prompts, not proof that a particular character is weak. Keep your description concrete: “the intended recipient entered before their Resonance Liberation was ready” gives you something to fix. “The team feels bad” does not identify a cause.

Assign main DPS, sub-DPS, support, and healer jobs

These role labels describe the work you want a Resonator to do. For a three-Resonator team, a useful starting exercise is to choose a main damage plan, add a complementary contributor, and cover survival where your attempts require it. The four labels are planning categories; they are not instructions to fit four separate members into the party.

Main DPS means your primary damage dealer. Decide which actions you are trying to enable during that Resonator's active turn. The combat system includes Basic Attacks, Heavy Attacks, Resonance Skill, Resonance Liberation, and the character-specific Forte Circuit. The relevant combination depends on the kit. You cannot choose a suitable supporting effect until you know what the recipient actually intends to use.

Sub-DPS means a secondary damage contributor. Give this member a defined assignment: perform their useful damage sequence, prepare the handoff, and leave when the planned contribution is complete. Do not assume that every sub-DPS deals damage from off field; that requires a specific documented skill. A shorter active turn is a planning choice, not proof of an off-field mechanic.

Support means a member chosen to help the team's plan through utility or an applicable effect. The documented Outro system makes the destination of that assistance especially relevant. Evaluate a support by the benefit the intended teammate can actually use and by how that benefit fits into the sequence.

Healer means a member assigned to restore health. Identify the action that provides that restoration and when you can perform it. The broader support category and the healer label answer different questions: helping an attack sequence and recovering health are separate needs. Credit a character with both only after checking their kit.

Job	Evidence you need from the kit	What to watch during play
Main DPS	The actions or resources around which you intend to build damage	Whether setup leads into a useful attack window
Sub-DPS	A secondary damage sequence that fits the team	Whether their turn contributes enough to justify its length
Support	A relevant effect, its trigger, and its recipient	Whether assistance reaches the intended member
Healer	A health-restoring action and its requirements	Whether recovery is available when attempts need it

Treat this assignment as a working description you can revise. A character's rarity, element, or weapon category does not provide the missing skill text. For investment decisions built around these jobs, use Resonator Priority for F2P Accounts.

Pair each Outro Skill with a deliberate Intro recipient

Concerto Energy is the resource that connects successive active turns. The documented gauge runs to 100. When the outgoing Resonator has 100 Concerto Energy, switching triggers their Outro Skill alongside the incoming Resonator's Intro Skill. Attacks, Resonance Skills, Echo Skills, and defensive actions such as dodges or parries contribute to the documented resource-building system.

That connection explains why team order matters. You are choosing both the character who leaves and the character who receives the next entrance. A useful handoff must account for the outgoing effect and what the incoming member can do after their Intro Skill.

Read the relevant descriptions together. First identify what the Outro provides, then check the intended recipient's opening actions. If an effect applies to a particular element, action, or condition, confirm that the recipient meets that condition. Those restrictions must come from the actual skill; this guide does not assign an undocumented bonus to a named pairing.

Use these questions when comparing possible destinations:

1. What does the outgoing Outro Skill provide?
2. Which teammate has a planned action that can use it?
3. What does that teammate's Intro Skill contribute to their entrance?
4. Are the resources for the following actions ready?
5. What duration or switching restrictions does the effect description specify?

The research describes Outro buffs as temporary, so avoid building a plan that depends on an unspecified effect lasting indefinitely. Equally, do not assume every buff has identical recipients, duration, or behavior after another switch. Those details are character-specific checks.

Concerto Energy also has a ceiling: additional generation beyond 100 is wasted. When your plan repeatedly leaves a member at full Concerto Energy, inspect why the next handoff is delayed. That observation can reveal an awkward pairing or an unnecessary action. The Combat System Guide explains the resources behind these decisions.

Build a repeatable sequence around resource readiness

An opening sequence is only part of a usable team. Check what happens when you return to the first member and try to perform the plan again. The second pass can expose preparation that the initial opening concealed.

Keep Concerto Energy separate from Resonance Energy in your notes. Concerto Energy enables the Outro and Intro handoff. Resonance Energy is required for Resonance Liberation. The Forte Circuit is a character-specific mechanism that may involve its own resource or empowered action. Seeing one resource ready does not establish that the others are ready.

Build your first sequence in this order:

1. Choose the main attack sequence you want to enable.
2. Identify the assistance that should immediately precede it.
3. Give the preceding Resonator enough preparation to reach the intended handoff.
4. Place required recovery or other utility where you can reliably perform it.
5. Run the sequence again and note which resource interrupts the repeat.

For a hypothetical support-to-attacker pairing, the support's turn should end with a useful destination already chosen. After the swap, the attacker should perform the actions the support was preparing them to use. If the attacker must spend the entire benefit window doing unrelated preparation, reconsider the order or the pairing. This is a planning example, not a prescribed rotation for any named Resonator.

Use observed readiness to decide how much complexity to add. A sequence you can repeat and explain provides a better basis for comparison than an ambitious sequence you execute differently every attempt. Once the basic handoffs work, Quick-Swap Rotations addresses rotation construction in more detail.

Choose element spread for a specific reason

The six documented elements are Aero, Electro, Fusion, Glacio, Havoc, and Spectro. Record these alongside your intended roles, but make the decision through skill interactions and the encounter you are preparing for. A collection of different element labels is not enough evidence of a useful composition.

Separate two questions. First, what element-related condition does an individual skill or effect require? Second, what additional options would another element give your account? The first concerns a specific team sequence. The second concerns the range of teams you could prepare. Confusing them can lead you to add variety while leaving the immediate role gap unresolved.

For example, the roster identifies Yangyang as an Aero Sword user and Chixia as a Fusion Pistols user. Those facts let you compare their element and weapon categories. They do not establish that placing them together creates a particular reaction, transfers a particular buff, or improves a third member's damage. A stronger claim requires the relevant kit information.

When reviewing element spread, work through the following checks:

1. Identify any element condition explicitly stated by the effects you plan to use.
2. Confirm that the intended recipient or action meets it.
3. Read the target encounter's stated rules before choosing coverage for it.
4. Compare the revised team with your existing team under similar conditions.

Apply the same care to equipment. The research documents elemental Sonata Effects, including Sierra Gale for Aero and Sun-Sinking Eclipse for Havoc, alongside support-oriented options such as Rejuvenating Glow. An element match is one part of equipment selection; the effect's conditions still need to fit the assigned job. Use Sonata Effects when checking that layer of the build.

Use Rover's forms as alternative plans for one slot

Rover occupies a single character slot with menu-based attribute switching. The documented forms are Spectro, Havoc, Aero, and Electro, and the roster lists each as a five-star Sword user. Their separate form entries describe alternatives for the protagonist. They do not let you place Havoc Rover and Aero Rover together as separate party members.

Rover form	What the research establishes	Team-building use
Spectro	The starting form	A starting point for learning your active turn and handoffs
Havoc	Obtained through the main story; described as the main-DPS form	A documented candidate around which to plan primary damage
Aero	Documented as free, with a support/sub-DPS orientation and debuff conversion	An alternative when you want Rover to contribute through that interaction
Electro	A documented form introduced in version 3.5	An owned option to inspect; the supplied files do not establish its combat role

Havoc Rover gives you a concrete role-based starting point. If you choose that form for primary damage, evaluate the other members by the assistance and survival needs of that plan. Their element labels alone do not establish compatibility with Havoc Rover's intended actions.

Aero Rover illustrates a more specific interaction. The systems research describes conversion of other attribute debuffs, including Spectro Frazzle and Havoc Bane, into Aero Erosion. That gives you a mechanic to investigate when reading potential teammates' skills. It does not provide a complete named team, a conversion formula, or proof that every Spectro or Havoc Resonator supplies the required debuff.

Changing Rover's job also changes what the remaining party needs. If Rover was your main attacker and you switch to a supporting plan, identify who now supplies primary damage. Treat that as a composition change, then review the associated equipment and handoffs.

For form unlocks and attribute selection, consult the Rover Forms Guide. This guide leaves out Aero's introduction version because the supplied research conflicts on that detail, and it assigns no unsupported role to Electro Rover.

Audit the four-star roster before expanding it

The documented four-star roster gives you a practical list to compare with your account. Begin with ownership, equipment, and the skills you can inspect. A roster entry verifies that a Resonator exists with the listed attributes; it does not mean every player receives that Resonator free.

Four-star Resonator	Element	Weapon	Introduced in version
Yangyang	Aero	Sword	1.0
Chixia	Fusion	Pistols	1.0
Baizhi	Glacio	Rectifier	1.0
Danjin	Havoc	Sword	1.0
Sanhua	Glacio	Sword	1.0
Taoqi	Havoc	Broadblade	1.0
Yuanwu	Electro	Gauntlets	1.0
Aalto	Aero	Pistols	1.0
Mortefi	Fusion	Pistols	1.0
Youhu	Glacio	Gauntlets	1.3
Lumi	Electro	Broadblade	1.4
Buling	Electro	Rectifier	2.8

For each owned candidate, record the intended role, the action that proves they can perform it, and the teammate who should receive their Outro handoff. If you cannot fill in those details, inspect the kit before assigning the job. The supplied roster does not document individual healing actions, coordinated attacks, or buff values for these characters, so this table makes no such assignments.

Keep similar names separate during the audit. Yangyang is the four-star Aero Sword Resonator shown above. Yangyang: Xuanling is a separate five-star Havoc Sword Resonator introduced in version 3.5. Advice or equipment assumptions for one should not automatically be applied to the other.

Use the resulting list to identify what you can test immediately. An owned candidate with suitable equipment can be investigated before you commit currency to an alternative. Judge the result against your missing job and the same encounter, rather than treating four-star rarity as a complete assessment of usefulness.

Check Verina's intended job and launch-era alternatives

Verina is documented as a five-star Spectro Rectifier Resonator introduced in version 1.0. That places her among the launch-era options you may already own. The available files do not record her healing actions, specific buffs, or Outro conditions, so they cannot establish a detailed Verina support package or a recommended named rotation.

If you are considering Verina for the healer or support position, check the corresponding skill descriptions against the job table above. Identify the recovery action, any resource it requires, and what the next member receives on a handoff. Assign only the contributions you can confirm. A team recommendation needs those details even when the character's basic roster information is settled.

The other documented launch-era five-stars provide additional candidates to inspect:

Resonator	Element	Weapon
Jiyan	Aero	Broadblade
Yinlin	Electro	Rectifier
Calcharo	Electro	Broadblade
Encore	Fusion	Rectifier
Lingyang	Glacio	Gauntlets
Jianxin	Aero	Gauntlets

These are ownership and equipment references, not role rankings. For instance, owning both Verina and Encore means you have two documented Rectifier users with different elements. Weapon category compatibility is worth checking, but their shared category does not establish that the same passive or stat priorities suit both kits. Read Weapons Guide when assessing what your existing equipment actually supports.

Count Rebecca when you own her, and check event access separately

Rebecca is documented as a five-star Electro Pistols Resonator from the version 3.4 Cyberpunk: Edgerunners collaboration. The research records a free login-event route with a Union Level 10 requirement. This is a documented historical opportunity, not confirmation that an account starting in version 3.6 can still claim her.

If you obtained Rebecca during the event, include her in your roster audit before deciding that another Electro option is necessary. You already have an Electro Pistols candidate whose skills and equipment can be inspected. Her presence changes the ownership question; her suitability for a particular team still depends on what her actual kit contributes.

The supplied files establish Rebecca's rarity, element, weapon, and free event history. They do not establish her precise combat role, preferred partners, Outro restrictions, or damage performance. Do not fill those gaps by assuming that Pistols imply a particular role or that a collaboration character requires another collaboration character as a teammate.

If you did not claim Rebecca, check current event access before putting her into a build plan. The research provides no verified current claim window, rerun date, or permanent replacement route. Keep the immediate team based on owned Resonators while that availability remains unresolved. This distinction also prevents a historical “free team” suggestion from becoming an unusable shopping list for a newer account.

Budget the investment required to make the team functional

Owning a suitable Resonator is only the beginning of the build. The documented progression systems include Resonator levels and ascensions, Forte upgrades, weapon upgrades, and Echo equipment. A composition change can therefore create several material needs at once.

Separate those needs before farming. Resonator ascension uses a designated boss material, common enemy drops, a regional specialty, and Shell Credits. Forte upgrades use Forgery materials, common drops, and weekly-boss Skill Upgrade Materials. Weapons have their own levels and ascensions, with Energy Cores providing weapon EXP. These categories explain why a newly acquired member may need preparation before you can judge their team contribution fairly.

Prioritize a functional test build. Give the candidate enough preparation to perform the job you are evaluating, then inspect the relevant actions in combat. This is a budgeting approach, not a claim that every member needs identical investment or a universal stopping level. Upgrade choices should follow the actual kit and the obstacle you observed.

Echoes add both stats and Sonata Effects. The research documents five Echo slots and a maximum Cost budget of 12. Check that the proposed equipment fits the available budget and that its effects serve the assigned role. Avoid judging an unfinished candidate against an established member without acknowledging that equipment difference.

Waveplate provides a concrete resource constraint: its documented cap is 240, with regeneration of one point every six minutes. Decide whether preparing another member is more useful now than improving the team you already use. Resonator Leveling, Forte Upgrade Guide, and Waveplate Priority cover those investments in detail.

Evaluate a new pull against the team it would change

Start a pull decision with the current roster and one specific gap. Name the member the candidate would replace, the job they would perform, and the handoff they would participate in. If the new Resonator would anchor another team, identify the other members that plan requires.

Work through this sequence before spending:

1. Write the missing function. State whether you need primary damage, a complementary turn, applicable support, recovery, or another team option. Tie it to an observed problem.
2. Check owned alternatives. Review the relevant Rover form, owned four-stars, launch-era five-stars, and Rebecca if claimed. Look for an untested solution already on the account.
3. Verify the candidate's mechanism. Read the actual skill that would solve the problem. Element, rarity, and release date cannot substitute for it.
4. Place the candidate in the sequence. Identify who precedes them, who follows them, and which resources must be ready at each handoff.
5. Review equipment and materials. Determine which needs your inventory already covers and which would add a farming commitment.
6. Compare the complete plans. Judge the revised team against the current team and the option of improving an existing member.

Distinguish acquisition cost from build cost. For ordinary Featured Resonator Convene, the research documents Radiant Tide as the relevant currency and 160 Astrite per pull. It records a five-star within 80 pulls and a featured-character guarantee after losing the initial 50/50, producing a worst case of 160 pulls from a starting position without pity or a featured guarantee. Your existing banner state matters to that budget.

Banner categories also matter: the research states that pity is not shared between different types and that collaboration pity is separate from regular limited banners. Check Convene Guide before treating any displayed pull count as progress toward the candidate you want.

Use preference as an explicit part of the choice. Wanting to play a character is a valid reason to plan around them. Keep that reason separate from an unverified claim that they will repair every weakness. If a pull depends on an undocumented buff, an unowned partner, or equipment you have not budgeted, record that dependency before committing.

Expand your roster around the demands of the mode

One functioning party and an account prepared for several combat assignments are different projects. Build your next team in response to the mode you intend to play, so each investment has a destination.

Whimpering Wastes provides a documented reason to think beyond one party: its stages have two halves, each using a three-Resonator team. Plan the jobs for both halves and check the team-selection rules when allocating your roster. A candidate's value may come from completing another usable group rather than replacing your strongest member.

Tower of Adversity introduces Vigor constraints, so review where each Resonator is needed before investing around a single lineup. The supplied research disagrees on the Hazard Zone reset interval; this guide does not use an exact reset schedule to justify team-building priorities. See Tower of Adversity and Whimpering Wastes for mode-specific planning.

Keep mode-specific testing in context. Depths of Illusive Realm includes supplied maxed Resonators and its own buffs, while Phantasma Dreamland: Rhapsody has Strange Encounters and Relics. A successful run under those conditions can help you explore a play pattern, but it does not by itself establish how your ordinary equipped team will perform elsewhere.

Run a controlled team check before the next major upgrade

Use a short, repeatable review to turn the composition into an investment decision. Choose the encounter that exposed the original problem and keep the comparison focused on that problem.

1. Record the lineup and equipment. Note Rover's selected form and the job assigned to each member. This makes the setup reproducible.
2. State the expected handoffs. Identify the intended Outro recipient and what they should do after their Intro Skill.
3. Watch each resource separately. Observe Concerto Energy, Resonance Energy, and the relevant Forte Circuit requirements.
4. Check the repeat. Note where the next pass through the team differs from the opening.
5. Track survival failures. Identify whether health recovery, resource preparation, or missed defensive actions interrupted the attempt.
6. Change one decision and compare. Try a different handoff or one roster substitution before changing several builds together.

Defensive execution belongs in this review. The documented combat system includes a Dodge Counter after a Perfect Dodge and parries against attacks with the golden cue. Parries also contribute to reducing Vibration Strength. If missed defensive actions keep ending attempts, practice that specific interaction using Parry, Dodge, and Vibration Strength before interpreting every failure as a roster deficiency.

End the check with an actionable observation: the intended Intro now triggers, the attacker enters prepared, recovery becomes available at the needed point, or the replacement still lacks the required mechanism. Use that result to choose the next upgrade or pull. You now have a concrete reason for the expenditure and a way to tell whether it solved the original problem.