[Kovarex] [2.0.63] Smart belt bug #11: Belt not placed when dragging over belt ghosts after splitter
Re: [2.0.63] Just another smart belt bug #11
Describe the bug in the title please.
Re: [2.0.63] Just another smart belt bug #11
I’ve been numbering these “smart belt” bug reports (#1 to #11) because they’ve become so common that I no longer want to spend the time writing out a full, detailed description every single time. I actually even take the time to make a clear video showing the bug so there’s no misunderstanding.
Now my report gets moved to “pending” with the note “Describe the bug in the title please.” Honestly, if the title is so important, you can change it yourselves. The video is there, the bug is obvious.
Over the past year, I’ve probably reported around 30 smart belt bugs. I’m not part of the QA team, and I’m doing this for free. If more detailed, formal reports are required, then that’s something the developers should be compensating for, not something the community should be expected to provide without question.
Right now, the reality is this: changes are being shipped that break things, and I’m putting in the effort to find and document them. The situation should be reversed, the dev team should be thankful for community bug reports, not making us jump through hoops just to get them acknowledged. Having my reports blocked over minor formatting issues makes me lose respect for how the bug reporting process is being handled.
Now my report gets moved to “pending” with the note “Describe the bug in the title please.” Honestly, if the title is so important, you can change it yourselves. The video is there, the bug is obvious.
Over the past year, I’ve probably reported around 30 smart belt bugs. I’m not part of the QA team, and I’m doing this for free. If more detailed, formal reports are required, then that’s something the developers should be compensating for, not something the community should be expected to provide without question.
Right now, the reality is this: changes are being shipped that break things, and I’m putting in the effort to find and document them. The situation should be reversed, the dev team should be thankful for community bug reports, not making us jump through hoops just to get them acknowledged. Having my reports blocked over minor formatting issues makes me lose respect for how the bug reporting process is being handled.