What if we make a team of qualified individuals that are specifically hired to address ban requests?
Here’s the way this will work.
•These individuals will be scanning through ban requests that can be found here on the forums. Alternatively, a channel can be opened in the Firestone Discord.
•Once they approve a ban request, it is sent to a Trello where they will be accessible by one Firestone Developer.
•The Firestone Developer being the link between the State of Firestone Trello and ban request will send the cards to the board and the ban is complete. The template will be pre-filled and the stack will be checked on a consistent basis. This board will be publicly accessible and I think it would be an easier way for people to understand that combat logging is not acceptable in the State of Firestone.
I’ve had a pending ban request for 2 months once. The evidence was more than valid. When I replied on the topic with “Nothing? It’s been two months…” someone replied with “It’ll come around some time.” 3 months later and still nothing, not to mention the channel being deleted in its entirety. I see people send Straphos ban requests all the time with “@Straphos [link]” but I doubt he has the time to put this all in.
I would not have created this topic if I did not think the Firestone Moderators could have done it. However, as LEO’s grow more agitated in doing their jobs which result in a reckless performance, I’ve come to realise there’s no actual solution to this.
In the event a Combat Logging Team member goes rogue:
•The State of Firestone Trello is protected. As previously mentioned the Firestone Developer is the link. No direct access. It also serves as reinforcement for bans so that we can say “This ban has gone through multiple people before being placed.” No escaping this time!
•As many of you know, Trello allows you to bring back archived items. If not, as I also stated before, bans are checked on a consistent basis. They’d probably only have a maximum of 5 or 6 ban requests archived.
What do you guys think?
This goes sorta kinda with my other proposed combat logging solution but is not the same.
