(25 Jan 20 at 10:12pm)The War Machine Wrote: I'm not liking the fact that you hold MPF COs to such a low regard(as I am an MPF CO myself), but if you really want to know what MPF COs actually do:
Do tryouts
Host debriefings
Approve NCO promotions
Organize mass deployments
Weed out inactive units through activity checks
Assign weekly taskings and reward units for completing them
and most importantly:
Kick out mingy units
Make their divisions better
I'm going to use my subdivision(BALLISTA) as an example as the importance of the last two duties of an MPF CO is what has kept BALLISTA alive to this day. Around a year ago, BALLISTA was suffering from a minge problem. In which enlisted units had constantly broke single rocketing rules and used their RPG as a primary weapon. This angered the resistance for some time. Eventually, they began complaining to the devs about nerfing BALLISTA. They did this...in the most asshole way possible. They, not only, gave us an RPG that had <1% mobility(you literately could not fucking move while holding it) with a reload speed about 2x longer then the RPGs current reload speed, but they also made the RPG fire rockets that had absolutely broken hit boxes. The map we were on had a big tunnel that Combine had to go through to meet the rebel forces on the surface of the city. I could fire a rocket down that tunnel and once it reached the tunnel, it would go off. Any object that was within 20 feet of that rocket made it go off. This, in many instances, resulted in the user killing themselves, because you could be firing a rocket from the entrance of an alley way and it blow up in your face. This made BALLISTA horribly ineffective at doing their job, as you had to be out in the open in order to fire a rocket at a vehicle or fortification. Eventually, the devs gave us a better RPG.
BALLISTA also had another problem, SENTRY. For a long time, they were regarded as a direct upgrade to BALLISTA. They had the exact same loadout as us, but they had more HP/AP and they had cuffs. And for a time, they took advantage of this. Mostly by encouraging BALLISTAs to leave and join SENTRY(one of the reasons I used to not like even hate NPU). This kept going on until I, a CO at the time, made a suggestion on the forums to change SENTRY along with other improvements to BALLISTA and other classes that had the RPG.
Without the COs of BALLISTA, the subdivision would not be here. Without COs, BALLISTA would still be the dead division that it was for so long. This applies to every other subdivision in the MPF and the Combine as a whole. If HELIX did not have any COs, you wouldn't be seeing Kasier hosting a Combine mass deployment. If you had no UNION COs, there would be no UNION squads and so on and so fourth.
NPU gang rule the world
Signature:
NPU JURY OfC II Poison. "You can't change whats done, you can only move on." ~Arthur Morgan, The Legend of the East.
As is mentioned above, COs kind-of need the ability to restrict entry/exit from the division in order to prevent minges from joining, and to be able to kick them out.
On a much similar note, I believe that NCOs should have the right to request that a CO come over if a RCT is being particularly mingy, and then it is up to the CO to decide if the RCT is being mingy enough to warrant a kick from the server. The fact that we force NCOs to train dumbasses and they have no ability to say "Hey guys, this RCT is a complete minge, can we do something about it?" is -in my opinion- retarded.
In fact, the above is probably the reason that more players don't want to be NCOs; the fact that they are guaranteed to be ordered to train an RCT who is a minge, and then they *have* to deal with the dumbass until the minge either gets their whitelist -after which they are basically guaranteed to RDM or spawncamp- or the minge leaves the server, thus wasting all of the NCO's time.
While I know that RCT training is also supposed to test an NCO's patience in addition to inducting new players to the server, it becomes a *massive* chore when the above occurs.
The flipside of all that, is that kicking people for things they haven't done yet is completely unfair, which is why the full decision is left to the CO who then has to go through staff to finalize it.
Yes this probably isn't the place to propose this suggestion, but I wanted to rant.
Tl:dr: RCT training is a chore and nobody likes mingy RCTs.
Thank you guys for the replies, and I'm especially grateful that you guys didn't just up and call me a retard. You guys brought up decent points, and as far as I can understand, the number one reason is because it's much easier to manage a division and keep track of who is in it. The community I was in previously had a serious MRP without tryouts for its divisions unless they were technical, and things were kept on an honor code basis. You could join GRID and HELIX with no tryout, just a 4-5 sentence app on the forum. A "technical" division would have been the equivalent of Kilo or Foxtrot, where people drive vehicles with specific controls, but mostly because the planes we had used WAC.
NPU gang rule the world
"You can't change whats done, you can only move on."
~Arthur Morgan, The Legend of the East.
As is mentioned above, COs kind-of need the ability to restrict entry/exit from the division in order to prevent minges from joining, and to be able to kick them out.
On a much similar note, I believe that NCOs should have the right to request that a CO come over if a RCT is being particularly mingy, and then it is up to the CO to decide if the RCT is being mingy enough to warrant a kick from the server. The fact that we force NCOs to train dumbasses and they have no ability to say "Hey guys, this RCT is a complete minge, can we do something about it?" is -in my opinion- retarded.
In fact, the above is probably the reason that more players don't want to be NCOs; the fact that they are guaranteed to be ordered to train an RCT who is a minge, and then they *have* to deal with the dumbass until the minge either gets their whitelist -after which they are basically guaranteed to RDM or spawncamp- or the minge leaves the server, thus wasting all of the NCO's time.
While I know that RCT training is also supposed to test an NCO's patience in addition to inducting new players to the server, it becomes a *massive* chore when the above occurs.
The flipside of all that, is that kicking people for things they haven't done yet is completely unfair, which is why the full decision is left to the CO who then has to go through staff to finalize it.
Yes this probably isn't the place to propose this suggestion, but I wanted to rant.
Tl:dr: RCT training is a chore and nobody likes mingy RCTs.
Ancient GRID CmD, prior SU Major/GB COL.
Credit to SEVIN.