Japan Stigmatized Property 3 Anomalies Hub

What counts as an anomaly

In Japan Stigmatized Property 3, anomalies are randomized irregularities on surveillance feeds across the four properties: Sugiya Ryokan, Blue House, Kannonzaki Park, and Y Residence. Official examples include furniture movement, objects appearing or disappearing, human or spiritual intrusions, lighting malfunctions, floating orbs, bloodstains, and video noise—plus stranger events that still read as not Normal once you know the room.

Your job for the Japan Stigmatized Property Association is not to admire them. It is to detect them between 00:00 and 05:00, report them with mouse hold-click, and avoid inventing them when the feed is clean.

How to use this hub

Start with Anomaly Types to build a recognition vocabulary across object, entity, lighting, stain, and signal-noise categories—including the critical split between standard-only and night-vision-only spawns.

Read Vision-Mode Anomalies when you keep dying because you married one camera filter. Store text is explicit: some events appear only on the standard feed, others only under night vision.

Read Dangerous Anomalies next if your runs end because something lingered after knocks or moans. Dangerous threats are the interrupt class: they override tidy camera tours.

Study False Reports when your mission failures show the Association rejecting your paperwork. Normal allows five false reports; Hazard Pay (特別手当) allows three. Many “I got jumpscared” losses are actually false-budget losses. Pair that with Mission Failure Rules so both pink-slip meters stay visible.

Fail math you must not argue with

Two mission-failure conditions dominate anomaly work:

1. Four concurrent unreported anomalies — the stack fail.
2. Too many false reports — five on Normal, three on Hazard Pay.

A third practical fail condition sits beside them: dangerous anomalies left too long after audio warning. Treat that as priority zero even when your concurrent count looks safe.

For the mechanical how of reporting and vision toggles, jump to the Guides Hub, especially How to Report Anomalies and Night Vision Guide.

Co-op anomaly handling

Online co-op (2 players, PC↔mobile cross-play) adds thermal confirmation. Use it to resolve disputed entity or heat-like reads, not to outsource basic two-pass vision checks. Partners should share a living list of active anomalies so nobody lets the concurrent count silently reach four.

Properties and expectations

Do not import first-game property names. JSP3’s stigmatized sites are the four listed above. Outdoor park cameras and dense indoor cameras produce different false-positive profiles, but the anomaly rules and fail meters stay universal.

Research loop after each night

After a clear or a fail, name three anomalies you handled well and one you misread. Look those classes up in the child pages. JSP3’s randomization means rote spawn timers will betray you; pattern libraries will not.

This hub is the catalog index. The child pages are the drawers. Open them before Hazard Pay, before achievement grinding across all 32 Steam unlocks, and before you blame the game for a report you filed on a Normal chair.