devtrackers.gg
Looking into this now.
Looking into this now.
However, for this morning's update, in order to keep downtime to a minimum, we did not restart one of the necessary central services. We felt that it was not required - we were wrong.
So... did you try turning it off and on again?
Technically speaking? Yes.
Then took the cartridge out, blew on the connectors and put it back in.
We also included a client change to fix the crash that I mentioned.
Adding to Andy's note: we setup an open thread on the forums for players/Outfits to report lost crafting progress (and associated resources):
https://forums.daybreakgames.com/ps2/index.php?threads/march-13-2020-escalation-hotfix-2-pc.253628/
We're particularly looking at the window between the two Hotfixes - the first at 6AM PDT, the second at 130PM PDT - as one of our worries was that resetting the service Andy referenced might cause Outfits who tried to re-craft Assets they had lost after the first Hotfix to lose progre...
Read moreHey everyone,
First, I want to apologize to our EU community, since this took place right in the middle of their prime-time. Please know that we try to avoid this at all costs, unless the severity warrants it. We will continue to avoid this going forward.
Changes included in the 130pm (Pacific) hotfix:
Of the two changes, the Bastion component crafting and Expedition progress loss were the reason we decided to perform an emergency hotfix at this time.
So how the hell did we miss such an obvious bug?
The way our live infrastructure is configured, each region utilizes dedicated hardware for the game servers. However, we have several "central" services that essentially st...
Read more External link →If you happen to know of any footage we can look at, could you post a link?
Do you want me to record and post a video showing both the 'bugged' and 'unbugged' states that I described?
Just the method of getting into the bugged state that you described, and feel free to message me with it. We were able to repro the infinite critical chain bug, but it was done in a way that's very different from what's described here, so we want to make sure we catch all the edge cases.
I know - incredibly sh*tty timing. But its to address the issue that happened with the update this morning where Bastion components that were in progress were lost, along with the resources. This should be a relatively quick downtime.
Your team is awesome, thanks for all the great work. Escalation is the most fun I've had in a videogame in years.
Thank you for the kind words!! That you’re enjoying the update is all we can ask for :)))
I've noticed that you can 'prevent' the Critical Chain duration bug by resupplying at an infantry terminal (somehow, it forces the duration to function normally).
However, the bug will still occur if you use the 'redeploy method' of class switching; redeploy, respawn as a different class, then redeploy again and respawn as an Infiltrator with a bolt-action and the implant equipped. If one remembers to never use infantry terminals, the duration is literally endless.
Would suggest that the devs check to see what exactly changes when you resupply at an infantry terminal, versus just using redeploy to respawn as a different class.
If you happen to know of any footage we can look at, could you post a link?
