Whitelist all command roles

[Tristan63]

Summary (a quick, 2-3 sentence summary): Since the CO whitelist has been implemented, the XO has become the new "CO" with most XOs claiming themselves acting CO for whole rounds on end. This is pretty ineffective as anyone can get XO if they want, and the occasional CO normally goes to cryo 30 minutes into the round because its boring as all hell. With this I would implement a system to lock all command roles; RO, CE, XO, SL, and Liasion respectively behind separate whitelist applications that disallows bald fucks from getting any form of control and ruining certain players rounds. On the forums a section would be opened where the CO whitelist is and change the format to one of the command roles, and a person can only apply for one command role every 2 months and have atleast 50 forum posts of meaningful length, and also have 5 reputable players/staff vouch for them. The person would be expected to know their role if accepted, or otherwise be removed with a 2 month appeal limit.

Benefits (How this will benefit the server and game as a whole): Prevent new people and space wasters from getting into important positions without the proper knowledge to do it properly. This would improve gameplay greatly in allowing tried and true players the ability to lead marines, and having more respect for those roles.

Details (Description of how you think this would work, the benefits, etc): This would probably lead to lots of debate and stricter rules and watching on these roles, leading to bigger OOC consequences should they fuck up. I think for the most part it would be a great addition and should be tested further by administration should it get accepted. I also debated on whether I should put MPs up there, but most MPs I see aren't total assclowns.

Implementation (Optional, if you have an idea how to implement it): Creating a new forum section labeled "Role whitelist applications" and have certain staff dedicated solely to keeping track of the various whitelists and making sure they aren't ruining rounds on a regular basis.

[McRipfist]

Must agree that the lack of active COs has lead to them being cut out of the standard CM round. Sadly with an already inactive Commander position, we cannot afford to whitelist all the Command positions.

[Helgraf]

^^^^^

[Jaketeaking]

-1. Nope. you yourself have said one of the issue's, with the XO basically becoming the CO. Because nobody plays the role of CO, because of the pain of having to go through a process of approval and denial. in addition, i just find this to be an ill thought out suggestion.

[NoahKirchner]

NOOOOOOOOOOOOOOOOOOO PLEASE DEAR GOD, NO!

I can understand time locks, even a CO application process to an extent as much as I hate it, but this is going to do the /exact opposite/ of what you want it to do. Instead of having bad ROs, XOs, etc, you're just going to have far fewer.

Applications are also going to be a nightmare, you'll have to have 5 more applications that need to be constantly monitored, voted on, et cetera, and you'll have to add all of those names to the whitelist .txt for each individual person that wants to play roles as minor as "RO" or "CE". Even in the event that the manpower is there to be able to handle this, you then have to deal with the fact that the whitelists are going to very quickly turn into popularity/robust-ness contests, as they have with the commander applications, as opposed to systems for rooting out baldies, and all it's going to do is push the problem downstream. Sure, you won't have any more terrible ROs messing up a round, but you won't have /any/ ROs, and the CT that has to take over will have less of a chance of having a boss, and more of a chance of having to lead a department on his own.

The way to teach people to play roles is to give them the ability to ever play with people working above them, not to make people have to jump through hoops to ever be able to get into those positions, even if they already know how to play.

I cannot stress this -1 enough, please dear fucking god no.

[McRipfist]

The issue with timelocks is that they can be by-passed by joining the server once, leaving for a few months or even weeks and then returning as new as the first day and being able to roll for CE, CMO, XO, BO, MP, CPL, SGT/SSGT and CL.

[NoahKirchner]

The issue with timelocks is that they can be by-passed by joining the server once, leaving for a few months or even weeks and then returning as new as the first day and being able to roll for CE, CMO, XO, BO, MP, CPL, and CL.

Sure, it's not a catch-all by any means, and it can be abused. However, if someone leaves for a few months and then comes back, they've likely been playing other servers in the mean time, and as such a time lock is really not required.

This would also require a SQL database which CM doesn't currently have set up to log time played to my understanding.

[Tristan63]

I personally would prefer fewer ROs, CEs, and SLs, than have many shit ones.
Also if you open it as its own forum and hire more people soley dedicated to managing whitelist, it wouldn't be as terrible as you think.

[Feweh]

This is illogical

[Tristan63]

This is illogical

Mr. Spock, if we do this it could encourage more people to come to the forums and sign up for roles. This would also increase the community size overall and filter out shitlers from important roles. At first it would hinder the marines greatly, but with the added staff for whitelist management it would make CM great...greater!

[Feweh]

Mr. Spock, if we do this it could encourage more people to come to the forums and sign up for roles. This would also increase the community size overall and filter out shitlers from important roles. At first it would hinder the marines greatly, but with the added staff for whitelist management it would make CM great...greater!

Or more than likely, wed never have any command staff.

[McRipfist]

I see where he's coming from with the forum use thing. But yeah, it can either lead to a skeleton-crew on the Sulaco most rounds or a booming forum and equally booming Sulaco.

[Swagile]

No.

You will just have no Command roles for rounds on end, or very few being overstressed due to a lack of Command and then quitting said roles due to over work.

And so the cycle continues.

[Tristan63]

You guys did notice I didn't have BO under this umbrella??
That qualifies as a bridge-role.

[Swagile]

CT would become the new RO.

BO would become the new XO / CO.

MT's would become the new CE's.

Specialists would become the new SL's.

We've seen this happen with XO being the new CO since we barely have any CO's on most of the time, and the same will happen to every other role.

[Clutch]

fuck no

[Steelpoint]

Multiple times I've stepped up to play as the XO in a round where we have no CO, and one never joins.

If anything, I think the XO is a better role than the CO. The XO has no whitelist restriction, slightly lower expectations and the XO spawns with great weapons (Revolver and 88 Mod 4) whereas the Commander just gets a M4A3 Pistol reskin. Otherwise the XO is identical to the CO sans the XO is more likely to spawn in due to him not being whitelisted.

[Snypehunter007]

I'd deactivate myself at the amount of problems this would cause.

Also, we are probably not going to hire forum-based staff unless there is excessive need for them.

[halo9663]

This suggestion is pointless and do not bring any advantage.
-1

[Renomaki]

Since the CO whitelist became a thing, COs have been a lot less common as of late.

If we whitelisted every command staff role, we'd end up with hardly anyone leading the marines, and RP would go out the window because there would be no one in the higher-RP roles anymore...

[Snypehunter007]

This is pretty down voted and unnecessary.

Asking this to be locked.

[Jeser]

I understand why you suggested that, there are some problems with XOs sometimes, but if we do this, instead of 3-4 people in Command and absent CO we will have 1-2 people in command. Not good. -1.

[shyshadow]

As if people have a good enough reason to be command why make so you HAVE to apply for every single one? That's redundant and repetitive, heads already are busy dealing with the two only whitelists, I doubt it will be easier on them when there's 8 Whitelists.

[Bmc777]

Not going to happen, see the feedback of others for the reasons why. Denied.