Hi,
it's unclear to me if the bug report I filed shouldn't be in the technical issue section instead.
It seems the difference between the two is whether or not something can be fixed by the user, but since I'm not sure what the issue is where should I put the post to be sure I get the help I need?
Here is the post: viewtopic.php?f=7&t=121991
Cheers,
Lyno
Bug Report vs Technical Issue
Re: Bug Report vs Technical Issue
In my opinion (I'm a random software dev), if you're unsure, don't bother with the distinction and just try to provide as much context for your problem as you're able to. Any kind of issue (bug or support) is still an issue, if you don't have the expertise to file it accordingly, leave it to the devs to figure out how to act on it.
Most closed-source projects don't even run a public bug/issue tracker, but provide something like Zendesk where people can only file support cases; your specific support case is never visible to the general public, etc. A support agent can escalate an issue to a PM (or an on-call engineer for critical cases), then from PM it gets assigned to a dev, etc. Wube cuts thru that extra fat because they don't need 20.000 employees (and imho the end product would've been way worse if they did).
Most closed-source projects don't even run a public bug/issue tracker, but provide something like Zendesk where people can only file support cases; your specific support case is never visible to the general public, etc. A support agent can escalate an issue to a PM (or an on-call engineer for critical cases), then from PM it gets assigned to a dev, etc. Wube cuts thru that extra fat because they don't need 20.000 employees (and imho the end product would've been way worse if they did).
Re: Bug Report vs Technical Issue
Local moderation team don't mind stray bug reports ending up in technical issues, vice versa. So unless it's something outrageous like "my Ritmix mouse LED do not react to Factorio events" posted in Technical Issues - you're fine.
Re: Bug Report vs Technical Issue
About terminology:
a bug is a software defect. For example, if some action results in an app crash. Or if some app functionality doesn't work as it was designed to work.
Everything else is some kind of user issue.
About "app functionality doesn't work as it was designed to work": most users think "this doesn't work the way I thought it would" and declare it a bug. However, in most cases it's just a misunderstanding the user has about this functionality, so it's just a user issue. No bug, as long as the function performs as it was designed to perform - no matter what the user assumes about this functionality. It's similar to airplane crashes: 70-80% of the crashes are pilot errors, not airplane failures.
a bug is a software defect. For example, if some action results in an app crash. Or if some app functionality doesn't work as it was designed to work.
Everything else is some kind of user issue.
About "app functionality doesn't work as it was designed to work": most users think "this doesn't work the way I thought it would" and declare it a bug. However, in most cases it's just a misunderstanding the user has about this functionality, so it's just a user issue. No bug, as long as the function performs as it was designed to perform - no matter what the user assumes about this functionality. It's similar to airplane crashes: 70-80% of the crashes are pilot errors, not airplane failures.
Re: Bug Report vs Technical Issue
You a not reporting a bug, you are asking for someone to fix your save file so Technical help is exactly where it belongs. If you can provide steps that actually produce corrupted save files it's a completely different story.