It seems to happen very frequently that someone posts in an old thread and then a moderator end up closing it. What’s the point of leaving posts open if people aren’t allowed to post in them? So I think there should be system in place that automatically locks a thread after a month of inactivity. And just in case, there could be an option for moderators to keep threads permanently open.
To me it makes more sence to post about an issue in a thread that has already brought it up rather than recreating the topic to seem like a new issue when it could be a long standing one.
master threads, no necro bumbing, no double threads, and creating a new topic aren’t too logical, rules that contradict each other but it’s a issue with foruming.
Auto-locking old topics would be good for us I think. There is a good reason for not reviving older topics, I’ll quote myself from a recent topic on the subject
> If it’s been like a month or 2 months with no activity and you don’t have anything meaningful or substantial to bring to the thread, it’s probably not worth reviving. In those cases, if there isn’t a more recent and active thread, you can start a new one and link back to the old one for reference.
>
> Reasoning behind this is that information can very quickly go out of date in a topic. What happened in the Halo Game / Community 2 months ago could have been fixed, updated, become a non-issue. A lot of people tend not to read past the first page or first few pages and can quite often miss the important info. This causes confusion when old topics are revived - people think it’s still an issue, etc. So we like to try and avoid that 
> 2533274962122285;2:
> To me it makes more sence to post about an issue in a thread that has already brought it up rather than recreating the topic to seem like a new issue when it could be a long standing one.
>
> master threads, no necro bumbing, no double threads, and creating a new topic aren’t too logical, rules that contradict each other but it’s a issue with foruming.
When I made the thread, I did search around for a bit to see if it had been brought up before, but I didn’t notice any posts about it. And since it’s still a problem, I was thinking that it wasn’t discussed before, as it should have been addressed at this point. However, searching now, I found one thread about it, so I should have looked around more.
> 2533274813317074;3:
> Auto-locking old topics would be good for us I think. There is a good reason for not reviving older topics, I’ll quote myself from a recent topic on the subject
>
>
> > If it’s been like a month or 2 months with no activity and you don’t have anything meaningful or substantial to bring to the thread, it’s probably not worth reviving. In those cases, if there isn’t a more recent and active thread, you can start a new one and link back to the old one for reference.
> >
> > Reasoning behind this is that information can very quickly go out of date in a topic. What happened in the Halo Game / Community 2 months ago could have been fixed, updated, become a non-issue. A lot of people tend not to read past the first page or first few pages and can quite often miss the important info. This causes confusion when old topics are revived - people think it’s still an issue, etc. So we like to try and avoid that
Yeah, I also think there are good reasons not to revive outdated threads. So I asked it more as a rhetorical question, as I it’s always something that bugs me. However, thinking more about it, there are cases where it’s good to keep threads open, for example, if someone is asking for help in forge. If it haven’t been answered, someone can still post in it, which could also help those who find that thread later.
So another suggestion would be to notify the user if it’s an outdated thread, and that it isn’t recommended to post in it. Which could be displayed right above where you type a reply, or even as a grayed out text inside the field where you type the comment.