Alan Wake – Episode 3: Ransom – With Behind The Scenes Level Look

We returned to Alan Wake for Episode 3, “Ransom,” with the plan to play through the full episode first and then go back in developer mode for another look behind the scenery. Before any of that could happen, though, the monitor PC decided not to cooperate, Twitch was throwing loading errors at me, and I spent the opening minutes staring at a lovely blank Chrome screen.

Once everything finally behaved, Bright Falls had plenty of its own problems waiting for us. This episode took us through a police manhunt, possessed machinery, a flying train that definitely was not supposed to fly, some extremely questionable cardio from Alan, and a ransom plot that turned out to be very different from what we had been led to believe.

🌲 About the Game

Alan Wake follows best-selling writer Alan Wake after his wife, Alice, disappears during their holiday in Bright Falls. While searching for her, Alan begins finding pages from a thriller he does not remember writing, and the events described on those pages start happening around him.

A Dark Presence is spreading through Bright Falls, taking control of people and objects while Alan tries to understand what is happening, recover the missing manuscript and find Alice. Light is one of his most important weapons, but the further we get into the story, the less straightforward the situation becomes.

🧭 Where We Are in the Journey

This stream took us through Episode 3, covering Act 1, “On The Run,” and Act 2, “Mirror Peak.” Alan believes Alice has been kidnapped, and the people claiming to have her are demanding the missing manuscript in exchange for her release.

We began with Alan and Barry following the trail to Rose, before the episode turned into a race to reach the supposed kidnappers. By the end we had reached Mirror Peak, discovered what was really going on with the ransom, and then gone back through both acts in developer mode to see how the levels were actually put together.

⚠️ What Happens in This Episode

The unease began at Rose’s trailer, where the difference between the woman Alan met earlier and the person now standing in front of him was immediately obvious. Rose’s usual enthusiasm had been replaced by a strange monotone, and the walls of her trailer were still covered in Alan Wake memorabilia, which made the whole encounter feel even less comfortable. She had the manuscript Alan was looking for, but nothing about the situation felt right. Alan and Barry were quickly caught in whatever had taken hold of her, and when Alan came around again, the mystery surrounding Barbara Jagger and the Dark Presence had only grown deeper.

A manuscript page made matters worse. Alan’s writing was apparently being “revised,” with Barbara exerting more influence over the story and pushing it further into horror. Alan was still trying to save Alice, but the boundaries between what he had written, what he remembered, and what was now happening around him were becoming increasingly difficult to separate.

There was little time to think about any of that. Alan had less than twelve hours to reach the kidnapper, and FBI agent Nightingale arrived with all the subtlety of a wrecking ball. Rather than lose his chance of finding Alice, Alan fled, beginning a long escape through police lines, forest paths, searchlights, and increasingly supernatural interference.

This also brought back one of Alan’s greatest enemies: cardio. Every short sprint seemed to end with him panting for breath, while I repeatedly tried to make him move faster and occasionally pressed the wrong control entirely. The “Happy Jump” returned as I continued mixing up jumping and running at exactly the sort of moments when Alan really could have done with concentrating on escaping.

Chat made sure the police chase never became too serious. Gary had already opened the night by asking when I was going to play “a good game,” which naturally sent us back into the ongoing SnowRunner debate. Apparently it is “mostly mud,” nobody likes it, and even the name is questionable. That argument never really went away, especially once the forest roads and industrial scenery began looking suspiciously like somewhere a truck could spend several hours stuck in a ditch.

There were a few practical problems mixed into the chaos as well. Chat noticed that the game audio was extremely quiet, with the slight complication that turning everything up too far risked my voice becoming considerably louder than anyone wanted. Somewhere between adjusting that, talking about Stargate, cars, daytime running lights, and all the usual stream diversions, Alan continued trying to avoid being shot by people who were technically supposed to be the good guys.

The escape eventually brought us to Pat Maine’s radio station. Alan was hoping Maine might be able to help him get to the coal mine, but any chance of having a calm conversation disappeared when Nightingale turned up again. Alan escaped once more and continued toward the meeting point, with the episode settling into a rhythm of darkness, generators, work lights, flashbangs, and sudden Taken attacks.

Several fights became a case of reaching the nearest safe light before Alan was overwhelmed. Ammunition was worth conserving, although my attempts to save it occasionally resulted in being surrounded and having to use something considerably more explosive anyway. A police helicopter also disappeared off into the distance during the chase, which immediately became something to investigate later once developer mode was available.

Not long after, a passing train proved far too tempting to leave alone. Rather than waiting until the end of the episode, we briefly stepped outside the intended camera to find out where it actually went. The answer was apparently nowhere particularly sensible. The train derailed, briefly appeared to fly through the world, and then waited for the surrounding textures to catch back up with what it was doing. It was exactly the sort of thing that makes looking behind the scenery worthwhile.

Back on the intended route, Alan received a call from Alice. It should have been reassuring, but even Alan knew something about her voice was wrong. She told him to be careful and cooperate, yet the call left more questions than answers. It was another moment where the game offered Alan a little bit of hope without giving him any real reason to trust it.

The supernatural side of Bright Falls continued getting more aggressive from there. Ordinary objects were no longer necessarily ordinary, which became particularly clear when a wheelbarrow managed to turn itself into a legitimate threat. We also stopped for another Night Springs episode, “Family Occasion,” where an unfortunate journalist discovered that researching local mythology can go badly when the mythology decides to take an interest in you instead.

Gary had perhaps the most practical solution to Alan’s problems at this point: stop writing horror books. The suggested alternative was “bouncy bouncy books,” which, to be fair, would probably involve considerably fewer possessed objects.

Unfortunately, Alan had already written enough horror to provide us with a large piece of industrial equipment. I remembered there being either a tractor or digger somewhere in this section, and it did not take long for the game to confirm that memory. The possessed digger fight became one of the messier encounters of the night, with Taken attacking at the same time, limited space to work with, and Alan ending up with almost no health. There was a desperate retreat toward the light, a lot of scrambling for the right equipment, and eventually the digger went down without sending us into the repeat attempt that seemed increasingly likely.

Around this point we also welcomed a raid from asmith501, who arrived bringing what they described as “troublemakers.” Chat continued to operate as its own separate layer of the stream, with community games, Rock Paper Scissors Lizard Spock, Bouncy/Marry/Kill results, conversations wandering everywhere from cars to games, and the occasional reminder that trying to follow the plot while reading Twitch chat is its own difficulty setting.

The tone shifted briefly when chat joined and mentioned that they had been dealing with funeral planning after unexpectedly losing their mum. The usual nonsense stopped long enough for everyone to offer support before the conversation gradually returned to normal. That mix of chaos, conversation, and people simply being there for one another remained part of the stream throughout the night.

By sunrise, Alan finally reached the Bright Falls coal mine, now operating as a museum, with only a few hours left before the promised meeting. After everything required to get there, the kidnapper simply failed to appear. Alan waited while imagining increasingly grim possibilities for Alice, until another call finally redirected him toward Mirror Peak.

That moved us properly into Act 2, and the journey became harsher almost immediately. Darkness returned, Alan’s car took enough punishment that travelling on foot became necessary, and supplies became increasingly important. Flashbangs were precious, ammunition was disappearing, and at one point we reached safety with what looked like little more than a pixel of health remaining.

EntertainJD chose an excellent moment to activate the “Death Loop” joke, complete with the idea of being trapped in the same section over and over again. Considering how close several encounters came to putting us back at the previous checkpoint, it was difficult to argue with the timing.

The route toward Mirror Peak took Alan through more industrial areas, mine workings, scaffolding, bridges, and cramped spaces where groups of Taken were far harder to avoid. The episode kept shifting between combat and quieter discoveries, including manuscript pages that added more to the story of Thomas Zane and Cauldron Lake. The idea that the lake might be more than a lake at all — something closer to a doorway into a much larger darkness — made Alan’s situation feel increasingly less like a simple kidnapping and more like being trapped inside a story with rules he still did not understand.

The machinery was not finished with us either. A possessed locomotive turned the railway into another weapon, continuing the episode’s apparent belief that anything remotely industrial should eventually try to kill Alan. The climb toward Mirror Peak became increasingly desperate, while chat supplied equally helpful instructions ranging from “Run Alan!” to effectively telling him to stop again moments later.

Then the entire ransom plot fell apart.

Alan finally reached the man he had spent the episode chasing, only to discover that the supposed kidnappers did not actually have Alice. They did not know where she was. Alan had crossed forests, escaped the FBI, fought through Taken, survived possessed machinery, climbed through the mine, and risked everything to reach a ransom exchange that had been built on a lie.

The revelation completely changed what Alan thought he understood about Alice’s disappearance. The episode ended soon afterwards, and as the credits began I quickly muted the copyrighted music before we moved any further into the next part of the story. We briefly saw Alan with Hartman, but deliberately stopped there. Episode 3 was finished, and it was time to go back through it again from somewhere the game never intended us to stand.

Developer mode turned the second half of the stream into a proper behind-the-scenes tour. We returned first to Act 1 and pulled the camera away from Alan to examine Rose’s trailer and the surrounding area. Without the normal restrictions, we could get much closer to the decorations inside, including the magazine cut-outs above Rose’s bed, objects on the shelves, and all the little props that are easy to miss during the actual scene. Rose herself was already positioned in the level waiting for the cutscene to trigger.

The neighbouring buildings were equally interesting for completely different reasons. Some were little more than empty shells because the player was never supposed to get inside them, while areas that had seemed much larger during the nighttime chase were revealed to be tightly arranged around one another. Roads doubled back, encounter spaces sat surprisingly close together, and the darkness had done an enormous amount of work convincing us that the journey covered far more ground than it actually did.

Act 2 gave us even more to investigate. From above, we could trace the coal-mine museum, rail yard, combat arenas, tunnels, crane, lake, railway, and the route Alan had taken toward Mirror Peak. Some distant objects disappeared when viewed from places the game never expected the player to reach, while other pieces of scenery were far more physical than expected. The crane ropes, for example, were actual solid geometry stretching through the environment rather than simply a visual detail hanging in the background.

Seeing the levels in daylight and from above made Remedy’s design much easier to appreciate. Darkness, restricted sightlines, trees, cliffs, buildings, and carefully folded pathways made Bright Falls feel enormous during normal gameplay, while developer mode revealed just how deliberately everything had been fitted together behind the scenes.

By the time we finished exploring, Episode 3 had taken us from Rose’s unsettling trailer through a police manhunt, supernatural forests, radio stations, industrial machinery, the coal mine, Mirror Peak, and finally the collapse of the ransom story itself. We stopped there rather than beginning the next chapter properly, leaving Hartman and whatever comes after the Mirror Peak revelation for the next session.

And after nearly three hours of Taken, possessed machinery, developer-mode discoveries, raids, community chaos, and repeated accusations that Alan Wake was becoming SnowRunner, we finished by raiding into IThinkImAPenguin8P and carrying the evening onward.

🎥 Watch the Episode

If you want to see the full run through Episode 3 along with the developer-mode exploration afterwards, you can watch the complete episode on YouTube.

You can continue through the series with the Alan Wake playlist, and if you enjoy the videos, feel free to like, comment and subscribe over on my YouTube channel.

🔦 Join the Adventure Live

Watching the finished episode is one thing. Being there while the monitor refuses to cooperate, chat debates SnowRunner, a train unexpectedly flies off into the scenery and Alan nearly runs out of health is something slightly different.

You can join us live on Twitch or YouTube. We had asmith501 and their troublemakers raid into this stream, and nights like this are always better when chat is there helping, distracting me or providing completely conflicting instructions.

🕯️ Community & Links

There is plenty happening outside Bright Falls as well. If you want to keep up with the streams, videos, community and everything else I am working on, you can find it all here.

Live — Come along for the next stream and see what goes wrong in real time:
Twitch | YouTube

Community — Join the conversation between streams and become part of the community:
Discord

Socials — Follow along for updates, clips and whatever else escapes from the stream:
TikTok | Bluesky | Instagram | Facebook | Threads | X

Music — If you want something to listen to while staying safely away from Cauldron Lake:
Spotify | Apple Music

Support — If you would like to help support the channel and future streams:
Fourthwall | Teespring | Streamlabs

More — For my other projects, services and work away from the stream:
Business Centre | Download the Brochure | About Me | Blog

🚂 The Train Flew, but the Ransom Fell Apart

Episode 3 gave us a lot more than the meeting Alan expected. We finally reached Mirror Peak only to discover the kidnapping story was not what we thought, while the developer-mode tour afterwards showed just how much was hiding beyond the normal camera.

Next time we can find out what Hartman has to do with all of this. Until then, I am still not entirely convinced that train was ever meant to stay on the tracks.

— Dr Ravenholm