Some updates seem to leave recurring interface bugs untouched, while others introduce problems that can stop missions from progressing. What should players reasonably expect from update testing and fixes?
Why do the same bugs keep showing up after updates?
Answers
Not every bug needs to hold up an update, but anything that blocks normal progression deserves a higher priority than a cosmetic glitch. Test the main mission paths before release, then be clear about what is still broken and when a fix might be coming.
Some failures are hard to reproduce, so a known issue may take longer than players expect. That is different from leaving people to guess whether anyone is looking at it.
Reply to this answer
A bug surviving an update does not necessarily mean it was ignored. The fix might not be ready, or it might need testing to make sure it does not break something else. A short status update would still help, especially if the issue has already been acknowledged.
Reply to this answer
Players should be able to criticize release quality without getting shouted down. A useful report says what happened, where it happened, and what was expected instead. That gives the developers something more actionable than just saying the update is broken.
scrimBenchCobbler:
And if it is intermittent, mentioning that can help distinguish it from a bug that happens every time.
Reply to this answer
Repeated minor bugs matter too. A new item marker that keeps returning or a reward display that does not refresh can make the whole interface feel unreliable. They may not be emergencies, but they are worth tracking rather than treating as invisible.
Reply to this answer
Add your answer
Answers are reviewed before publication.
turboTapTaffeta:
That distinction makes sense. A recurring interface issue is annoying, but a mission that cannot be completed is a bigger problem.