Originally Posted by
ThatOneDeveloper
It's not just competency, it's dedication to the role. That's why a timelock doesn't work. A timelock would never work for a role like CO, and definitely not Synth or Predator.
There are three kinds of timelocks, and none really help here:
Locked by playtime: Bad idea, especially since each whitelist is for a specific specialization (CO is leadership, Synth is support, Predator is combat). Baldie McBaldFace the PFC can roll for synth given enough time if we used a timelock system. A synth requires knowledge of engineering, chemistry, surgery, medicine, and requisitions. Predators need to understand the lore incredibly well and RP well. Commanders also need to RP well and should be good at organization and fast thinking. All of these skills can easily be checked through a whitelist application; not so much through an automated timelock system.
Locked by playtime for a certain job/role: Though this would be the best option if we decided to make things timelocked, timelocking is in general a bad thing to have for the roles we're discussing here, as I mentioned below.
Locked by account age: Easily the worst option, a newbie can show up once, come back a month or so later, and then role CO or something. Easily the least-effective way to timelock things.
And timelocks still won't keep the one thing that whitelists were made to prevent: griefers. A Mateba would be a griefer's dream, as well as the ability and authority to toy with the entire marine force. Synths, being incredibly durable, incredibly strong, and incredibly skilled could also wreck havoc. And predators... open to griefers... oh god....
Whitelists are meant for players that shown their dedication to the community, commitment to make the round fun for everyone, and possess the knowledge and skills required to fulfill these roles. If they fail to do this, they get ousted. That simple. It's easy to have a knee-jerk reaction after a bad experience with a whitelisted role and say "REMOVE WHITELISTS!", but it's really not the most productive thing to do. Whitelists are here to stay. If anything, the whitelist application process needs to be changed, not the whitelist itself.
Also, regarding stories for COs: I personally think it's a step in the right direction for CO applications. Previously, CO whitelist applications hinged on how much you were known / how much you were liked in the community, and applications in general were based on the player's community rep (as well as how much you were seen in command roles by other people, which meant if you played during deadpop hours, RIP). Stories are a great alternative way to show your dedication to getting the whitelist, your command style and how your character interacts with others. It also raises the bar for CO applications, which is a good thing.
Anyway, rant over. Gotta study for my AP tests now.