Outriders Dev Tracker

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...

We were able to fix the armour values skyrocketing because of an incorrect value on the backend. Tweak that, run a maintenance to push players onto the same backend, issue resolved.

The damage mitigation issue is because the game is (under certain circumstances) not pulling a certain backend table, so it doesn't matter what the backend says, the game isn't reading it. There is no way to fix that via the backend.

That's why this second fix is taking a bit longer while the first one was easily resolved.

Regarding the bug with the amour - the values are just a symptom of the issue. The root cause is a nasty little bug (whereby the correct values are not being pulled) that needed to be found and patched just like any other bug.