Best case scenario: There is a patch with some real changes that is going to drop any day now and it was too late to revert the tooltip.
/shrug
Best case scenario: There is a patch with some real changes that is going to drop any day now and it was too late to revert the tooltip.
/shrug
Look, we’ve all seen devs just omit things from patchnotes for whatever reason.
If there was ever a time it would have been ok, maybe even a good idea…
As is tradition.
Like how Disrupt Destiny used to not show you your buff stacks even though the buffs were active and how that bug was in the game for more than 575 days ![]()
This, but also they probably noticed the issue after submitting the release to xbox/playstation for approval so they had the choice between a release that fixed some crashes but has some incorrect text, or hold off on the crash fixes to back out some text, recompile, and resubmit to xbox/playstation and wait another week for approval.
One is objectively worse than the other.
^ 100%, well coem to wonderful world of software development. If people knew how the sausage was made they’d buy a cabin in the woods and live off the grid.
Deploying updates and getting updates is a major PITA on consoles apparently.
FWIW I’ve harped on it in the past, but DT and many other games could really benefit from some kind of on-launch over-the air micro-patching (secure and immutable) for stuff like this and Lua script typos/omissions similar to what Borderlands 3 had.
IDK if this would have required EAC to protect this part or not. I imagine it’s a bit trickier here but boy would it have solved so many problems and community backlash.
What is this company lmao just when you think you’ve seen the absolute peak incomprehensible mess that is fatshark management and decision making they manage to surprise us.
Post about the upcoming quarterly update that should be released within the next few weeks ![]()
add misinformation to the game for absolutely no reason ![]()
I can’t help but notice you still haven’t added a way for us to play solo with bots. It’s still coming, right?
Wow. Worst patch by FAR for me. This supposedly “crash” fixing patch has so resulted in 10x more crashes than “normal” for me >_>
They stopped caring after the console port.
Now they can reap your aquila and release content nobody requested, like mortis trials and havoc.
Bots will not happen. Deal with it.

Not so green.
Not with that attitude. The less we hold developers accountable, the more they’ll take advantage of their players. Fatshark already has an entire list of unfilled promises, are we just going to let them promise to add/do something and then just roll over and let them pretend like they never said that once they got our money? I bet restaurants love you. They can charge you for anything and then tell you it wasn’t a priority when you don’t get it and you’ll say “ok” and pay them anyway and keep coming back for more
Reminder that all FS would need to do is change the minimum player count for private games from 2 to 1 and you’d be able to play solo online.
Every day that passes is a day where Fatshark chooses to not let players play solo.
i start having crashes the 2 days
Feels like 1 in 4 or 5 missions is guaranteed server disconnect and booted back to mourningstar.
Got up the point now treat it as being all about the combat plays you can pull, than getting to the end.
It’s ridiculous that we are still here.
1 week has passed since misinformation was put in the game
misinformation that isn’t true yet is the new soon™. we’re braving new frontiers.
I truly believe they have a serious, serious, serious staff shortage. They must be micro studio size judging by the output and fix rate