Hey @Tempestorm
We’re aware of this issue and it’s been fixed internally. It will come out with the next hotfix, to be released as soon as possible alongside other critical fixes.
Thanks for the feedback and apologies for the frustration.
We have no estimate at the moment other than as soon as possible. We’re doing all that is in our hand to make this hotfix hit early next week but this could be affected by factors out of our control.
Apologies for the inconvenience.
We are not “refusing to patch”. Cooking a fix into a build and releasing it is not as simple as just pressing a button and having it ready and available in a couple of minutes, at least not in the current engine we’re using.
Since the process takes hours, and there are other critical issues that have been addressed in that span of time (along with certification considerations as this and other issues are not exclusive to this platform), we opt for having a bigger patch to maximize our time and resources.
Since this feedback has been collected and addressed, and the thread is once again derailing, we’ll proceed to close this topic. For any general discussions about the game, please use the corresponding subforum.
Thanks.
devtrackers.gg