What synergy means here
The official store description gives us a safe starting point: the game is built around a squad, upgrades, and a survivors-style run. A synergy is useful when one choice makes another choice more reliable in the same run. That might mean coverage protects a focused weapon, a team member covers a weakness, or an upgrade keeps a damage pattern active while the squad moves.
The phrase best team is broader than any one player post. Use it as a question to investigate, not as a result we can announce without a version, mode, difficulty, and evidence set. The Steam Community discussion supplies examples of player routes; it does not turn one route into an official ranking.
Build by jobs
Start by assigning jobs instead of collecting names. A working team usually needs a way to keep the screen manageable, a way to pressure durable targets, and enough survivability or uptime to keep those jobs online. The exact character and weapon that fill each job should be verified against the current roster and upgrade pages.
When two roles overlap, ask whether the overlap is deliberate. Two sources of the same kind of damage may clear early waves quickly but leave a later gap. Conversely, a mixed route can feel weak at the start but become stable once its coverage comes online. Record that timing instead of scoring the team from its first minute alone.
- Define the main damage job before selecting a second weapon.
- Choose one coverage or control answer for the pressure your first choice cannot handle.
- Keep a survival or uptime plan so the team can continue delivering damage.
- Name the mode and difficulty whenever you report a result.
A two-run comparison protocol
To test a synergy, hold the mode, difficulty, opening team, and intended route steady. Change one team member or one upgrade family, then record the first meaningful difference: safer movement, faster clearing, better target pressure, or a new failure point. Repeat before using words such as consistent or best. A single high-roll run is a lead, not a conclusion.
This protocol also makes community advice easier to read. The player discussion can show what to try; your notes show whether the interaction survives a second context. Link weapon-specific findings to Rocket Launcher vs Minigun or Weapon Upgrade Route instead of burying them in a general team paragraph.
Version boundary and next page
The 1.0 General Points page is the companion for broader account or general-point decisions. It uses the Steam displayed release date 2026-08-20 and keeps the official announcement date 2026-08-19 as a source-date note. If your question is specifically about point allocation rather than team interaction, follow that page; the two pages link to each other so the build context is not lost.