Alien Invasyndrome Characters Hub

What this hub covers

Alien Invasyndrome puts you on the exploration vessel Atlas as a weak alien larva. Crew and medical staff are not collectible roster cards — they are detection sources, room timers, and encounter gates. This Characters Hub explains those roles in mechanical language so you can plan softlocks, nest runs, and Security Room prep without treating every NPC as a lore dump.

All characters are written as 18+. Adult content exists in the Steam Demo; this wiki does not catalogue scenes. We only note when a role changes patrol pressure, Clinic timing, or recovery options after a spotting.

Developer Mozu Field / 百舌鳥, publisher Shady Corner Games, Steam app 4603980. Full release remains TBA. Demo builds float near v0.99.x, so labels and spawn beats can shift — verify against your installed build and the Changelog.

crew / character focused gameplay

Pages in this section

1. Crew — general patrol roles across Kitchen, Cafeteria, Laboratory, and deck corridors: sight cones, idle turns, and when to abort into a desk softlock.
2. Doctor — Clinic-associated medical crew as an encounter guide: wing layout pressure, hide furniture, and nest-risk timing.

Read both before you treat Clinic or Cafeteria as free loot rooms. Pair them with Stealth and Detection and Key Rooms.

How to use character pages

Use character pages as threat profiles:

• Where the role usually walks (Kitchen line, Clinic bay, Cafeteria floor).
• How long a failed read costs you (~1 minute hide after a clear spotting).
• Which nest or skill beats reduce retry pain (stealth nodes first; then INT or STR per Early Build).
• Which walkthrough segment owns the room (Kitchen Route, Demo Walkthrough).

If Japanese UI text blocks menu reads while you study encounters, configure Locale Emulator before blaming the NPC.

Crew as a system layer

Atlas crew exist to enforce the stealth fantasy. They punish sprinting through open sight lines, reward desk softlocks, and force nest banking between commits. When a crew member turns toward your last tile, the correct response is usually hide → wait → re-scout — not a panic STR dump. Details live on the Crew page.

Cross-check room names against Atlas Overview and Decks. Top / Middle / Lower deck language in guides maps to where patrol density feels highest in the Demo slice.

Doctor and Clinic as a gated wing

The Clinic is a landmark space with medical crew pressure. Treat the doctor role as a timed encounter zone, not a romance checklist. Softlock furniture near Clinic approaches matters as much as the interaction itself. See Doctor and keep Softlock Fixes open if hide exits fail.

Clinic routing often sits between early Kitchen comfort and later Laboratory / Security Room risk. If nest income is thin, do not force medical-wing commits — return to How to Nest.

Security Room is not a character page

Route A / B branching in the Security Room is a systems gate, not a named character hub entry. Character pages still matter there: crew density and detection discipline decide whether you arrive with nest power or arrive broken. Finish character reads, then open Security Routes and How to Beat the Boss.

Recommended reading order

Session setup: How to Play → this hub → Crew.
Clinic push: Doctor → Key Rooms → nest check.
Mid Demo: Security Room → Walkthrough Hub.
Buyer context: Demo Review and Pros and Cons.

Tools that help while studying NPCs

• Detection Timer — practice the hide penalty while you learn crew turns.
• Nest Checklist — keep colony goals honest between encounters.
• Skill Planner — allocate INT/STR after you know which rooms punish your current build.

Demo honesty

The Demo is a vertical slice. Not every Steam blurb fantasy appears as a fully voiced cast list. If a role behaves differently after a patch, prefer Steam build notes and Updates Hub over assuming this hub is frozen. Wishlist the TBA full game from Steam Status if the systems click.

Tone reminder

Mechanical. Brief about 18+ framing. No pornographic detail. When an encounter matters, we talk timers, desks, nest risk, and route order — then send you back to Guides Hub for the loop that actually wins runs.