Alien Invasyndrome Bugs and Known Issues

What this page tracks

Alien Invasyndrome is a public Steam Demo (app 4603980, Demo package 4830300, store date 24 July 2026) at the Demo 1.0 hotfix (May 5, 2026) content checkpoint as of the 24 August 2026 wiki re-check. Bugs and known issues change between builds. This page tracks classes of issues players have reported, plus how to verify and how to report. It is not a live defect tracker — Steam Community discussions are.

Developer Mozu Field / 百舌鳥, publisher Shady Corner Games. Adult 18+; tone stays mechanical. Hub: Updates Hub. Siblings: Changelog, Version History, Steam Status, Demo Access.

How to use this page

1. Match your symptom to one of the categories below.
2. Run the re-test protocol for that category before assuming the bug is real.
3. Confirm your build via Steam → Library → Demo → Properties → Updates.
4. Report reproducible issues with a build string, room name, and reproduction steps.
5. Avoid third-party “fixes” that promise easy patching — most are malware.

If a class disappears from this page after a Steam patch, the patch likely fixed it. Changelog is the canonical “what changed” record.

Class A — Softlocks and detection minute confusion

What it looks like

• You got spotted, hid under a desk, waited ~30 seconds, came out, and immediately got spotted again — feels like the hide minute never ended.
• You hide, the UI freezes, and you cannot exit hide.

What is usually happening

• The ~1 minute detection tax was longer than expected on this build.
• A second spotting stacked the timer.
• A real softlock under the desk.

Re-test protocol

1. Fresh Kitchen doorway scout with one intentional spot.
2. Hide under a desk; run Detection Timer for the full ~60 seconds.
3. Exit only after the timer ends.
4. If exit is still blocked, this is a real stuck state — see Softlock Fixes.

Pages: Stealth and Detection, Softlock Fixes, Detection Timer.

Class B — Save resume and reliability

What it looks like

• Resume loads an older nest state.
• Skill points roll back after a long Security attempt.
• Save file appears in userdata but Demo shows “no save found” on launch.

What is usually happening

• A flaky Steam Cloud reconciliation.
• A build that wrote the save but did not flush before crash.
• An old save slot from a prior Demo build that is incompatible with the current version.

Re-test protocol

1. Close Steam completely (Steam → Exit).
2. Reopen Steam; let Cloud sync reconcile.
3. Toggle Steam Cloud off → on for the Demo.
4. Try a fresh slot if a suspect slot keeps rolling back.
5. Back up the 4830300 folder under %SteamInstall%\userdata\<your_steam_id>\ before long attempts.

Pages: Save & Progress, Save File Location.

Class C — Locale rendering (Japanese UI)

What it looks like

• Tiny or missing Japanese glyphs on non-JP Windows.
• Garbled menu text on first launch.

What is usually happening

• Older Demo builds boot Japanese by default and rely on Windows fonts that may not be installed.
• Steam language preference not honored on first launch.

Re-test protocol

1. Confirm Steam language preference is set to your expected language.
2. Install / configure Locale Emulator for non-JP Windows.
3. Re-launch the Demo.

Pages: Locale Emulator.

Class D — Performance hitches and frame pacing

What it looks like

• Capture commits hitch for 30–80 ms.
• Detection hide stutters feel longer than they are.
• Kitchen doorway feels “slow” on every attempt.

What is usually happening

• Recording overlay (OBS, NVIDIA ShadowPlay, Discord Game Activity, Steam overlay).
• Outdated GPU drivers mishandling OpenGL 4.1.
• Background apps eating RAM.

Re-test protocol

1. Close overlays; close browsers; close RGB software.
2. Re-run the same corridor on the same binds.
3. Update GPU drivers via vendor clean-install.
4. Switch the Demo to a High Performance power plan on laptops.
5. Lower render resolution / disable anti-aliasing.

Pages: Performance & Settings, System Requirements.

Class E — Skill labels and tree inconsistencies

What it looks like

• A guide mentions a skill label that does not exist on your Demo.
• Your skill tree shows different nodes than a video.
• Your INT/STR reflects a different progression than expected.

What is usually happening

• The Demo’s labels shifted between patches; old footage is outdated.
• Your build string is older than the wiki assumes.

Re-test protocol

1. Open Skill Planner and rewrite your plan based on your live labels.
2. Cross-check with Skill Tree — but trust the live Demo over the wiki.
3. If a label is missing on your build, file it as a likely drift issue, not a “broken Demo.”

Pages: Skill Tree, Early Build, INT vs STR.

Class F — Doctor / Clinic event pacing

What it looks like

• The Doctor encounter feels “stuck” — you cannot trigger or exit the beat.
• Doctor pacing interrupts detection hide in unexpected ways.

What is usually happening

• Nest income was thin; the Doctor event is gating your progression.
• A detection during the Doctor beat stacked the timer.

Re-test protocol

1. Confirm nest is healthy before approaching Clinic.
2. Approach with a clean detection state — not mid-detection.
3. If the event still blocks, treat as a real stuck state and consult Softlock Fixes.

Pages: Clinic Doctor Route, Doctor.

Class G — Security Room and Route A / B presentation

What it looks like

• Route A or Route B does not appear where a guide expects.
• Security personnel behave differently than the wiki describes.

What is usually happening

• Patch-level changes to approach density or personnel patrol.
• Skill plan that does not match the route’s expectations.

Re-test protocol

1. Re-check the Security Room and Security Routes pages on your build.
2. Cross-check the personnel on Security.
3. If the route’s pressure feels different, re-test your skill plan.

Pages: Security Room, Security Routes, Security.

Class H — Crash on launch or mid-session

What it looks like

• Demo does not launch at all.
• Demo crashes after a long Security attempt.

What is usually happening

• Windows locale blocker (JP).
• Insufficient disk or GPU.
• Save corruption after a long resume cycle.

Re-test protocol

1. Verify System Requirements.
2. Confirm file integrity via Steam (Library → Demo → Properties → Local Files → Verify integrity).
3. Disable overlays.
4. Try a fresh save slot.
5. If a crash is reproducible on the latest Demo, file a developer report.

How to report a reproducible bug

When you can reproduce the bug on a clean install with the latest Steam Demo:

1. Note your Steam build string.
2. Note the room (Kitchen / Clinic / Laboratory / Cafeteria / Security / Boss).
3. Note whether you were in detection-hide, mid-softlock, or normal play.
4. Note your skill plan summary (INT/STR focus).
5. Reproduce once and capture the steps.
6. File via Steam Community discussions for app 4603980 or via Mozu Field’s Patreon bug-form.

We will not host bug reports on this wiki. Steam and the developer’s own channels are the supported path.

What this page will not do

• Promise an “easy fix” for any bug class. Steam patches are the only honest fix.
• Link unofficial patchers, trainers, or save editors.
• Document how to bypass Steam’s anti-cheat.
• Promote rumor builds or repacks as “fixed versions.”

Re-test checklist before assuming a bug

Run this list once before filing a report:

• Steam build string noted.
• Library → Properties → Local Files → Verify integrity passed.
• Recording overlays disabled.
• Steam Cloud toggled off → on.
• Detection minute waited out in full (use timer).
• Locale Emulator configured for JP issues.
• Skill screen matches Skill Tree on your build.
• System Requirements cleared.

If all eight pass and the bug reproduces, file a developer report.

Related pages

• Updates Hub
• Changelog
• Version History
• Demo Access
• Steam Status
• Save & Progress
• Save File Location
• Softlock Fixes
• Performance & Settings
• Locale Emulator

Bottom line

The Demo’s known issues cluster around softlock-vs-detection confusion, save reliability, JP locale rendering, performance hitches, label drift, Doctor/Security pacing, and launch crashes. Most “bugs” are environmental (overlay, driver, locale) — re-test once with overlays off before assuming a content regression. For real regressions, file a developer report with your build string.