On reporting issues

TLDR: Provide as much information as possible (logs, screenshots, description/instructions for reproduction). "It doesn't work" is not enough.
Also don't use reviews on the forums for getting support, I can only reply once and the reply will most likely never be read. I also don't provide support via email. Finally, don't ask to ask.

If you want to increase your chance of receiving help with your issue it's important that you provide as much information as possible in your request. Just stating that something doesn't work won't do. It might come as no surprise that playing tech support, spoon-feeding (i.e. telling you things you could've figured out yourself easily) and pulling teeth (i.e. having to painfully extract each piece of information individually) are not the most fun pass-times for me, so I sometimes answer very briefly and might even come off as harsh, which is not intentional. As long as you remember

• to provide enough information with your request,
• that me and others are doing this in our free-time voluntarily,
• to not act like you're owed support

things should be fine. A proper bug or issue report should contain

• the entire obs studio log related to the issue (more info here),
• crash logs (if applicable),
• a thorough description of all steps taken to encounter the issue/bug/crash,
• screenshots of configuration dialogs/source properties/obs if necessary,
• any steps that might've been taken to attempt to solve the issue.

That's really all there is to it. Issues can be reported on my gitea instance or on the forum thread for the respective plugin.