This is not a rant, just trying to explain why sometimes people don't get answers fast, or not at all.
Unless devs get a very specific idea of the problem you have, they won't be able to help you with literally no information given.
A lot of time is "wasted" here with people basically asking for help but not providing any useful information the first time, or worse, asking for the same things over and over again.
If you're not willing to properly explain your problem (no, "it doesn't work" or "it stopped working" is not explaining), you can't expect help in return.
It's simply easier to help someone who's willing to dig into the problem, and then report it.
The best way to get a quick answer is to provide as much information as possible:
- A list of everything you did prior to the bug, what did you try to accomplish (for sm4shexplorer for example, what files have you added/modified, did you try to cheat on the LS check like many, way too many did...)
- What have you tried already?
- Logs (if no logs, at least the detail error message)
- OS and eventually any specificity (what version of python, no sound device...)
- Screens, if you think it can be useful for a better understanding of the issue.
With that, if the bug is already known, another member will be able to help quickly. If its not, either the dev(s) will qualify it as a new bug (which is very possible) or you can also create a new issue in the github of the project.
With very specific (and fairly young) modding tools, there are a lot of unknown variables. One example in my case would be the Metaknight bug, I had no idea it was even a thing since it was brought up. The issue was quite simple to understand: After rebuild: victory animation 3, game crash, and logs were provided > was a lot easier to find the reason and fix it. (Thank you to the person who reported it by the way!)
OP: I think a paragraph on how to properly report a bug would be nice, and maybe adding a list of bugs already resolved?