Or have proper analytics. If a user emails you and says "It crashes after a few hours" rather than feeling bad for them, you ask them what their steam/game id is and you look them up in the crash reporter system and see exactly what happens rather than relying on a few programmer consumers doing the work for you.
But not analytics that are too good, or certain people will write a lot of inflammatory articles about how your software is nothing but evil spyware.
Seriously, though, having a robust and automatic crash reporting system very much helps track down bugs you're never going to get a good report on or be able to directly reproduce.
Possibly, but how many of the bugs are rare edge cases (i.e., attempting to break the game) versus problems players actually face in normal gameplay? Without knowing what priority or severity these bugs take, it is difficult to say how useful the increased volume of feedback is.
Even if someone is not attempting to break the game, they might accidentaly hit those rare edge cases.
Of course, you could infer the usefulness of the increased volume of feedback from the fact that a game author is extremely happy about it.
Overall, I don't see any particular problems with having reported issues. We definitely don't pay cloud storage per open issue or anything like that. Initial assessment of a bug report is not particularly difficult either.
I'm not sure if your concerns translate to actual negative impact.
Depending on what kind of game you have, those exotic edge cases can come to be the dominant behavior in games, particularly multi-player where slight advantages can lead to some players dominating every one else.
Or have proper analytics. If a user emails you and says "It crashes after a few hours" rather than feeling bad for them, you ask them what their steam/game id is and you look them up in the crash reporter system and see exactly what happens rather than relying on a few programmer consumers doing the work for you.
But not analytics that are too good, or certain people will write a lot of inflammatory articles about how your software is nothing but evil spyware.
Seriously, though, having a robust and automatic crash reporting system very much helps track down bugs you're never going to get a good report on or be able to directly reproduce.
It's not really that hard to do this: ask bug reporters to attach their logs. Don't just take them preemptively "just in case".
3 replies →
Possibly, but how many of the bugs are rare edge cases (i.e., attempting to break the game) versus problems players actually face in normal gameplay? Without knowing what priority or severity these bugs take, it is difficult to say how useful the increased volume of feedback is.
Even if someone is not attempting to break the game, they might accidentaly hit those rare edge cases.
Of course, you could infer the usefulness of the increased volume of feedback from the fact that a game author is extremely happy about it.
Overall, I don't see any particular problems with having reported issues. We definitely don't pay cloud storage per open issue or anything like that. Initial assessment of a bug report is not particularly difficult either.
I'm not sure if your concerns translate to actual negative impact.
Depending on what kind of game you have, those exotic edge cases can come to be the dominant behavior in games, particularly multi-player where slight advantages can lead to some players dominating every one else.
I'm not a gamer, but from what I've read, the whole industry has been transformed by the incredible lengths people go to, to cheat.
So I would expect that edge cases might be really relevant to mainstream use because everybody is trying to break the game.
FTA it sounds like basically all of them were normal gameplay that affected all platforms. only 3 were linux specific.