JUST ONE MORE ASYM teams win by making the next decision easier for one another. The official description gives the structure: an AI Aberrant works with player Adversaries against 13 Survivors. That creates two teamwork problems at once. Survivors must keep a large group useful without clumping into every attack, while Adversaries must amplify a predictable AI threat without abandoning it for personal chases.
Use calls that produce an action
A good call contains threat, place, direction, and need. “Seeker, District road, moving to buildings, need peel” tells a teammate what to do. “Hunter here” does not. Use stable landmark names from the Maps Dex and repeat only when the situation changes.
When voice is unavailable, use pings, short chat, and visible movement. Move toward the called regroup point rather than circling between two groups. Do not spam a target marker after the team has decided to disengage.
Survivor team shape
Think in three layers. The front line controls contact and protects entrances. The middle layer interrupts, zones, or adds damage when the front line creates a safe opening. The back line sustains, provides information, and keeps escape routes visible. Character labels can change, but this shape helps any roster.
Frontliners should not chase so far that the backline becomes the new front. Supports should not stand on the same pixel as the tank; spread enough to avoid one area attack while remaining close enough for peel. Midliners should watch side routes and player Adversaries instead of tunneling only on the Aberrant.
Adversary team shape
The Aberrant supplies the main predictable pressure. One Adversary can reveal or control the route, another can close the exit, and a faster attacker can punish the isolated target. You do not need all player hunters on the same angle. You do need agreement on which Survivor and which route matter.
If the AI changes target, update the call. A trap or debuff placed for the previous route may no longer help. When the Survivor group turns together, fall back toward the Aberrant rather than feeding separate eliminations.
Regroup before the next engagement
Survivors should regroup when stamina is low, a support is exposed, multiple abilities are unavailable, or the hunters have both sides of a route. A regroup is not passive waiting: identify the next cover, restore formation, and decide who takes first contact.
Adversaries should regroup when the Aberrant is far away, a rush character has spent its escape, or the target reaches a full team stack. Resetting preserves pressure. A failed solo dive gives Survivors a numerical window to attack the remaining hunter layer.
Assign jobs before special pressure
Caller
Names the main threat, route, and regroup point. The caller should update facts, not narrate every animation.
Peel
Protects the targeted teammate and blocks the second threat. Peel ends when the teammate reaches safety; do not turn it into a map-wide chase.
Control
Watches flanks, traps, slows, marks, and chokepoints. Control makes another teammate's damage or escape reliable.
Recovery
Tracks who needs space, healing, or stamina time. A recovery player calls when the team is ready to move again.
These jobs can move between players. A backliner under pressure becomes the protected target; a healthy midliner may take over calls. What matters is that the team knows who is doing each job during the current exchange.
Fight the correct layer
Survivors often lose by attacking the Aberrant while player Adversaries reach the backline. Ask which layer is creating the immediate danger. If a control Adversary has trapped the escape, clear or avoid that setup before committing to the AI. If an Adversary is isolated while the Aberrant paths elsewhere, a coordinated counterattack may be possible.
Adversaries should do the reverse. Do not duplicate the AI’s chase from directly behind. Take the route that forces the Survivor back toward the Aberrant, pressure the healer waiting at the destination, or stop the disruptor preparing a peel.
Map-based team habits
On District, use buildings, roads, and parking areas as clear calls. On Cloud Nine, announce bridge and island movement early because narrow crossings limit rescue paths. On Green Garden, agree whether the team owns the center or is rotating around the edge. On Double Runes, distinguish pillar side and stair level rather than saying “middle.”
Every regroup point needs two exits. If both teams know the only route out, it is a trap rather than a safe anchor. Change the anchor after repeated pressure so Adversaries cannot pre-place every setup.
Review losses without blaming roles
After a loss, identify the first broken connection: a missed call, an unsupported dive, an empty stamina bar, a blocked route, or a late regroup. Avoid reducing the review to “bad character.” The same pick can look weak in a scattered lobby and powerful when its setup receives follow-up.
Use the team compositions guide to compare functional roles without treating a community lineup as a guaranteed best team. Exact team size, character limits, and live balance remain in-game verification items.
Frequently asked questions
Should Survivors stay together all the time?
Stay connected, not stacked. Keep peel and recovery range while spacing around area pressure and maintaining more than one route.
Who should call targets?
Use the player with the clearest information and calmest view. The caller can change when that player becomes the chase target.
How should Adversaries support the Aberrant?
Reveal routes, close exits, control key space, and punish the target the AI already pressures. Avoid long solo fights on the opposite side of the map.
When should Survivors fight back?
When threats are separated, the team has stamina and key abilities, the backline is protected, and there is an exit. Otherwise, regroup and wait for a better window.