Just to make sure, did you add all details you could to the ticket? I know it can be kinda annoying to collect and add too many details but it doesn’t hurt to try and could make things easier for them to check.
Like, try to make a reproducible test case, list everyone who were online when trying, everyone who received the dialog and clicked accept then everyone who went to the guild raid place. Like, to a point a dev can look at the table and know all the environment of what happened.
I’d recommend something like:
Date/Time (started the raid): 00/00/0000 - 00:00 AM/PM
Guild name: A
Guild level: B
Templar: F
Raid: C
Map: G
Total members: D
Total members online when starting the raid: E
Total members who saw the dialog: H
Total members who accepted: I
Total members who rejected: J
Total members who ignored (no click): K
Total members who were online and did not see the dialog: M
Total members who went to the X on map: L
Total members who went to the map and did not see the X: N
Date/Time (everyone on map): 00/00/0000 - 00:00 AM/PM
Time waited before leaving: [0 hours,] 0 minutes
Members:
Team Status See dialog Accepted Rejected Ignored (no click) [...]
GMem1 offline no no no no
GMem2 online yes no no yes
GMem3 online yes no yes no
GMem4 online yes yes no no
GMem5 online no no no no
I’d also add the columns/information if the people went to the map and if they saw the X.
As well get the time of when you started the guild raid, the time everyone was ready in the map and how much time you waited before it actually starts.
I’m not sure if all this information will be really helpful and in worst case scenario you’ll only “waste” some minutes. But if they actually look on the issue it’s enough information to check if the conditions were met and notice if there was something off.
I’d also recommend every member who want to do the raid to send a ticket as well since the problem is actually affecting everyone.
And as far it could be “i got automated answer; i got ignored; it’s not fixed” judging from our part, I’d say always try to do the most detailed bug report you can, in all games/software/etc. Even if people are busy enough to not be able dig the situation for the reason it doesn’t work sometimes a good report can pinpoint it exactly to the problem and it would be so easy to change that the developer would do it faster.
If not, at least you did your part >< Try to think on it with the mindset you’re trying to do your best to provide details for it to be fixed because you want it fixed and you’d help them to get it done by doing your part well, even though we have no obligation to provide detailed reports and etc.
