After two or more consecutive locker teleports outside of Night, The Dredge's client displays the Undetectable status effect (no terror radius, no red stain on the killer's own screen). However, the server does NOT register this status. As a result: - Survivors can still see The Dredge's aura (e.g., through Deerstalker) and hear the terror radius. - The Dredge does NOT receive the corresponding aura-reading feedback from perks like Deerstalker (which normally reveals the aura of a Survivor who can see the Killer's aura), because the server correctly knows the Killer is NOT Undetectable. This creates a one-sided informational disadvantage for the Killer and a gameplay-affecting bug. It occurs even with no perks or add-ons equipped, and the effect can last for a random duration or be manually cancelled by teleporting to the Remnant, hooking a Survivor, or breaking a pallet.

If the server does not register The Dredge as Undetectable, the client should also not display the Undetectable status effect. Aura-reading perks should work symmetrically: either both sides see each other's auras (if neither is Undetectable), or neither does (if the Killer is truly Undetectable). The reciprocal effect of Deerstalker should always be consistent with the actual game state.

Major

Always

Steam

- The bug was reproduced with a completely empty loadout (no perks, no add-ons), confirming it is not tied to any specific item. - Confirmed with another player in the same match — the Undetectable status is only visible on the killer's own screen. Survivors see and hear the killer normally (terror radius and red stain are present). - However, the bug is NOT purely visual: it also breaks the functionality of aura-reading perks like Deerstalker. The Survivor can see the Killer's aura (triggering the perk), but the Killer does not see the Survivor's aura in return, because the server correctly knows the Killer is not Undetectable. - This indicates a client-server desync issue where the client incorrectly believes it is Undetectable, while the server knows the truth. - No existing reports of this exact issue were found on official forums or Reddit, suggesting it may be a new bug introduced in recent patches (possibly 9.6.x or 10.0.2). - I can provide a video or screenshots upon request – please let me know if they are needed.