What public guides report
Community guides describe Clark as a stalking threat and connect survival advice with light, sound, movement, and line-of-sight awareness. This is useful player vocabulary but not an official stat sheet.
A cautious Clark entity page built around the strongest public community description and explicit gaps around behavior, counters, and spawn rules.
Use these notes while you play, then follow the related pages for codes, rankings, tools, or route-specific help.
Community guides describe Clark as a stalking threat and connect survival advice with light, sound, movement, and line-of-sight awareness. This is useful player vocabulary but not an official stat sheet.
No public source currently establishes exact spawn rules, health, damage, detection radius, guaranteed counter, or a fixed encounter script. Keep those details open until a stronger source appears.
Note the date, squad size, first visible or audible cue, whether line of sight was broken, what the group tried, and the outcome. A single encounter can support a dated behavior observation, but it cannot establish a damage number, detection radius, spawn probability, or universal counter.
Prepare the squad to communicate, observe the current build, and regroup. If the threat behaves differently, treat the observation as an update signal rather than forcing an old guide to fit. Compare the observation with the survival and update pages, and submit a correction only with enough context for another player to reproduce the situation.
Wiki pages should point players toward the practical pages that explain what to claim, compare, build, or check next.