Choosing to ignore points being brought up is not a good way to go about server suggestions.
Leaving lore aside, as you choose, that still leaves that model =/= job.
As the example for the last suggestion where they wanted to give all Commanders DC-17s because they were either higher ups or had the bodygroupers.
Bodygrouper =/= Getting it in-game. Ex. Just because you have DC-17 holsters doesn't justify giving you DC-17s to spawn with, you need more reason to back it up.
The models were made with no background detail, considering GC just looked like regular 212th. They are fiction in looks, so we can't take their looks as value nor what they should receive based on it.
You choose to make GC require ARC, that's fine. You have a GC ARC T rooper, alright, may as well get the ARC set-up for the GC ARC Trooper.
GCC requires ARC? That's cool too but you want the ARC set up too? Well, he's not an ARC Trooper, you just require that per choice of the Battalion.
The model is ARC? Well, the model is literally made up. By that logic, when someone gets their models re-worked they can ask all models have a Medkit and ask all their jobs had Medkits - is that not broken? Sure, the example is extensive but you get at where we're going.
Originally, we were just bringing up our points but there's been so much back and forth talking that things just continue to escalate.
This is my opinion, my -1 stands and will stay solid considering the biggest excuse as to why it's ARC is that it's an ARC model on a custom made model.
EDIT:
See, same argument again. It has moved up that we're no longer going against it because you require to have ARC but rather that the ARC model is custom made with little to no background to go off on. For all we know the modeler made him ARC for the hell of it; so in our view it doesn't justify it getting ARC benefits. Requring ARC for positions is fine, that still doesn't mean you get the benefits of an ARC loadout unless it's an acual ARC job (as represented by the server/Devs, not the Battalion itself).