I did read the bug report document but
1. I have a disability that prevents me from comprehending large blocks of text, I legitimately glaze over and entire pages of text will go through me, even if I think I'm reading them.
2. It's very difficult to sift hundreds of bugs spread across multiple tabs just to cherry pick a single one, especially closed issues such as this one, especially since this is my first time ever playing FF7 so I don't have context for most of the bugs and can't easily parse when something is relevant.
3. Having finally found it after an hour of trying to read it over and over, eventually getting two friends to help me search and finding it, I will note that unless hotfix 2 isn't R06b, it was still occurring for me after patching with the hotfix, which I noted.
4. Given that I was on the latest update posted in the thread (the hotfix), I really did not expect it to be marked under "fixed."
Is there any reason you haven't migrated to a dedicated bug tracker like Github or Gitlab? Even if you don't post the code there and just add a ReportInstructions.md or Troubleshooting.md or something, it seems like having a searchable issue tracker would cut down on repeat bugs and thread pollution. The vast majority of the bugs in the google spreadsheet are marked fixed, so it shouldn't take too long to migrate the several that still exist to an issue tracker, I'd even help. I understand if you want the doc around to keep notes on legacy bugs, but an easily searchable issue tracker would really benefit end users, especially those with disabilities like mine that make it difficult to parse large amounts of text. It would've been rather easy to just search something like "honeybee jitter in:issues" and click on open/closed to see the bug. You can even set it so users who open an issue are given an autogenerated template to fill out.
