This wuthering waves best teams piece is a ledger rather than a ranking. Waveplate caps at 240 and regenerates roughly one point every six minutes, which puts a week near 1680 points. Tower goes first, skill domains second, Echo domains last, and the standard Echo split is 4+3+3+1+1. The wuthering waves team comps notes at the end cover substat priority and how to divide teams for multi-stage Tower runs.
Applicable version: 3.7 (client 3.7.2, updated 2026-10-19)
Wuthering Waves 3.7 overview: what the October 19 client update means
The official store record shows Wuthering Waves updating to client 3.7.2 on 2026-10-19, with release notes limited to crash fixes on certain iOS devices .
A point release does not change build logic
3.7.2 is a fix build and does not touch character values or Echo rules, so the 3.7 progression path stands. Actual version content follows official notices; do not read a crash-fix note as new content.
Anchor the version properly
The most common guide error is pasting 3.6 homework onto 3.7. The check is simple: look at the client version and its date, and only discuss builds that postdate 3.7.2.

Wuthering Waves Echo builds: five slots and a 12 COST cap
The Echo system gives you five equipped slots with a combined COST limit of 12, and the main Echo usually takes 4 . That leaves a small set of valid splits.
4+3+3+1+1 is the standard close
A 4-cost main Echo, two 3-cost Echoes and two 1-cost Echoes total exactly 12. This keeps the set bonus and main stat on the main Echo while leaving two 3-cost slots for substat tuning. Putting two 4-cost Echoes in the lineup exceeds the cap, and the UI refuses the configuration outright.
Substat priority follows the damage source
Main DPS wants crit rate, crit damage and ATK%; sub-DPS wants resonance efficiency plus the matching elemental bonus; supports want resonance efficiency and healing bonus. Chase substats only after the first two main stats land, and never refarm a whole set for one substat .

Wuthering Waves weekly Waveplate ledger: planning around the 240 cap
Waveplate caps at 240 with roughly one point per six minutes, which refills a full bar in a day. Over a week that is about 1680 points.
First priority: Tower of Adversity
Tower resets on a cycle, and a missed cycle is a missed payout. It tests team strength rather than Waveplate, so clear Tower before deciding where the rest of the bar goes.
Second priority: main DPS skill domains
Skill materials are a hard gate. Without levels, even perfect Echoes underperform. Keep at least one key skill level on the main DPS moving every week.
Third priority: Echo domains
Echo farming is a probability game, and wrong substats return zero. Put it last, spend leftovers there, and stop once the build is usable.
A practical daily split: log in, claim dailies, patch whichever gap hurts most, then dump the remainder into Echoes. If the day goes sideways, only the Echo farm gets cut, and fixed income survives.

Wuthering Waves Tower teams: division beats raw power
Tower requires relay teams, and one overbuilt squad cannot absorb every stage. The current 3.7 buffs and enemy layouts follow the in-game notice; the split below is generic.
Carry, sub-DPS, safety net
Team one holds your best-built carry and takes the hardest stage. Team two uses a sub-DPS plus two supports for mid stages. Team three absorbs low stages with leftovers. Do not share supports across teams, or a stuck team one leaves team two with nothing.
Do not concentrate resonance chain and weapon in one unit
Resonance chain improves rotation quality and the weapon improves per-hit damage. Stacking both on one character collapses against an element matchup; moving one piece to team two usually raises clear consistency.
One more thing worth saying: Tower swaps enemies, not your roster, so team two should be able to stand on its own rather than exist to make team one stronger. The stronger team one is, the more independent team two should be.
Wuthering Waves 3.7 resources: who gets enhancement materials
Echo enhancement materials split into basic and advanced tiers, and the advanced tier is scarce, so week one goes to the main DPS and the main Echo .
Main Echo first
The main stat decides whether the set is usable at all, and it is the only slot that can carry 4 COST, so enhance it into a working range before touching substat slots. The opposite order spreads materials across four slots and ends with nothing usable.
Keep a weekly buffer
The tension is that enhancement materials are finite, so a buffer means giving up some farming. A workable compromise: treat Monday and Thursday as full-clear days, run minimum dailies the rest of the week, and decide on Sunday whether one more Echo round fits.
Keep roughly 200 Waveplate out of the plan each week for temporary events or double drops. Fully booked accounts have to squeeze events out of Tower time.

Wuthering Waves 3.7 FAQ
When did 3.7 update?
A: Client 3.7.2 shipped on 2026-10-19 and is a fix-oriented point release .
What is the Echo COST cap?
A: Five slots share 12 points, and the common split is 4+3+3+1+1 .
What should Waveplate go to each week?
A: Tower first, main DPS skill domains second, Echo domains last; a week yields roughly 1680 points.
Should I refarm Echoes with wrong substats?
A: Use them once the first two main stats land and only chase substats when it does not threaten next week's plan.

Wuthering Waves 3.7 action list
- Clear this cycle's Tower before spending the rest of the bar.
- Push at least one main DPS key skill level this week.
- Build Echoes as 4+3+3+1+1 and enhance the main Echo first.
- Move either the resonance chain or the weapon to team two.
- Reserve about 200 Waveplate for temporary events.
Later 3.7 events and banners follow official notices, and gghubs.com updates the weekly ledger when they land.