Forums » Suggestions

Let us bump old suggestions again!

Jul 22, 2016 Sieger link
I was just going to bump two old suggestions to gain more support for those ideas when I noticed I could not write in those threads?
I then realized it was impossible to post in old threads on here at all. Every thread with a last post older than half a year cannot be commented in anymore. This is something I never noticed. What's wrong with reviving old suggestions that were good but were forgotten about cause other stuff was more important at the time?

By the way, here are the 2 threads I think should be looked at again!:

ARF's idea for the Ragnarok bomber with 3 large ports and 2 turrets: https://www.vendetta-online.com/x/msgboard/3/26608?page=1

My Iceflare/Starflare Rocket Mk2 idea: https://www.vendetta-online.com/x/msgboard/3/30988
Jul 22, 2016 Whistler link
I wasn't aware of it either. However, an easy workaround would be to post the link in a new discussion. In many case the old threads have outdated info that is no longer relevant to the discussion. People aren't that much less likely to click the link than to look back in the thread.
Jul 22, 2016 bojansplash link
Threads are working fine. I resurrected that ragnarok one several hours ago.
Jul 23, 2016 Pizzasgood link
Threads do auto-lock, as Sieger notes, but PCC members have the power to post in them anyway, which revives the thread. That's useful since PCC threads often go unused for long periods of time between legitimate uses, as do Community Projects threads.

But just because we can necro does not mean we should. Suggestion threads from years ago are usually better off linked, so that people don't have to wade through old, obsolete discussion based on previous states of the game. The same goes for most RP threads, with the main exception being a returning author who wants to resume a story thread without breaking it into multiple threads.

My preference would be for the auto-lock behavior to be disabled on a per-section basis in the PCC, Community Projects, and RP sections, and then eliminate the PCC-member exception. I'm guessing adding the PCC exception was simpler for the devs, though.