Re: @Devs or CS Rep: start perusing and taking forums seriously
@E9ine_AC From what I know, please correct me if I'm wrong, the forum mod (talking as a whole) is most of the time part player, part dev. The CS team definitely has admins and mods operating the forum, but may, in times of need, also "hire" outstanding users to lend a helping hand with summarizing things on the forum.
Part II of what I know is that CS needs to convert "random rants on forums that may describe, even if vaguely, an issue to the QA team, after which the issue is tracked in their internal database/QA reports. If it's not reported, someone gets bum whipped, the issue is then sent directly to the DEVs and a fix ensues, depending on the complexity of the issue (most of the times it's a "will not fix", since it may, at this point, cause more issues - hence the severity and priority of the issue are important, and a deciding factor).
Out of all the threads I've perused, I'd say about 83% of them are simply pointless rants, filled with mistakes, wrong attributes when specific issues are addressed or plain venting (users that start or contribute to those threads barely log back in to check the flow of the convo).
But (even if I'm being generous) the 17% remaining, that can be utilized in a proper fashion seems left unattended. A simple post, like "The team is aware of the issue and we are investigating internally. The changes will be reflected in the patch notes", followed by a thread lock by a mod, isn't hard to make, especially with copy/paste templates that CS must have (when they aren't allowed to go too in-depth with some info being required of them).
Back to the actual thing you mentioned that I also wanted to address, I have to argue that it is in their job description and is required of them to inform the players. User feedback is both ways: what I, as a user, and also what is transmitted to me, from the development team (through any means or channels).
Simply ignoring the logical steps in interacting with the playerbase and deciding to drop some fixes (after a lengthy time of not addressing them, in writing, where they have been reported) is, in my opinion, a mistake that will add up to others, pile up and lead to a downward trend in user acquisition. Even if they are working on things, not communicating makes the users believe nobody gives a hoot. As an example to support my last idea: the ring flare SFX issue -- hearing the specific sound effect across the map, whenever any player, in any location, would enter a heat shield - a deafening and severe issue, causing gameplay issue (in a shooter where audio cues make the difference between a win and a loss).
I might've gone a bit overboard, please let me know if I've failed to address anything.
I have no intention of derailing the conversation or asking for a statue; I simply believe in a thing well done and I want to be able to say this about "everything Apex".
Thanks for weighing in, much love!
Part II of what I know is that CS needs to convert "random rants on forums that may describe, even if vaguely, an issue to the QA team, after which the issue is tracked in their internal database/QA reports. If it's not reported, someone gets bum whipped, the issue is then sent directly to the DEVs and a fix ensues, depending on the complexity of the issue (most of the times it's a "will not fix", since it may, at this point, cause more issues - hence the severity and priority of the issue are important, and a deciding factor).
Out of all the threads I've perused, I'd say about 83% of them are simply pointless rants, filled with mistakes, wrong attributes when specific issues are addressed or plain venting (users that start or contribute to those threads barely log back in to check the flow of the convo).
But (even if I'm being generous) the 17% remaining, that can be utilized in a proper fashion seems left unattended. A simple post, like "The team is aware of the issue and we are investigating internally. The changes will be reflected in the patch notes", followed by a thread lock by a mod, isn't hard to make, especially with copy/paste templates that CS must have (when they aren't allowed to go too in-depth with some info being required of them).
Back to the actual thing you mentioned that I also wanted to address, I have to argue that it is in their job description and is required of them to inform the players. User feedback is both ways: what I, as a user, and also what is transmitted to me, from the development team (through any means or channels).
Simply ignoring the logical steps in interacting with the playerbase and deciding to drop some fixes (after a lengthy time of not addressing them, in writing, where they have been reported) is, in my opinion, a mistake that will add up to others, pile up and lead to a downward trend in user acquisition. Even if they are working on things, not communicating makes the users believe nobody gives a hoot. As an example to support my last idea: the ring flare SFX issue -- hearing the specific sound effect across the map, whenever any player, in any location, would enter a heat shield - a deafening and severe issue, causing gameplay issue (in a shooter where audio cues make the difference between a win and a loss).
I might've gone a bit overboard, please let me know if I've failed to address anything.
I have no intention of derailing the conversation or asking for a statue; I simply believe in a thing well done and I want to be able to say this about "everything Apex".
Thanks for weighing in, much love!
