How to Play Against The Singularity
The Singularity Matchup Mini Guide
The Singularity is a high-threat matchup. Your core job is to deny uncontested camera setup and sloppy emp timing. while preserving objective tempo.
First 90 Seconds
- Opening priority: Track first pod cluster and route away from it.
- Primary scout check: Call pod zones and which lanes are currently unsafe.
- Most common early throw: Ignoring side-objective pressure. Fix: assign one player to manage it early.
Mid-Match Conversion
- Best chase adjustment: Pre-drop when macro pressure has already removed safe backup routes.
- Best macro adjustment: Adapt gen strategy to secondary objectives; pure gen rush is often punishable.
- Pattern to respect most: Tag one lane, then teleport pressure to another for split chaos.
Map And Loadout Read
- Maps helping The Singularity: Maps with strong pod sightlines and objective overlap
- Maps hurting The Singularity: Irregular LOS maps where pods are harder to leverage
- Build path anchors: Information / Aura Intel, Self-Sufficiency (Solo Queue), Totem / Anti-Hex, Anti-Tunnel
At-a-Glance
- Threat level: High
- Biggest danger: Slipstream network can convert one bad interaction into rapid chained pressure.
- Best counterplay theme: Manage EMP windows and deny free camera network value.
- Solo queue note: Solo queue needs clear EMP discipline or pressure spikes get out of control.
Threat Model
- What the killer wants: Set camera info web, apply Slipstream, then chain teleports for tempo.
- What you must deny: Uncontested camera setup and sloppy EMP timing.
Power Basics (Plain English)
- What their power does in real matches: He monitors via pods, applies Slipstream, and teleports for fast chase pressure.
- What “good usage” looks like: Good Singularity players sequence info and chase so every interaction compounds.
Early Game Plan
First 60–90 seconds priorities
- Track first pod cluster and route away from it.
- Use EMPs on meaningful lanes, not random low-impact pods.
- Avoid objective stacking in pre-networked sectors.
What to scout/call out
- Call pod zones and which lanes are currently unsafe.
- Track EMP inventory timing across team.
- Warn when slipstreamed survivors are near each other.
Chase Rules
- Pre-drop when macro pressure has already removed safe backup routes.
- Greed only if team info confirms no secondary pressure angle.
- Rotate early to avoid being trapped in scripted objective states.
- Commit to chases only when team can absorb macro fallout.
- Do not tunnel-vision one interaction while side objectives collapse.
- Respect hidden timers and delayed punish windows.
- Break predictable movement once killer starts conditioning routes.
- Use comms/pings to prevent repeated macro mistakes.
- If killer forces mini-games, simplify decisions and deny free value.
- Take guaranteed tempo over flashy outplays in unstable states.
Macro Rules
- Adapt gen strategy to secondary objectives; pure gen rush is often punishable.
- Hook trades should account for side systems, not only timer bars.
- Prevent snowball by assigning clear roles for objective, rescue, and scout duty.
Common Killer Tricks
Pattern 1
Tag one lane, then teleport pressure to another for split chaos.
Tell: Pod placement around future objective not current chase.
Pattern 2
Force EMP usage early, then commit during downtime.
Tell: Rapid target swaps after slipstream spreads.
Pattern 3
Hook near pod network to punish routine rescues.
Tell: Aggression spikes when team EMP economy is low.
Common Survivor Mistakes (Fixes)
- Ignoring side-objective pressure. Fix: assign one player to manage it early.
- Chasing flashy plays while macro collapses. Fix: prioritize win condition order.
- Overcommitting to one lane. Fix: rebalance roles every major event.
- Trading hooks without system awareness. Fix: track both hook and side timers.
- Late reactions to killer setup cycles. Fix: pre-plan responses.
- Assuming normal chase rules always apply. Fix: adjust for power state first.
- Wasting resources on low-impact windows. Fix: save tools for conversion moments.
- No contingency for solo queue drift. Fix: default to self-sufficient lines.
Map Notes
Map types that help/hurt
- Help the killer: Maps with strong pod sightlines and objective overlap
- Hurt the killer: Irregular LOS maps where pods are harder to leverage
Tiles/areas to respect
- Pod-covered rescue routes
- Clustered central objectives
- Slipstreamed teammate proximity
Recommended Build Types
Quick Checklist
- Track secondary objectives constantly.
- Reassign team roles after each major event.
- Avoid pure autopilot gen rushing.
- Use safe, repeatable chase lines.
- Trade hooks with macro context.
- Call out timer and power-state changes.
- Stabilize before forcing high-upside plays.
- Default to self-sufficient decisions in solo queue.