FULL RP Name(s): A: USMC FH SGT/RECON PVT Shogun, EOW REAPER 07 0721
Discord Username: A: Minishogun721#4983
Steam ID: A: will edit later
Workshop Link:(If applicable) A: N/A
What is your suggestion? A: Give NCO (SGT and beyond, 03 and beyond. Not too familiar with new combine NCO structure)
How would this benefit the server? A: 2 things.
1. Eliminates the huge downtime for new recruits, also allows the trainer to show some weapon mechanics
2. Makes the server look good and efficient. First impressions are everything, and if a new player sees an NCO begging in text, it makes CVR look like a discordant mess.
Now, what if it got abused? I don't know if you can only have both whitelist and blacklist command, or if you can toggle someone to have one and not the other. If it's the latter, that eliminates a lot of abuse potential. If it's only both allowed, it's simple. Any NCO that messes with the system under any circumstance would be punished severely.
Whitelist access is related to both
A) Current WL (Ex. COs can WL for their class and RCTs)
B) Current ULX (Ex. some Staff can WL for any class)
Ranks are logged in-game as a part of your name which would be very hard to properly regulate and would expose the server to anybody who knows that name formats give you access to whitelist perms. Creating a new ULX specifically for NCOs would be hell to regulate, just look at how ENG ULXs are regulated and how many more total NCOs there are than GRID/ENGs.
A: USMC FH SGT/RECON PVT Shogun, EOW REAPER 07 0721
Discord Username:
A: Minishogun721#4983
Steam ID:
A: will edit later
Workshop Link: (If applicable)
A: N/A
What is your suggestion?
A: Give NCO (SGT and beyond, 03 and beyond. Not too familiar with new combine NCO structure)
How would this benefit the server?
A: 2 things.
1. Eliminates the huge downtime for new recruits, also allows the trainer to show some weapon mechanics
2. Makes the server look good and efficient. First impressions are everything, and if a new player sees an NCO begging in text, it makes CVR look like a discordant mess.
Now, what if it got abused? I don't know if you can only have both whitelist and blacklist command, or if you can toggle someone to have one and not the other. If it's the latter, that eliminates a lot of abuse potential. If it's only both allowed, it's simple. Any NCO that messes with the system under any circumstance would be punished severely.
A. The Whitelist you are on
B. Your ULX Rank.
As much as I would love to see this, I don't see it happening any time soon
Bore is dead
Secretly a Staff Main
Whitelist access is related to both
A) Current WL (Ex. COs can WL for their class and RCTs)
B) Current ULX (Ex. some Staff can WL for any class)
Ranks are logged in-game as a part of your name which would be very hard to properly regulate and would expose the server to anybody who knows that name formats give you access to whitelist perms. Creating a new ULX specifically for NCOs would be hell to regulate, just look at how ENG ULXs are regulated and how many more total NCOs there are than GRID/ENGs.
Ancient GRID CmD, prior SU Major/GB COL.
Credit to SEVIN.
Locked/Moved.