SUITBORN NIGHT 3 Night 2 — Anguirus, Bart, Dart & Csybot
Multi-threat survival when SUITBORN escalates beyond Gojira into coordinated facility pressure.
Night 2 in SUITBORN is where SuperBao90’s alpha horror stops being a single-monster tutorial and becomes a coordination exam. After Gojira teaches generators, cameras, and closets on Night 1, Night 2 introduces Anguirus alongside variant threats Bart and Dart, plus the systemic pressure of Csybot. This guide explains how those names map to in-game behavior, how squads should call threats, and which Night 1 habits must change immediately.
Night 2 threat roster
| Name | Role in Night 2 | Player focus |
|---|---|---|
| Anguirus | Primary physical hunter | Route denial, repair interrupts |
| Bart | Variant pressure / alternate pacing | Confirms when “safe” lanes suddenly aren’t |
| Dart | Fast harassment / angle checks | Punishes greedy task paths |
| Csybot | Systemic or assist threat | Overlaps with cameras, tasks, or map logic |
Community naming follows TMITS-adjacent kaiju nods, but survival strategy cares about patrol overlap, not lore trivia. When in doubt, call compass direction and wing name — not debate spellings in chat.
How Night 2 differs from Gojira
Night 1 fails are usually single-point mistakes: one runner caught alone, one camera panic, one early closet exit. Night 2 fails are cascade failures:
- Anguirus pushes while Dart checks a flank you assumed was clear
- Bart’s presence forces a reroute that drops generator timing below 6 AM margin
- Csybot spikes anxiety or task complexity while cameras already watch another wing
If your squad still plays Night 2 like Night 1 with extra screaming, revisit Gojira fundamentals before blaming entity RNG.
Anguirus — anchor hunter behavior
Anguirus behaves like the “main chase” entity on Night 2:
- Corridor control — prefers locking the map center, splitting repair pairs
- Repair denial — approaching offline generators during mid-chain repairs
- Closet flushing — lingering near known hiding clusters after a pass
Counterplay:
- Stagger repairs — never sync both generators on the same wing without camera cover
- Use fake progress — start a repair, break early if Anguirus audio trends closer, resume after callout
- Hold office calm — anxiety spikes from dual threats snowball faster than Night 1
Bart and Dart — variant pressure
Bart and Dart represent alternate pacing layers community guides group with Anguirus:
- Bart — often associated with slower, oppressive map presence that makes shortcuts feel unsafe even when Anguirus is distant
- Dart — faster harassment that punishes players who sprint tasks without listening
Practical squad protocol:
- Camera watcher calls primary (Anguirus) and secondary (Dart/Bart) when both audibles exist
- Runners mark task abort zones when Dart angles appear on minimap-less wings they memorized from Night 1
- Do not assume Bart is “harmless background” — variants exist to break repetitive safe routes
Exact timings shift in alpha patches. Re-test after every Patch Notes drop — V3.7 adjusted idle presentation for classes, which indirectly helps spot motion in dark halls.
Csybot — systemic threat layer
Csybot is Night 2’s wildcard: less about one stomp line and more about systems overlap. Players report Csybot tied to:
- Camera or UI disruption windows that spike anxiety
- Task objective complications during generator crunch time
- Map zones that suddenly require two-player confirmation
Treat Csybot as a timer accelerator. When Csybot activates, simplify the plan: one generator, one task batch, no hero plays.
Camera room upgrades for Night 2
Night 1 camera discipline is necessary but insufficient:
- Maintain a priority queue — Anguirus > Dart > Bart > Csybot UI cues
- Pre-assign emote vocabulary for “abort repair” vs “hold closet”
- Rotate watchers every few minutes; dual-threat nights burn out camera mains fast
Night Vision (~150 Robux) remains optional clarity for runners returning from dark wings — not a substitute for callouts.
Generator and task scheduling
Use phased shifts instead of parallel chaos:
| Phase | Goal | Threat focus |
|---|---|---|
| Opening | Secure nearest generator | Anguirus spawn bias |
| Mid | Split tasks + second generator | Dart flanks |
| Crunch | Finish backlog tasks | Csybot timers |
| Endgame | Hold 6 AM margin | All active |
If crunch phase overlaps with Csybot, cut optional tasks. Extraction beats perfection.
Closet discipline under multi-threat
Closets fail on Night 2 when players hide from Anguirus but forget Dart’s faster pass:
- Enter on secondary callout, not only primary stomps
- Wait for two audio fades when dual threats were confirmed
- Exit toward camera-confirmed safe wing, not last known safe from Night 1 memory
Class and gamepass notes
Classes from Classes Overview matter more here:
- Kenji Fujimoto (Bloodbath unlock) helps experienced squads recover from bad angles — not beginners ignoring callouts
- Clock gamepass players can anchor shift timing for crunch phases
- Promo codes do not unlock classes — ignore fake strings promising Kenji
Path to Night 3
Night 2 mastery gates sensible Kong Night 3 practice. Kong is live in V4.0 but still receives alpha hotfixes, but multi-threat call discipline is the transferable skill. Read Night 3 Roadmap for place status without skipping Night 2 reps.
Related pages
- Gojira — Night 1 fundamentals
- Kong Night 3 — upcoming Night 3 entity
- Players Hub — full entity and class index
- Classes Overview — survivor roles for Night 2 comps
Frequently Asked Questions
Quick answers to the most common questions.
Do Bart and Dart spawn every Night 2 run?
Alpha builds vary. Assume variants can appear and plan routes accordingly rather than gambling on a fixed spawn table.
What is the hardest part of Night 2?
Coordinating callouts when Anguirus and faster threats overlap — not raw sprint skill.
How does Csybot differ from Anguirus?
Anguirus is the primary physical hunter. Csybot accelerates systemic pressure like tasks, cameras, or UI spikes.
Should we practice Night 2 before buying gamepasses?
Yes. Night Vision and Clock help but cannot fix broken comms or generator scheduling.
Is Night 2 required before Night 3 Kong content?
Not strictly, but multi-threat discipline from Night 2 makes Kong tests far less chaotic on live Night 3 shifts.
Where do I report changed Night 2 behavior after patches?
Cross-check Patch Notes first, then community threads linked from Updates Hub if alpha hotfixes land mid-week.