INT vs STR in Alien Invasyndrome

INT and STR are the two planning axes every Alien Invasyndrome Demo larva eventually faces. They are not moral choices — they are risk budgets. INT-leaning spends buy setup quality: safer peeks, cleaner nest commutes, and fewer coin-flip Kitchen crossings. STR-leaning spends buy commit success: finishing a capture window you already earned with position. This page compares early priorities, when to pivot, and how Security Route A vs B changes the math. Pair it with Skill Tree, Early Build, Evolution Paths, and Skill Planner.

18+ adult stealth-action; advice stays mechanical. Developer Mozu Field / 百舌鳥, publisher Shady Corner Games, Steam app 4603980, full release TBA. Hub: Skills Hub.

INT vs STR in one table

Axis	What it buys	Early Demo value	Late Demo value
INT	Setup, timing, control tools	High — learning Atlas without donation detects	Medium — still needed for Clinic/Lab patience
STR	Commit finishers, pressure tools	Low until windows exist	High — Security and boss commits

Neither axis removes the ~1 minute detection hide. Read Stealth and Detection before you interpret STR as “skip stealth.”

stealth gameplay with hypnosis power

Early priorities — INT usually wins first

The first meaningful hour on Atlas is an education tax. Crew cones, desk softlocks, and nest commutes punish ego. That is why Early Build sequences setup-first clusters before STR finishers.

Phase 0 — spend zero points

Complete control and stealth literacy:

• How to Play
• Keyboard Controls and Stealth Actions
• Softlock Fixes desk exit tests
• Kitchen Route wall-line crossing

If Phase 0 fails, STR only accelerates bad habits.

Phase 1 — INT-leaning Priority A

Buy the smallest INT-leaning cluster that makes Middle transit less suicidal. Practical targets:

• Fewer accidental reveals at Kitchen doorways (Key Rooms).
• Safer return paths to nest (How to Nest).
• Tools that reward patience over sprinting (Vents and Cover).

Log the cluster in Skill Planner. Re-test the same loop twice before buying more.

Phase 2 — colony commute armor

Second wave can stay INT-leaning or hybrid, but the job is return safety, not flashy captures. Evolution Paths calls this colony identity: nest cadence before Security ego.

When STR becomes honest

STR is not “bad.” It is early when bought before you can create windows. STR becomes honest when:

1. You complete a Middle silence loop without random detects.
2. Nest commute is shorter than your greed (Atlas Overview).
3. You can spot → hide → exit on purpose using Detection Timer.
4. You know which room you are trying to finish next (How to Capture vs nest banking).

Then buy STR tools that finish interactions — not tools that tempt you to start fights in Cafeteria open floor.

When to pivot INT → STR (or back)

Pivot deliberately, not every death:

Signal	Pivot
Detects dropped but captures fail at the last second	Add STR commit tools; keep INT commute nodes
Captures succeed but every return donates a minute	Add INT commute tools; delay STR
Security A prep feels slow but safe	Stay INT-leaning; do not STR-rush A
Security B prep needs faster commits after setup	Hybrid INT base + STR package
Softlock under desk	No pivot — fix exits (Softlock Fixes)

Write the pivot reason in Skill Planner before spending. One variable at a time.

Security A / B implications

Security Room is where INT/STR theory meets chokepoint reality. Read Security Room and pick one route in Security Routes before you specialize.

Route A — patience tax

Way A rewards setup quality:

• INT-leaning plans fit naturally — longer waits, softer peeks, desk discipline.
• STR dumps before you can enter A cleanly usually create extra crossings in sightlines you were avoiding.
• Crew context: Crew patrol economy still applies.

Route B — commit timing

Way B shifts pressure:

• Hybrid INT/STR often fits — you still need setup, but commit tools matter earlier.
• Pure STR without Middle literacy tends to fail B the same way it fails Kitchen center-lane sprints.
• Boss readiness still separate: How to Beat Boss.

Rule: buy for one route package in Early Build Phase 4 — not both.

INT/STR and evolution identity

Evolution Paths frames INT as setup path and STR as commit path. Tree purchases make that identity visible. A colony path larva can still buy STR — but only after nest cadence is honest. A commit path larva still needs INT commute nodes or Security becomes tilt.

Demo WIP menus may show duplicate-learn noise. Trust live labels on Skill Tree and patch notes on Changelog, not a screenshot from 0.99 footage.

Video context — hypnosis power clip

The embedded stealth gameplay with hypnosis power video shows INT-leaning control fantasy: positioning, timing, and a power that rewards setup rather than raw rush. Use it as pacing reference — pause when the skill interface appears and map nodes to your Skill Planner plan. Do not copy a speedrun order if your Demo build labels differ.

Map timing still comes from Map Hub pages and Demo Walkthrough. Save hygiene if you grind repeats: Save and Progress.

Sample INT-first card (first hour)

• Identity: setup → colony → limited commit
• First buys: INT commute survival
• Second buys: nest return safety
• STR: delayed until Kitchen loop is boring
• Security: one route package only
• Forbidden: STR dump before silence loops

Sample hybrid pivot card (pre-Security)

• Keep INT nodes that protect nest returns
• Add STR nodes that match one Security route
• Abort plan written before door approach
• Detection timer ready — no panic re-spec

Common INT/STR mistakes

1. STR to fix softlocks — desks need exits, not muscle.
2. INT hoarding forever — eventually you must commit for Demo clears.
3. Respec-by-death — changing both axes every wipe hides the real failure.
4. Ignoring nest gates — some tools arrive after nest interaction; see How to Nest.
5. Security A/B mash — hybrid panic spends fail both routes.

Related reading

• Skills Hub
• Skill Tree
• Early Build
• Evolution Paths
• Skill Planner
• Guides Hub
• Walkthrough Hub
• Updates Hub

Bottom line

INT buys learning time on Atlas; STR buys finishers once windows exist. Early Demo clears favor INT-first sequencing from Early Build. Pivot with a written reason, specialize for one Security route, and confirm every label on the live Skill Tree screen.