All I know is that the bug reporting community is filled with tons of “not a bug” and “not enough info” responses, and sometimes, issues that are just a couple of sentences long—or even lack image evidence—still get approved. To fully meet a bug manager’s requirements? Well, that’s basically impossible. The only way your issue might survive is if you’re lucky enough to have a manager who actually takes the time to read it carefully. Most of the time, they just send you a canned reply, give no explanation, and lock your issue. Now, they’ve turned off the display of manager names, so we can’t ask for reasons on the community forum anymore.
5 Likes
99% of the time, they are valid. The other 1% is usually a game decision by the devs and it is an arcade game, I should stress.
1 Like
Not really. If it’s not announced that the fix will be implemented, it’s not validated. How many reports were validated 1, 2, or 3 years ago and are still not in the game for no gameplay changes, just added content? Many! It’s the managers who validate all the information. The developers can’t do anything, like model objects for testing and then leave them abandoned in the datamine.
5 Likes
Please elaborate your point. Do you mean that mass-NEI/NABing the issue reports about the discrepancies between the in-game J-10 and the IRL one is justified, even when you can’t get access to the brochures that are export restricted and have to rely on cross-referencing secondary and tertiary resources?
Speaking of which, that Thai brochure of VT-4 was once rejected as “Sekrit dokuments” but look, now the Snail is openly using it for the adjustment of autoloading time for VT-4 and 99A. Now the arbitrariness is really tickling under us CN main’s skins.
1 Like