EyeAI Scanning Guide
Quick answer
EyeAI scanning currently has three confirmed target categories: Creatures, Slime, and Portals. This page should list exact targets, scan timing, rewards, danger, and tips as they are verified.
Confirmed Scan Targets
| Target | Current role | Fields to verify |
|---|---|---|
| Creatures | Paranormal entities tied to the investigation loop | Name, spawn area, scan distance, danger, counterplay |
| Slime | Environmental or creature-linked evidence | Location, whether it moves, scan reward, risk |
| Portals | Paranormal entry or event target | Trigger, scan window, reward, escape route |
How To Approach Scanning
- Identify the target category before committing the whole team.
- Call the target, location, and current danger.
- Finish the scan only if viewer pressure and creature risk allow it.
- Record failed scans separately from completed scans.
Scan Log Template
| Target name | Category | Where found | Scan time | Reward | Danger | Tip |
|---|---|---|---|---|---|---|
| TBD | Creature / Slime / Portal | TBD | TBD | TBD | TBD | TBD |
What Not To Guess Yet
- Exact scan duration.
- Creature names.
- Reward values.
- Whether Slime and Portals behave the same across nights.
- Whether character abilities change scan safety.
Next Update
As soon as named Creatures are visible, create or expand a dedicated Creatures section and link each creature back to the EyeAI scan table.
Scan Evidence Workflow
The strongest version of this page will be built from repeated scan attempts. For every target, capture a screenshot if possible, write the target name exactly as shown, then record whether the scan completes, fails, or is interrupted. A failed scan is still useful evidence if the note says what broke it: distance, line of sight, enemy pressure, teammate movement, timer pressure, or a donation request.
Do not combine Creatures, Slime, and Portals into one generic row. They may share the EyeAI system, but players will search them differently. A named Creature can become a creature guide. A Portal may become an event or escape-route guide. Slime may become an evidence or hazard guide depending on how the game uses it.
Evidence Links
| Source | Use it for |
|---|---|
| Steam store | Official EyeAI, Creature, Slime, and Portal wording |
| Steam Community | Screenshots, player scan discoveries, bug reports |
Scan FAQ
What should I scan first? Start with the target that is easiest to identify safely. Before exact routes are known, survival and repeatable evidence matter more than speed.
Are Creatures, Slime, and Portals the same kind of objective? They are confirmed scan targets, but their behavior should be tested separately after unlock.
When should the team stop scanning? Stop when the risk of losing the run is higher than the value of the scan. Record the reason, because that reason may become a useful strategy note later.
Scan Failure Modes
- Calling a target "creature" without recording its exact in-game name.
- Publishing scan rewards from one attempt without testing whether night, player count, or modifiers changed the value.
- Failing to separate interrupted scans from scans that completed but gave no visible reward.
- Ignoring viewer rank pressure while testing EyeAI routes.
Current Decision Rule
Update the table only when a scan result can be repeated or clearly observed. One screenshot proves that a target exists; it does not prove the scan time, reward, or best route. Keep existence, behavior, and strategy as separate fields so early evidence can improve without forcing a full rewrite.