Alien Invasyndrome Demo Changelog Notes

Honest scope of this page

This is not a scraped mirror of every Steam patch paragraph. Alien Invasyndrome’s Demo iterates, and exact notes shift. As of community and update-tracker framing in May 2026, the live Demo conversation centers on a Demo 1.0 hotfix (May 5, 2026) after a long climb through earlier preview builds. Treat the sections below as verified change classes and timeline anchors — not as a forged line-by-line ledger of every string edit.

Game: Steam app 4603980, developer Mozu Field / 百舌鳥, publisher Shady Corner Games. Full release remains TBA. Adult 18+ title; changelog talk here stays mechanical.

Sibling pages: Steam Status, Demo Access, Version History. Hub: Updates Hub.

Timeline spine — 0.65 → 0.99 → Demo 1.0

Players and older footage often still reference mid-preview numbering. A useful mental spine:

1. ~0.65 era — early public gameplay slices; Atlas stealth and larva fantasy already visible. Historical footage context lives on Version History (older build recordings age fast).
2. Room expansion era (~0.81 style chatter) — Kitchen, Clinic, Laboratory, Cafeteria, and Security Room become the landmark set players actually route.
3. Doctor / Clinic event era (~0.91 style) — medical-wing first-meeting pacing enters the Demo conversation; see Doctor and Clinic Doctor Route.
4. Late 0.99.x — skill labels, nest UI, and detection feel still drift while the fantasy stays stable.
5. Demo 1.0 + May 5, 2026 hotfix — treat this as the current “play this build” checkpoint until Steam shows a newer string.

Exact internal patch titles can disagree with community shorthand. Always prefer the version string on your Steam install over a wiki sentence.

How to verify your Demo version

1. Open Steam → Library → Alien Invasyndrome Demo (or the listed Demo entry).
2. Note the version / build string Steam shows for your install.
3. Skim store news or patch notes if any exist for that build.
4. Only then compare against wiki steps in Guides Hub or Walkthrough Hub.
5. If UI language is the blocker, fix Locale Emulator before assuming a regression.

When reporting issues, include: version string, room (Kitchen / Clinic / Lab / Cafeteria / Security), and whether you were in a detection hide or a true stuck softlock (Softlock Fixes).

Demo 1.0 hotfix — what to re-test first

After installing or updating into the Demo 1.0 hotfix window, run a short regression drill before a Security push:

1. Softlock enter / exit under a Kitchen desk.
2. One intentional spot → full ~1 minute hide with Detection Timer.
3. One nest bank cycle (How to Nest, Nest Checklist).
4. Skill screen label check (Skill Planner, Skill Tree).
5. Optional Clinic approach scout only if nest is healthy (Clinic Doctor Route).

If hide no longer exits, escalate to Softlock Fixes before grinding Laboratory. Save friction has appeared in some earlier builds — if a save fails to resume cleanly, note the build string and avoid stacking long Security attempts on a suspect save slot.

Change class A — stealth and detection feel

Patches in stealth Demos commonly nudge:

• Sight cone widths or idle turn cadence for crew.
• Hide duration expectations after a clear spotting (~1 minute remains the planning default until your build proves otherwise).
• Softlock enter / exit responsiveness under desks.

Re-test protocol: one Kitchen doorway scout, one intentional spot, one full hide wait, one clean exit. Theory: Stealth and Detection. Cover literacy: Vents and Cover. Threat profiles: Crew.

Change class B — nest economy and capture commits

Nest UI labels, checklist items, and conversion pacing can drift while the fantasy stays “bank colony progress between commits.” Capture / reproduce commits that feed the larva fantasy should be re-verified the same way — quiet window, cover assigned, abort ready. Docs: How to Nest, How to Capture.

Do not invent new nest rules from old 0.65 preview videos when the panel layout changed.

Change class C — INT / STR and skill labels

Skill names and node order are prime patch targets. INT-leaning control vs STR-leaning pressure can remain conceptually true while strings move.

Re-test protocol: open the skill screen, rewrite your plan in Skill Planner, and reconcile with Skill Tree / Early Build. If a guide mentions a label you cannot find, trust the live Demo screen.

Change class D — room routing, Doctor, and Security A / B

Kitchen, Clinic, Laboratory, Cafeteria, and Security Room should remain landmark names. Historically, Kitchen / Clinic / Lab additions and the Doctor event arrived across the mid-preview climb; approach denseness and Route A / B presentation can still shift after 1.0 hotfixes.

Re-test protocol:

• Kitchen comfort loop via Kitchen Route.
• Clinic / Doctor pacing via Doctor and Clinic Doctor Route.
• Security conceptual branches via Security Room and Security Routes.
• Boss readiness via How to Beat the Boss.

Map orientation: Atlas Overview, Key Rooms, Decks.

Change class E — UI, locale, input, and saves

EN/JP string fixes are normal. Binding prompts and stealth verb labels may be clarified without changing the larva loop. Some earlier builds drew community notes about save reliability — treat a bad resume as a build fact to verify, not as permission to chase unofficial clients. Official play path: Demo Access.

Re-test protocol: confirm menus readable → confirm move / hide / interact bindings on Keyboard Controls and Stealth Actions → confirm a short save / reload in a safe room before a long session. Hardware context: System Requirements.

What we will not do on this page

• Fabricate dated patch paragraphs we did not verify.
• Promise full-release roadmap items as Demo facts.
• Document adult scenes as changelog bullets.
• Link piracy mirrors or cracked clients.
• Claim every community rumor build number is official.

When official notes are detailed, prefer Steam’s text and use this page as a systems regression checklist. Broader dated spine: Version History. For Patreon milestone framing versus what your Steam build actually contains, see Dev Progress. For save-slot quirks before long sessions, see Save & Progress.

Suggested post-hotfix session (30–40 minutes)

1. Verify version string (expect Demo 1.0 / hotfix-era labeling unless Steam shows newer).
2. Softlock drill in a low-threat room.
3. Nest bank once; optional capture drill if that is your next goal.
4. Confirm skill screen labels.
5. Touch Clinic approach only if nest is healthy.
6. Stop before Security if anything fundamental broke — file notes, do not tilt into boss attempts.
7. Resume linear clear with Demo Walkthrough only after the drill passes.

Linking updates to reviews and audio

If a hotfix changes first-hour friction, update your personal take using Pros and Cons categories (detection tax, UI friction, nest gating). Longform context: Demo Review, Review Hub. Audio direction notes: Soundtrack.

Practical example: “my guide disagrees with my build”

1. Identify the disagreeing system (stealth / nest / skills / route / Doctor pacing).
2. Find the matching change class above.
3. Run the re-test protocol.
4. Adjust only that slice of your plan.
5. Keep How to Play as the loop spine even when labels move.

Bottom line

Changelog literacy for Alien Invasyndrome means expecting motion around a stable fantasy: larva stealth, desk softlocks, ~1 minute detection hides, nest growth, INT/STR spends, Atlas rooms, Doctor / Clinic pacing, Security A/B. The useful checkpoint in May 2026 is Demo 1.0 hotfix, reached after the 0.65 → 0.99 → 1.0 climb. Verify your Steam string, then play.