Hey @VirginMarie
We were made aware of this issue shortly before releasing the new patch. We’ve fixed it internally and will release a hotfix soon to cover this issue.
Thanks for your feedback and apologies for the frustration.
We’re not going to get into details, but there are certain steps needed to release a patch specially when taking into account all platform requirements. In this case, it was minutes before pressing the “send” button on the patch notes. The process on all platforms was already started and there was little we could do besides swiftly working on a fix. Which is what we did.
We understand that game issues can be frustrating and you’re all free to send us your feedback and constructive criticism. But please keep in mind that we don’t willingly release bugs or break things just because. We do have a QA process but what is often ignored when finding a bug in a released build, is that QA found a bunch other bugs that were fixed prior to the release. They do also run their own tests and report problems properly. We also gather feedback from our community that sometimes it is not yet found by us, other times it complements what we’ve found, and other times we already knew about. This is an organic process in which we want to include as much player feedback as we can, and in an open world sandbox games with many intertwined mechanics, many things can break or act strangely in the most unexpected ways.
Given that this issue has been acknowledged, fixed internally and discussed enough, we’re going to proceed to close this thread as it has served its original purpose. We thank you all again for your feedback and support, especially when delivered constructively.
devtrackers.gg