Forums | Chat | News | Contact Us | Register | PSU Social |
PSU: Moms Like You Choose PSU
Forums | Chat | News | Contact Us | Register | PSU Social |
Home | Forum | Chat | Wiki | Social | AGN | PS2 Stats |
|
|
|
Thread Tools | Search this Thread | Display Modes |
2014-11-23, 05:28 PM | [Ignore Me] #1 | ||
Private
|
(This outfit is for Connery server only)
My outfit, The Blazers First Strike Infantry, is a new outfit, and I will be blatantly honest from the beginning: it is not for everybody (but please feel free to join and at least try it out). I personally am a military nut (no I don't obsess over guns, or tanks, or whatnot), and therefore, my outfit is following a military layout. Meaning you have to earn your rank of private, then member, then officer. Be warned, it is not easy. The outfit WILL be a fun and rewarding outfit, however, you are expected to follow a few rules while you're in. The rules aren't complicated, and there are only a few.
Those are the only 4 rules I have. Of course, they probably will change, a rule or 2 might be removed, or more added to as time goes on, but hey, I can't help but to perfect it. For those interested, the outfit name is [NBRG] The Blazer Specialization is: Combined Arms Classifications is: Competitive ------------------------------------------------------------------------------------------------------------------------------------------------------------- As of November 23rd, 2014, the prerequisites to joining are:
The promotion scale (the prerequisites to be promoted from recruit to private, private to member, and member to officer) are as follows:
CHAIN OF COMMAND. THIS IS VERY IMPORTANT. As mentioned above 1,000,001 times, I follow real military layouts. This means that I, as a leader, CANNOT tell a recruit what to do. If I did, the recruit has full authority to disobey me and not be punished. If I want a recruit to do a certain thing (say, for example, to spawn a MBT and cover me while I drive a sunderer to a hotspot), I must tell the officer that particular command. The officer then tells the member. The member tells the private. The private tells the recruit. The recruit then spawns the MBT. This also applies the same, going backwards. If a recruit has an opinion, a complaint, or whatever, he tells his commanding private. The private tells his commanding member. The member tells his officer. The officer tells me. I relay my response back down the chain of command. Now, you're probably saying "this is a horrible idea. During a large battle, nothing will be achieved, because everyone will die before they get their orders sent down the chain, or their suggestions sent up the chain." My response is quite simple: That layout will likely not be followed during a large battle. If it is a large battle, everyone in that battle is the same in my eyes. A private could directly order me to change class to a light assault and flank the enemy, and I'll probably listen to him. Same going backwards. In a firefight, the layout will likely be ignored, as it is indeed, time consuming. ----------------------------------------------------------------------------------------------------------------------------------------------------------- Last thing I need to mention. For anybody wondering as to what I said above about how a recruit must report to a private, a private reports to a member, and so on. Depending on how large the outfit gets, because many people will likely be accepted everyday, and a few kicked everyday, a recruit will have no authority over anybody. A recruit cannot tell another recruit what to do, etc. A private will likely only have authority over 10 or so recruits. A member will have authority over 10-15 privates, and an officer will have authority over 5-10 members. Now, if the outfit grows to have, say, 250 members, then a private could have authority over 25-30 recruits, a member over 15-20 privates, and an officer over 30-35 members. COMMENT BELOW FOR ANY QUESTIONS. PRACTICALLY ANY AND ALL APPLICATIONS WILL BE ACCEPTED. Last edited by JosephKuraii; 2014-11-23 at 07:48 PM. |
||
|
|
Bookmarks |
|
|