thearcan

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.

Still here! I've been updating the latest gather thread whenever there is news (though I'm also trying to ensure that the news is tangible enough for you to understand the behind the scenes). I'll likely roll out a fresh more encompassing thread soon.

Please do bear in mind that us not posting over the weekend does not mean anything has been abandoned.

In my opinion, the largest issue (after damage mitigation is fixed) is the lag in multiplayer. Most of the time it is unplayable if I'm not the host. Is there any plan to address this? Is it possible to fix?

Yep, this has been on our radar for a while and we're aware that lag and rubberbanding issues still persist for some players. We haven't forgotten about them and are continuing to look into it.

Thanks for the kind words! Happy friday! :)

Please try re-selecting the latest Story Point in the lobby (don't hit continue when in the lobby).

No nerfs are planned for the upcoming patch. The patch is focused primarily on the survivability issue.

As a reminder - Balancing changes are mainly done via the backend and would most of the time not require a patch.

Our last patch did include a small number of intentional (positive) balancing changes that did require some patch work (such as changing sniper behavior and Perforo stuns), but it did not include any intentional nerfs.

The Killing Spree and displayed armour value changes that showed up alongside that patch were unintentional and were rolled back within hours. The reason they crept in is because the patch included an optimization on how the backend was being used, but when pushing this live a small number of outdated configs were pulled, which resulted in the handful of issues that appeared which were subsequently and quickly reversed.

Any other perceived nerfs are not intended. For example, the Devastator Statue set now only lasting 8...

Understood, thank you!

FYI - I've just updated my user flair here to better indicate my position.

That thanks to your feedback - this should help other people avoiding confusion regarding who the CM is in future.

Thank you! :)

I was able to do CT14/15 before but now get killed too easily on CT12. Even Perforo’s seem tear through me.

Thank you very much for the video and the details, I'm passing them on to the team! Take a look at the update I just posted in the main thread - your experience at CT12 looks familiar... Are you level 50? What happens when you play higher level content (CT15 for example) - Same problems?

Edit: Watching your video properly now as well so apologies if it already answers my question.

Edit 2: Those photos of your build and skill tree would be tremendously helpful too if you could share them.

Wat

The statue set acting in this way is a bug, not a nerf.

We're considering whether there's a way to "help" this issue via the backend, but a true fix would require a patch. Our currently worked on patch is, however, focused on the damage mitigation issue and is slimmed down in order to expedite it. So it won't address this issue yet.

Poof! With a puff of smoke I appear (cough cough). Thanks for the summoning circle.

I've just updated the gather thread here.

As mentioned there, testing for the patch is ongoing, so we can't yet say when exactly the patch will be ready for sure, but I'll let you know the moment I have news on that.

That being said, I mentioned the below in the gather thread too:

Note: As testing is an ongoing process over a number of days, we may not provide a public update here tomorrow (Tuesday, 11.05.2...

Thank you! As a fellow Londoner, I can appreciate the analogy!

Thanks for the reply, it's good to chat about these things. Happy to share the pie with you and have a slice myself.

Normally I would be much better at taking all your thoughts about communication improvements on board and seeing what I can be doing to address the conclusions you're drawing about us. (For example, what can I do to help players like yourself better understand from the get go what my role is etc.) If I had more time (and I will in future), I would be all over that.

I shared the post mortem in the week following the launch. You ...

No problem! As an aside, as it is topical, I've just shared the latest news around the damage mitigation issue in the gather thread.

Heh, just replied in the other thread here. :D Quite interesting to see exactly what I wrote there ...

No patch planned for today.

I can very much appreciate the meme though so full credit to you there. :)

It may be helpful explaining things from our side:

Ideally we aim to patch on a Thursday or a Tuesday - that's the base aim. And it has been on all games I've CM'd on to date (8ish years of CMing overall).

With Outriders, as you well know, there were and are still some hot button issues. We have never denied them, and we have always worked our hardest to identify their root cause and resolve them.

So we find fixes, we compile a Patch Build, we run that Patch Build through QA. QA works that build through their regular process and regresses fixed issues (i.e. they confirm that the fix has worked) or they don't (in which case the fix has not worked and we go again, so a change/fix could get pushed out another week).

That's a very rough explanation of the cycle, but lets say (for the sake of argument) that a Patch passes out of QA su...

Truth be told, nobody in any team is purposefully trying to limit what we (or I) am allowed to say or talk about. There is no one at PCF or SE telling me that I can't say or talk about certain things.

My style has been developed from on my personal experiences with communities more than anything. As /u/DocDevice pointed out, this isn't my first rodeo. I'm 8 years into CM'ing at this point (If I'm not mistaken).

If you want to understand why I tend to be careful in what I say, look no further than the below example.

/u/DocDevice When you talk about my fears of being "quoted out of context", I must ask: Were you checki...