Evidence boundary: Official sources establish the Shape Jump darkness and line-of-sight rule and named patch changes. The state table and timing observations below come from a community guide; Kingy has not reproduced them on 1.0.2.

When a room goes dark, treat it as a state problem first. Identify what changed, what the prompt still allows, and whether the effect is local or temporary before spending a Repair Kit.

Shape Jump checks

Officially verified: IllFonic’s multiplayer overview says Michael’s Shape Jump transition depends on darkness or being outside a Civilian’s line of sight. If a transition fails, check both conditions before assuming a cooldown or range limit.

Darkness is a condition, not proof that every nearby power source is disabled. Re-check the room, the approach angle, and the Civilian’s view at the transition point.

Classify the power state

The following is a working community model. It is useful for deciding what to test, not a published device map.

StateWhat may changeFirst responseConfidence
Room switchLocal illuminationToggle it, then retry the interactionCommunity report; wider effects not established
Power box switched offConnected building lightsRestore the state and re-check the roomCommunity report; exact dependency not established
Destroyed power boxPersistent connected-system damage; a CB radio may also stop workingUse a Repair Kit when the prompt is availableCommunity report; repair timing unconfirmed
BlackoutTemporary nearby power suppression; nearby cars or bikes may be disabledWait or reposition before repairingCommunity report; radius and timer unconfirmed
Active lightCan expose or interfere with Michael but does not restore room powerUse the beam deliberately and keep movingOfficial patch change plus community observation

Blackout: wait before repairing

Community lead — needs confirmation: Gamers.Wiki’s lighting and blackout guide reports a private-lobby observation of roughly 15 seconds for one Blackout effect and an observed cooldown of about 1:30. That is a single test context, not a universal timer.

Use the report as a decision sequence:

  1. If the effect is recent and nearby devices are affected, wait through the temporary state.
  2. Re-check the car or bike after the lights return. A vehicle that remains unavailable may be separately damaged.
  3. Repair only a persistent, confirmed interaction problem and record the patch, platform, map, and prompt.

Read active light and HUD cues

Flashlights, the Brass Lantern, and Road Flare are active-light examples in the community report. Phone colors and exact green, yellow, and red thresholds are also community observations; use them as cues, not measurements.

Patch 1.0.2 officially changed Chapter 5 challenge tracking so flashlights no longer need to be fully drained. That fixes a challenge condition; it does not publish a universal beam range, battery rule, or Blackout radius. If a prompt is missing, reposition and retry before treating it as a hidden value.

A short decision sequence

  1. Identify the scope: one room, a connected building, or nearby devices.
  2. Ask whether the state is temporary. If yes, wait and re-check before repairing.
  3. If the state persists and the game presents a repair prompt, use the Repair Kit record and log the result.
  4. For Shape Jump, check darkness and Civilian line of sight at the transition point.
  5. If the result repeats, record the build, platform, map, device, prompt, and elapsed time for a useful correction.

What is still unconfirmed

  • Blackout radius, duration, and cooldown across maps and platforms
  • Which lights, cars, bikes, radios, and rooms share a power dependency
  • Repair time, consumed quantity, and whether a temporary state can be repaired
  • Flashlight range, beam angle, battery behavior, and detection thresholds
  • Whether the released 1.0.2 behavior matches the pre-release Shape Jump explanation

For Michael’s broader tool choices, read Playing Michael Myers. For dated changes, use the Patch Index.