now i'm seeing this a lot. people, even some who are members since the beggining even, are posting on old threads with is spamming up my (and other's) alerts. and i need to explain how to tell if it's an old thread. when the forums was just re-vamped, there were no such things as an old thread since it was about a week or two old. now we are at a month and a half aproximate. the way i find an old thread is look at the date below the post. if the date is 7+ days and it has no replies to that, don't post. just let it be, don't even think about it. doing this will make the forums a lot less spammy and better for everyone. that's all i ask. just keep a look out for old threads. any questions? reply down below or pm me.
I'm not sure if this forum has this rule, but on others people can reply if their post is relevant, or if they are the original poster.
I've seen it as well. It's important that events like that are stopped. I suppose reporting the people can help... If they checked the report button reports, which evidently they do not. So there isn't much of a way to solve it unless consequences occur.
On the old forums, I only saw a ember get banned from the report button once. Once and only once. And that's because my report was a few sentences, and because the person happened to be Poof XD I feel that this should be fixed. I agree entirely. Perhaps mods can ban those who offend the rule? That way, people won't want to do it.
i've used the report button to report people. the only ones who were really banned were only spam bots :p
I suggest, if possible, an auto-lock for threads, except ones for suggestions and reports, since they will be looked at eventually, perhaps 2 weeks. Don't know if this is compatible with Xenforo, but just an idea.
Like dmuds said, don't use the report button to request locks. It takes up time where actual reports are needed to be completed. To addon, if you see that the thread is locked, you don't need to report the player who brought up the thread because by the time it's locked, a Staff member already resolved it