Urgent.News

What's breaking now, across thousands of outlets.

Tech

This brutal Fallout 4 horror mod turns the Commonwealth into Silent Hill

Introduce Pyramid Head and friends to the Boston suburbs in Whispering Hills.

This brutal Fallout 4 horror mod turns the Commonwealth into Silent Hill

The Fallout 4 map, typically known for its stark and dangerous environments, found a new level of dread with the horror mod Whispering Hills. This mod, reminiscent of the Silent Hill series, transformed the entire region into a haunting and mysterious landscape. The fog and rain reduced visibility to short distances, making the world feel more oppressive and eerie.

The player starts their journey in the same manner as the original game, with the unsettling task of rescuing their son, Shaun, who has been abducted by a cult. The town of Whispering Hills, modeled after Centralia, Pennsylvania, is a pivotal location, providing a fitting backdrop for a Silent Hill-inspired experience.

Upon arrival, the player faces a new set of enemies, including Sirenhead, a towering figure that broadcasts distressed child cries to attract them. The enemies are tougher than usual, with some capable of dealing significant damage in just a few hits. VATS is disabled, adding to the challenge as players are given only rudimentary gear to navigate the treacherous environment.

The mod's approach to stealth and running becomes essential, with themes of parenthood woven throughout. The lighting and sound design are particularly effective in creating an unsettling atmosphere, with grotesque imagery and eerie radio broadcasts. The mod's climax sees Pyramid Head, a formidable enemy, pursuing the player even outside the modded areas, adding to the game's overall sense of dread.

Written by urgent.news from PC Gamer's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at pcgamer.com →

More in Tech

Always Set persist-credentials: false in actions/checkout

There's a default in actions/checkout\ that most teams never change — and that quietly leaves a GitHub token sitting in a readable file for every subsequent step in the job. The fix is one line.

  • Set persist-credentials to false in actions/checkout
  • Default action writes git credential config file
  • Deleting file after checkout prevents security risk

More from Friday 30 October →