Originally posted by DapperDlnosaur
If you're unsure of how to make sure you are made aware of issues when people find them, the answer is to actually read your dang forums. If someone makes a post on the insider forums outlining a clear bug or issue and a single Rare employee reads that, it should be pinned or logged or linked to whoever needs to start fixing it. It really is that simple. And if not a single Rare employee is reading them, then there is no point in having them. There is no excuse for a big bug to be mentioned in the Insider forums and then make it to the live game, other than "we didn't have time to fix it, but we know about it and are working on it", but we don't even get that. Even the barest minimum of communication in-house should be preventing that from happening, like I said, if a single Rare employee is actually reading anything on the Insider forums and doing the minimal work of forwarding it to somebody.
Speaking of that, what exactly is causing issues to remain in the game for mon...
Read more
The best way to get critical bugs to the Dev team is to submit bug reports, while we have teams who try and skim the threads as part of our usual process there is a chance they will be missed in the discussion.
RE prioritisation, running a Live Service game takes a lot of triage and prioritisation to ensure we are focused in the right spaces. We have multiple game teams focused on long-term feature commitments (some 12 months out, others 3-6 months out etc).
We are always assessing the issues reported from various channels but ultimately we have to make a priority call on how much we invest in bug fixing alongside feature work - I won't claim that we always get that right, but it's a constant effort for us to juggle the various things we feel are important!