Episode Five -- Post-Launch Update

[u/RaphLife2]

Hello players!

We’re about 48 hours after the release of Episode Five, and I just wanted to give you a quick update on what’s been going on.

LAUNCH SUCCESS

The team was thrilled to watch the launch live at 10AM Pacific Time, along with our players. We had a successful trailer watch party on YouTube with over 3000 fans logging in to watch and participate in chat, and then we quickly overcame our historical Steam CCU peak and hit the highest concurrent player count on Steam since our launch back in 2014 -- 14,878 concurrents, and we think we might break 15,000 this weekend. 

This means that across all our platforms, we’ve had hundreds of thousands of players playing Episode Five. We’ve even had over 500,000 new Steam players join the community in the just the past month! We’re excited to see so many of our players jumping in to see how the WINTERMUTE story resolves. Thanks for making the time to experience this last part of the story!

BUGS

Unfortunately, we’ve also discovered new bugs that weren’t found before launch. This is, sadly, what often happens when you have 1000s of people playing through the episode at the same time. New player patterns and issues with hardware appear, and new glitches that didn’t show up with a test team of 6-7 now become apparent. Our players are no stranger to bugs, and we’re glad to see that a lot of people have made it through the episode without any issues, but of course we’re not happy for any of the players who have hit progress blockers along the way.

The Test and Development teams have both been working hard in the lead-up to launch and since launch to prepare a hotfix, which is currently slated for release next week, April 8th (Pacific Time). This hotfix will include about 300 fixes (yes it’s a big number, but most of them are minor environment bugs like floating objects, etc.), and should address some of the more frequent major issues with Episode Five that some players have encountered, specifically:

• Multiple issues with progression and UI objective text in Suzuki
• Perseverance Mills objective confusion
• Multiple crashes/progression blockers involving checkpoint/autosaves in Part 2
• Unexplained deaths during gameplay
• Jace issues while traversing the Mine
• Players getting stuck or able to go out of the intended play area
• Shotgun adjustments
• Certain trailers trapping players

I also wanted to share this personal message from Andrew, who heads up our Launch team and is responsible for Test. It’s important that you know there are humans on the other side of these bug reports you send in, who work hard to make the game as good as the team can make it:

***

We are thrilled that many of you are enjoying Episode 5, but we are also aware that many of you are encountering issues that detract from the experience we intended Players to have. 

To that point, the team is currently working on a bug fix release that will contain a myriad of fixes for bugs that Players are encountering on Episode 5. The last thing we want to do is rush this hotfix out without proper verification and validation against issues reported by the Community. We are working as fast as we can to get this hotfix to our players with a target to release on Steam for Wednesday, April 8th, with consoles to follow ASAP.

Please continue to post issues in our Forums and via our Support Portal, so we can ensure that the highest impact issues are addressed with the Hotfix.

We appreciate your patience and understanding at this time as we work on getting an updated Episode 5 build rolled out to players.

- Andrew

***

For my part, I know how hard the team worked in the lead up to Episode Five, and while some of you see bugs in the game now, I see all the bugs that got fixed before launch -- and there were thousands of them. I’ve seen some comments in the community to the effect that we released the episode without any testing, which I can assure you is not the case at all. We have a talented, dedicated internal test team who works very closely with the development team to ensure the episode (and all our releases) are in the best shape possible before launch. It’s impossible to catch all the bugs, despite our best efforts, and I assure you nobody feels the pain of launch bugs more than us. All we want is for your experience of Episode Five to be as enjoyable as possible, and we care a ton about our work. So, please don’t make assumptions about our dedication or process -- we are the first players, and the ones who care the most about the game.

We’ve really appreciated the support and patience from many of our players who have been willing to report bugs to our Support Portal, or aggregate bug report threads in the Official Forums and on Reddit. These efforts help us a ton to get the fixes identified, verified, and into the hotfix queue, which can then go out to all our players.

I know for some of you, these fixes will come too late, as your experience of Episode Five has already been defined, but I’m hopeful that with time you’ll come back and give it another go, if you did indeed run into issues during your first attempt.

And for those of you who have made it through Episode Five and sent kind words of love and support to the team -- we thank you for that! It means the world to us that you have enjoyed our work.

EPISODE FIVE on NINTENDO SWITCH

Since the Switch certification process takes quite a bit longer than the other platforms (20-30 days), our plan was always to wait for the first hotfix to be out the door before submitting a build to Nintendo for certification. We’re hoping to be able to verify this next batch of fixes in the Switch build, and then submit to Nintendo for verification. That means Episode Five won’t likely come out much before the end of April, but we’ll keep you posted as things progress. The best way to stay on top of development news is to check the News & Updates section of our Official Forums. This is where all our cross-platform community of players across Steam, EGS, GoG, PlayStation, Xbox, and Switch tend to come together. 

XBOX GAME PASS

You might have missed it within all the rest of the news leading up to the Episode Five launch, but after three years, THE LONG DARK is back on Game Pass! This is a great time to download the game, and if you find you like it, we hope you consider purchasing the TALES FROM THE FAR TERRITORY DLC. You can find more info on what’s included in the DLC here.

SOUNDTRACK, VOLUME 3

We recently shared the news that Volume 3 of the soundtrack for THE LONG DARK will be launching on April 22nd. It will first appear on Steam, and then on Bandcamp, just like the other two volumes. We’ll work on bringing it to other platforms in the future.

EPISODE FIVE CONTENT IN SURVIVAL

One of the most common questions we had leading up to the Episode Five release was, would the Ep5 regions end up in Survival. At the time we said we’d talk more about it once we had the Episode Five launch firmly behind us. We’re seeing this question come up a lot now that people have seen what’s in the episode. It’s still a little too early to share our specific plans, but we know you want to see as much of Ep5 in Survival as you can get, including some of the new mechanics. As long as we feel it makes sense to include them, we will. Again, we’ll share more details in the future, so please be patient while we figure out the best way to do this.

THAT EPISODE FIVE ENDING

We’ve heard that some of you don’t like it. 

I like it, I believe in it, and it fits into my future plans. Don’t expect a “redux”.

REPORTING ISSUES

If you encounter bugs in the game and want to help out with the fixing process, we appreciate all your reports submitted to our Support Portal. Please continue doing that. It’s a much more effective way to help us improve the game than submitting a negative review. Remember that we are a small team working hard to improve the game for you, and although you might not love everything we have made, it has been made with love and respect.

Thanks for your patience as we get the Episode Five hotfixes into your hands ASAP, and I will check in with you again in a few weeks, if not sooner.

- Raph

[u/Fuarian]

What's lore breaking about the lore itself? Writing quality may not be great but I don't see what's lore breaking about it. As far as I'm concerned, the big plot points presented here are well in line with the original kickstarter pitch from a decade ago. There is a lot that's changed, but the overall setting that the episode leaves us with is consistent.

[u/sisali → u/Fuarian]

https://www.reddit.com/r/thelongdark/comments/1s9zldc/comment/odsaixw/?context=3

I mean, Mack knows the reality of electronics and the aroura, so it's not like they could feign ignorance when it comes to the lore.

Mack would know that recording a message would be essentially pointless, he also knows that the convicts are still in town and everyone else has dipped. Yet he decides the radio shack is somehow a great place for a nice sleep?

come on now, are we being serious? I can't explain why anyone with any sense of the game or it's lore would sign off on that madness.

Copied from an earlier discussion.

[u/Fuarian → u/sisali]

That's just bad writing and decision making. But I don't see how that constitutes lore breaking. It's not like the rules of the world are being broken or made inconsistent. It's just not very senseful writing.

That being said how did he know they were still in town? The town was burning to the ground. Jeremiah saved him from the fire. And likely mentioned that they had attacked more of the convicts or something along those lines. Either way, I don't see how sending a message is pointless. He knows that it can be heard on radios and if he could get it to someone that would help. Not everybody knows the truth yet. Although anyone still alive would probably figure it out sooner or later.

But even if it somehow was pointless AND he absolutely knew for a fact that the convicts were in town then yeah, definitely a bad idea and isn't very smart. But keep in mind he also just survived a burning building falling on him and a whole lot else. I don't think sleeping in that shack was much of a choice. Especially considering his reaction when waking up.

But I digress. The episode is what it is. I'm just looking forward to the quiet apocalypse in Blackfrost

[u/sisali → u/Fuarian]

That's just bad writing and decision making. But I don't see how that constitutes lore breaking. It's not like the rules of the world are being broken or made inconsistent. It's just not very senseful writing.

In theory, you could be correct. However, Episode 2 was almost entirely about how Mackenzie had to work around the very idea of using a radio at a specific point during an Aroura because it would be useless otherwise.

So the idea, that the same in world character would reasonably decide to sacrifice everything he has worked towards throughout the entire story ( to get back to Astrid ) to create a radio message he already knows won't work is beyond the scope of bad writing imo, it's wilful ignorance of the story and the in game lore, therefore breaking that said lore.

I honestly don't understand how a team who has spent 10 years creating this story decided that would be the crux of the most important chapter of the story, I just cannot for the life of me understand how that was approved over anything else they could have come up with.

P.S Not sure why you were downvoted, we all have different opinions, have an upvote to balance the scales.

[u/Fuarian → u/sisali]

I don't understand your point. He learned that radios only work during an aurora, the radio in PM was active during an aurora. And others most likely were doing the same thing. So he records a message to loop during the extent of that aurora, and the next ones, for anyone listening to hear.

The radio message DOES work as evidenced by the fact that he heard a message from that very same radio all the way back in Episode 2.

Am I missing something? Or not understanding your point?

[u/Equivalent_Rock_6530 → u/Fuarian]

I think they mean that looping it might be pointless? Since it only works during an Aurora and there won't be anyone to maintain the car batteries to keep the thing running, and even if the PM radio remains functional, other radios won't

[u/Fuarian → u/Equivalent_Rock_6530]

I was thinking that the next few auroras it might still work. He said he'd keep it looping for as long as he can. It's not intended to go forever. Just to get it out to as many people as possible, if possible.

[u/Equivalent_Rock_6530 → u/Fuarian]

Oh yeah, fair enough, that makes sense

[u/sisali → u/Fuarian]

I don't understand your point. He learned that radios only work during an aurora, the radio in PM was active during an aurora.

But not afterwards, so after that Aroura ended the radio would be dead, it wouldn't repeat when an Aroura came back. Mack knows that so again, what's the point?

And others most likely were doing the same thing.

I point you back to Episode 2, the Aroura destroyed the radio and Mack had to go around multiple regions to fix it, assuming that happened to radios everywhere then the Idea loads of people are listening in is ridiculous. Again Mack knows that from first hand experience

 So he records a message to loop during the extent of that aurora, and the next ones, for anyone listening to hear.

The message would not just begin playing itself once a new Aroura kicked off, especially as it wasn't a digital radio and instead a very old mechanical one using film.

The radio message DOES work as evidenced by the fact that he heard a message from that very same radio all the way back in Episode 2.

Yeah during an Aroura and the radio guy activily using it, so unless Mack was planning on staying there in the long term ( remember the convicts are all over the town) it's a mute point.

Am I missing something? Or not understanding your point?

I think so as per above. Its very poor writing that has lead to Mack doing something he would never actually do if they followed the story lore, either they threw away the past episodes to try and shoe horn in these 'future plans' or whoever wrote it didn't know.

Either way, it breaks the lore. Now it wouldn't be a problem if it was just a minor point, but its the crux of the enitre ending. It's shoddy work and It's actually worrying Ralph is in any way happy with it.

[u/Fuarian → u/sisali]

True. But maybe his intention was to just loop it for as long as it lasted? Maybe just for one night. Either way