No - the root cause of the issue was a bug that was causing the backend table that deals with armour calculations to not be pulled properly.

The brood mother changes are related, but a separate matter.

Thanks! As you have a Youtube Channel, do you have a video (or stream VOD) of where we'd be able to see this in action, including what your gear might be at the time?

I can understand that. That's also why I'm hoping to pull together the known issues thread, so that you can see some of what's in the pipeline.

Nothing about the inventory bug where all items always show up as new?

This will be noted in my next news thread - it will be fixed in a future patch.

As explained a few times previously, this patch is primarily focused on the damage mitigation issue. Other fixes are in the pipeline, but we want to keep this patch slimmed down to be able to focus on damage mitigation.

https://preview.redd.it/nsgwf9uf1a171.png?width=1200&format=png&auto=webp&s=8a3ceb57c74302559bf9a3dc8aea48f571e33c74

Our latest Patch has now released.

Patch Notes:

• Fixed a bug that was causing armour values to not be calculated properly under certain circumstances, leading players to take unintended increased damage.
• Changed the damage behaviour of Brood Mother enemies to prevent them from one-hit killing players in under certain circumstances.
• Addressed an issue that could cause players to be unable to sign-in under certain circumstances.
• Added telemetry to better track and diagnose any outstanding sign-in issues.
• Fixes for crashes.
...

given how your turn around time on each patch seems to be about a month it would be way worse not to know your intentions.

Yep, none of us want such a long turn around cycle, but it's partially a result of the sudden "high-impact but quite random" issues that we've faced. If a bug were happening 100% of the time to everyone, it'd be much easier to reproduce and fix in turn, thus also speeding up the patch release.

That being said, we are looking at ways to increase the frequency of patches so you don't have to go so long in between them.

As just announced, unfortunately the patch is not ready for release today despite our best efforts.

For me personally (as one of the Outriders CMs), with us having previously talked about our aim to deliver the patch today, this raises a bit of a quandary about how we're communicating that I'd been keen to hear your opinions on.

As you know, we've made it our goal from the start to be as open and transparent about Outriders as we can be. That's also the reason why I've never shied away from acknowledging issues or setting up gather threads here on reddit, but also why I've made sure to always provide you (the community) with as much behind the scenes info as I can.

For example, during our launch week, with the server issues, we made sure to update everyone regularly (in 20 minute time-gaps) with what was going on and we also subsequently shared our ...

Same.

This is a known issue and is on our radar. At this moment in time I can't yet say for certain when it will be patched though, but we are aware of it.

No problem, I appreciate your ongoing support here on Reddit! :)

I'm also trialing out a new "latest dev comments" section on this megathread's OP, so that will hopefully make some of my replies about such topics a bit more visible.

The latest Stadia build is continuing to be worked on but I dont have any news today. But as soon as I do, I'll let you know. You've not been forgotten.

Yep, we're aware of this issue - it seems related to when the client or the host might not have the Hell's ranger gear pack installed. The investigation is ongoing so I can't promise when it will be fixed, but we're aware of it.

This patch won't include a fix for that, but that particular issue is on our radar to be included in a future patch.

One of the reasons why it's taking a bit longer is precisely because we're seeing what's possible in order to provide you with a better experience.

For example, we're looking into coding whether it's feasible that the appreciation package makes sure to only include a legendary(s) that the player has not received to date. This isn't part of the script that we used for the inventory restoration, but it's an example of us needing a bit more time with it.

I know that there are a lot of discussions and questions around legendary drop rates at the moment, and truth be told I think there are multiple different reasons that come together to form the overall sentiment. (e.g. opinions about not getting enough legendaries overall, not getting specific enough legendaries etc.)

I'm hoping to be able to share a bit of info/news about drop rates soon, but don't want to promise anything specific just yet. But I just wanted to say that we're aware.

Hey everyone,

We've just shared some more fun stats about Outriders via our Social Channels including the fact that we surpassed 3.5 million unique players in our first month after launch!

Launching an entirely new game IP is never easy and we remain very grateful for all your support and feedback – we are still here, are continuing to listen carefully and want to assure you all that we are committed to improving and enhancing your experience throughout the coming weeks and months. We're also looking forward to expanding Outriders in the future…

But first things first: Our latest patch, designed primarily to address the damage mitigation issue is currently running through some final testing. As mentioned yesterday, we're hoping to release it this Thursday (May 20), but that will only be confirmed once it successfully passes through testing.

The patch will additionally include cras...

Thanks for the write up and the detailed time-stamps! I'll pass this on to the team :)

The threads I reply in should get a special little flair indicated my activity in them. (This thread has the flair: Question // Dev replied X)

I pin the threads with big news when I've posted the threads myself, but Reddit only allows 2 pins at a time, and given that I can often be active in multiple threads in a day, pinning them all isn't feasible.

Good question! Here's a timeline to help explain things a bit :)

In this case, we identified what we believed was the root cause of the issue on the 7th (Friday), and I updated the community then. Bear that date in mind as you then work through the process below.

Once an issue fix has been identified, it needs to be software compiled into a build. So all game files need to be pulled into a proper build, not just loose files. That can take a few hours, perhaps half a day.

That build is then smoke-tested) on-site, which also takes time. Add half a day.

Once it's through the smoke test, the build needs to be uploaded and sent to our wider QA teams. That upload can take a while since the build is tens of GBs in size. Add on a f...