What a Static Photo Actually Means
ALERT LEVEL: WARNING
Immediate Command Summary
- [COMMAND]: A static photo by itself is not an auto-reject anymore.
- [COMMAND]: As of the June 22 note on the anomaly page, shooting a patient with no other signs can make them faint, indicating they were a real patient.
- [COMMAND]: Treat static as a tie-breaker only when another face or CCTV clue also looks wrong.
1. Why This Confuses Everyone
Static used to read like a simple red flag, but the current anomaly documentation explicitly warns that a static photo can appear without another visible feature and may still belong to a patient. That is exactly why players feel they are making the right call and still getting punished.
2. The Better Decision Rule
Do not shutter purely on static. If the face, ears, mouth, or camera feed also fail, reject; if static is the only problem, keep checking instead of guessing.
Run this before you commit
- Let the photo finish processing before picking it up.
- Compare the photo against the patient face and body at the desk.
- Open CCTV if the photo is static but the desk view looks clean.
- Reject only when another channel also points to an anomaly.
- Keep checking if static is the only issue and the patient has no other bad sign.
What throws the run
- Treating every static photo as an automatic shutter call.
- Ignoring the face and CCTV channels after seeing a bad photo.
- Picking up a photo during processing and creating an avoidable sanity hit.
- Letting one old static-photo habit override the current intake loop.
Fast answers for this route
Is a static photo always an anomaly?
No. Use static as a warning sign, then confirm with the face, body, and CCTV reads before you shutter.
What is the safest static-photo decision rule?
Reject when static comes with another failed channel. Keep checking when static is the only strange signal.
Can the photo itself cost sanity?
Yes. The safer desk routine is to wait until the photo finishes developing before you pick it up.