|
Loading...
|
 |
||
 |
||
Black Widow Company PlanetSide SOP | ||
|
Black Widow Company Standard Operating Procedures (SOP) Read this, and post your acknowledgement of understanding. NO ONE is above the SOP. There will be no other replies, and any made will be deleted. The only exception to this rule is if you have a question or an issue with anything listed below. In the event of a question/issue, please quote the section and someone will clarify. Basic Expectations BWC is a military-style outfit. We define ourselves as such for various reasons- we have a dedicated chain of command that we expect to be followed. Legionnaires are the senior-most NCOs of the company- they are not officers but they have the same authority, granted by the BWC Commanding Officer. They also have the same responsibility towards conduct and professionalism. BWC also features a rank structure and a Battle Decorations Program. We also define the concept of working together in ways that few outfits can match. BWC is an elite outfit of highly-motivated, highly-dedicated, highly-trained players. We are proud of who we are and we will not hesitate to hold you to the same standards. There are TWO basic rules for being in BWC. -- ONE- *ALL* members are expected to be in the appropriate BWC Operations channel on the ULTRA Alliance Teamspeak server before you log into the game. It doesn’t matter if you have a microphone or not. It does not matter what game you're in - if it's a BWC-sponsored game, you will be on our TS server. -- TWO- Forum registration and participation is a must. The SOP is duplicated in several spots - this copy is the one that you will be required to sign once you’ve been admitted to BWC. Admission requisites include registering for the Operations Server and getting a Fruitsalad 2.0 signature image set up in your forum signature. When you become part of BWC, which would mean you're associated with BWC in a game that we play or you're part of the forum community with general membership access, you are beholden to the same rules as the rest of us. Yes, Planetside is our current main game. But it is not the only game we play, and therefore when you play with BWC, you play by BWC's rules. Just because you only play, say DDO for example, doesn't mean you're not allowed to break rules that are associated with the whole of BWC. And if it's not in a Company-specific section at the bottom, then you WILL follow these rules. The standards that we apply to all of BWC apply to you - otherwise you are not in BWC, so leave the forums now. Company-specific standards apply to those members who are playing that particular game. I. Participation Black Widow Company [BWC] encourages each member to participate 100% of the time and try to attend all meetings/Ops if possible. We understand that there is more to life than devoting most of your time to a game. All we ask from you is to at least try to attend one mandatory meeting/mission per week to satisfy participation requirements. We also require you to check in frequently on the forums regardless of your participation-level, in the form of indicating your presence at operations. When you are online, you are expected to participate with BWC squads- if you didn’t want to be in the Company you wouldn’t have joined. It is perfectly acceptable to solo once in a great long while, if you feel like goofing off because you won't be online very long. During operations nights, we expect all online members to be in a BWC squad, no exceptions. If you have friends who play and you want to hang with them, then either have them join BWC or join our squad for the evening. II. Attendance A.) Attendance Post In the BWC attendance is vital in our ability to function as an elite unit. All members are required to register on the Operations Server, located on the website. Signing up for every operation is not necessarily a requirement - you earn promotion points for signing, that's your reward for doing it. However, Operations planners and Mission Commanders may opt to specify that you cannot attend if you haven't signed up for an op. You're S.O.L. if you don't adhere to that requirement. In addition to your signing in, the squad leaders and operations commander of the OP will be responsible for also taking attendance during the OP. In order for a member to get full credit for participation on Op nights both the sign-up for the op on the Operations Server and the OC’s attendance rosters must match. B.) Absences The Leave of Absence (LOA) policy is as follows: -- If you plan on being inactive for a period of time to exceed 15 days, post an LOA. If you don't know how long you'll be offline or out-of-game, you need an LOA post. -- You must be logged in at least once every 15 days. Logs of TS activity and in game stat tracking will be used to make the determination of attendance. Consequently, BWC's policy is that anyone who shows up as having 16 or more days absence without a posted LOA will be automatically and unapologetically kicked from the Company. -- LOAs are only valid for 90 days, unless extenuating circumstances such as crippling disaster, military deployment or job-related temporary transfer apply (ie, an Extended LOA). Generally, after one year, if no contact has been made, we consider your Extended LOA invalid. Essentially what this states is, if you or your alternate character have not logged in for over 15 days and there is no LOA post, you will be booted from the Company. You are free to reapply, provided you maintain an active account. If you earned the Legion of Honor, you may enter BWC at the rank of Legionnaire at the discretion of the Company Commander. Otherwise you will be readmitted to BWC as a Recruit. The bottom line is, no LOA post - no immunity from the boot. Our attendance rule exists for two reasons: To help the command staff determine eligibility for promotion, and to determine what resources will be available to the Outfit when operations are being planned. The Commanding Officer of the Outfit is very flexible with the attendance rule and he understands that some members will be unable to attend due to vacations, family emergencies, illness, etc. The CO asks only that you keep the Company informed as to your status and that you post notice of your expected absence (for any reason) in the Leave of Absence Forum. The CO/XO will reply to your thread acknowledging your status. Members who post in the Leave of Absence Forum for leave can return to the Outfit without penalty of being busted in rank or dropped from the roster. weeks missed/action taken 1 weeks - Warning Letter/Inactive Status 2 weeks - Removal from Outfit and forum usergroup C. Status Members are classified as being Active, On Leave, or Inactive. A member's status is posted in the Mission Attendance roster, the member's profile, and the Team page where the member is assigned. -- a.) Active - A member who attends 1 or more meetings/Ops per week is considered to be active within the Outfit. -- b.) On Leave - A member who has posted there status in the Leave of Absence Forum will be given this title. No penalties will occur for these individuals while On Leave. -- c.) Inactive - A member that misses 1 week of Ops without posting in the Leave of Absence Forum concerning their status is considered to be Inactive. Members who find themselves on Inactive status have 1 weeks time to get in contact with the CO/XO in order to keep his/her full membership. Members who fail to do so after that time will be removed from the Outfit. **Note - those who are dismissed from BWC for inactivity are eligible to rejoin the Company at any point, at the rank of Recruit. Those who previously held the rank of Legionnaire or were inducted into the Legion of Honor, and retire from BWC, are eligible to have their rank reinstated. III. Battle Decorations A) Promotions 1) Promotions within the enlisted ranks are based on three factors: Seniority, Attendance, and Medals earned. Points are awarded to each member based on their achievement in these three areas. A certain number of award points is required to be eligible for each rank. Members who have obtained the minimum number of points to be eligible for higher rank must apply for a promotion. Promotion request process: 1) A PM must be sent to your task force detachment commander or your XO 2) Det-leader or XO will then Courtesy-Copy it to your TF NCOIC/1SG and pass the request up for review to the Company XO. 3) Company XO posts in the Officers Awards Discussion forum. If the NCOIC/1SG provides input, that is to be forwarded for input. 4) Officers have 24 hours to provide input. Silence is Acquiescence. This keeps all knowledgable personnel involved. 2) The Promotion Points system is a structure which will allow for blanket competitive promotions. Not all members are expert shots or kill-junkies. Members may augment their Promotion Points by earning skill badges and tabs, ribbons and medals, and otherwise distinguishing themselves on the battlefield aside from massive amounts of kills. Each of these features allow for Promotion Points, which will assist in the overall goal toward promotion to the next rank. Awards will now take the place of most “meritorious promotions”. Meritorious Promotions are still possible, but they will be very very rare. You are advised to simply fulfill the requirements for promotion, due to the rarity of such promotions. 3) Training Sessions & Promotion Points -- a) - This is the official word. Consider this carved in granite. TRAINING DOES NOT COUNT FOR PROMOTION POINTS. TRAINING SESSIONS DO NOT COUNT FOR OPERATIONS. -- b) - There are three types of events on the Ops Server: Training, Field Training Exercises (FTX - non-standard training), and Operations. B) Rank Brackets 1) Officer Ranks -- Officer ranks are administrative in nature, and indicate a person who is an officer-in-charge of a particular unit with BWC, or holds a senior staff OIC position (such as S-1, S-3). Officer ranks are meritorious, and are only commissioned when a duty position is available. When a person steps down or is relieved of an OIC position, they return to the enlisted rank from which they held before they were promoted. 2) Legionnaire Ranks -- Legionnaires are the pinnacle of Leadership, the enforcement arm of the commanding officer's executive authority. They are promoted meritoriously from any rank and have earned distinction by being inducted into the Legion of Honor. Legionnaires are the penultimate senior NCO rank and best exemplify the traditions of leadership and mentorship. The Sergeant-Major is the chief Legionnaire and the duty position is filled from the ranks of the Legionnaires. Legionnaires who go on to serve as officers are promoted to Legionnaire-Officer status unless serving at higher command levels. 3) Enlisted Ranks -- Members of BWC enter the Company at the rank of Recruit. They must complete a series of requirements in order to gain promotion to the next level. This progression is outlined in the BWC Awards forum, and is entitled the "Promotion Points System". Promotions range from Recruit to Staff Sergeant via points, and promotion to Sergeant First Class (SFC) is given to Staff Sergeants [and Master Sergeant (MSG) is given to Sergeants First Class] via merit and by authority of an officer promotion board. These two final ranks (SFC & MSG) may not be earned via points. -- The position of First Sergeant is equivalent to Master Sergeant, but this position is filled from any rank. The First Sergeant is "frocked", meaning they are given the duty position of 1SG and are treated as a senior NCO. They will wear the rank insignia of a 1SG and be afforded due respect given any senior NCO. When they vacate that position, they return to whatever rank they held previously. Generally, if a Legionnaire fills the 1SG position, he/she is still a Legionnaire, but they will wear the 1SG rank insignia. They are still afforded the same respect as a Legionnaire, under all circumstances. C) Promotion Points System The system BWC uses to judge promotions is adapted from US Army promotions procedures. The points are revised on a monthly basis, and are generally published on the 1st of every month. Therefore, the Awards Forum promotion thread should be updated once a month by an Admin. IV. Common Procedures A.) Forum Profiles 1) Your rank icon is not an avatar- it is a set “forum title” that comes with an image. You will be given one based on your in-game rank. If yours has not been squared away, simply notify an officer or the Outfit Sergeant Major by private message. Forum signatures will consist of the following as a minimum: 1x (ONE) Kazpoint Fruitsalad 2.1 signature image At the max your signature may contain the following: 1x (ONE) Kazpoint Fruitsalad 2.1 signature image or game-specific banner 1x (ONE) "signature banner" image (rotators do not count as multiples) 1x text-message B.) Squad Conduct -- 1) The BWC squad leader is the absolute authority for orders. It does not matter if the Squad Leader is the CO, XO, Lieutenant, Legionnaire, or a new private. When that SL tells you to do something, you do it. When you click “OK” after the invite, you are submitting to that authority. If you do not wish to squad up and receive and follow orders, don’t join. In fact, don't join BWC at all - BWC is a squad-based, team-based outfit. We succeed through organization, coordination, and teamwork. If you're a Han Solo lone-wolf, or you think you're Dirty Harry or Maverick, then you belong in another outfit because BWC does not tolerate that crap. -- 2) DO NOT QUESTION ORDERS. It will not be tolerated. Nor will we tolerate disobedience. All members are given a chance to lead, and the Outfit Command will not have that authority superceded by your personal motivations. The squad leader’s word is law- it all boils down to simple respect. Members who disobey a squad leader’s orders can be expected to be kicked from the squad, and they will not receive sympathy from the Company command. This does not mean you can't propose an alternative if you think there is a better way. But this is to be done as discretely as possible through /tell's where possible. Do not contradict a squad leader's orders in any level of chat or on Teamspeak. Send them a /tell if you have a better idea, or if you wish to ask "why?". If the game's interface does not include a method for sending a typed /tell to the squad leader then you will set up a whisper to the channel commander in your TS channel. -- 3) When your squad is conducting operations, be where you need to be. Members who cannot join the squad due to a 'population lock' or a full server will be given additional instructions. Find out what you need to be doing. We do not tolerate lone wolfs or Han Solo-ing. The squad is a team, not a fountain for XP and fame. SQUADS STICK TOGETHER. We have defined tactics in this Company- learn them, know them, use them. -- 4) If you have a suggestion or problem with an order that the SL gives, take it up with the SL in a /tell or a TS whisper. Do not air your dirty laundry to the squad, platoon, or Company. The same goes for Teamspeak. Do not be insubordinate or disrespectful- if you think you have a better idea, simply say "I have a suggestion" or send a /tell or whisper requesting clarification. Once the SL has heard your suggestion and makes a decision, don't be rude- either follow the order or leave the squad and politely explain your reasons for doing so. RESPECT is a two-way street. C.) Forum Conduct -- 1) Keep your flames and rants to yourself. We don't care if you get pissed. Everyone does, everyone has a bad day. If we all acted on our anger, this forum would be filled with thousands of rants. Flaming and ranting towards a member of the Company will not be tolerated, regardless of whether it is implicit or explicit. This means whether you name the person or don't, it WILL NOT be tolerated. If you have an issue with a member of the Company, your first move is to inform them via PM and try to resolve it at the lowest level (your "sent box" maintains records of what you sent, keep them in case it gets out of hand). If that does not work, use your chain of command. Talk to a Legionnaire. If a Legionnaire cannot solve the problem or recommends you take it to an officer (SL, XO, CO) then follow that advice. BWC is a family, a community of friends- we do not wish for people to leave because of disputes. -- 2) Profanity is fine. This game comes with a rating for Teen audiences and maturer players. BWC will not be held accountable if your mommy or daddy hears the F-word and doesn't like it. We do not expect people to suppress their rights to free speech simply because you're not old enough to understand what "blankety-blank" means. BWC does not censor its language, and when you click on the OKAY for the User Agreement, you are recognizing the fact that these games have a Teen Rating and you are entering a somewhat adult world where there is violence and uncouth language. If your kids play the game, then you authorized consent for them to see and hear whatever goes on in-game. HOWEVER - BWC respects its members and we will do our best to tone down the language upon individual request at that point in time. -- 3) Racial, ethnic, religious or sexual slurs are absolutely forbidden, regardless of the offender's orientation. Meaning we don't care if you're Jewish and making "jew-jokes". Others will not find it funny, and the Company command will not hesitate to send you packing. This single offense is grounds for immediate banning. It does not fall under the "Three Strikes Rule". This will not be tolerated on the forums, on Teamspeak, or in the text-based communications in-game. This does not mean you cannot say what you wish- you're free to say whatever you want. If it crosses this single line, we'll say what we want- and that will be "Goodbye". Now, if a member has a problem with something you said but doesn't include Item Two, again- don't air your dirty laundry. Take it to /tell or forum-PM. -- 4) Public Forums are public. All BWC members are expected to conduct themselves civilly on all public forums. It does not matter if you don't care- BWC cares. This is a team, not a free-for-all. BWC has a reputation of being outstanding members of the online community, and we are well-known in-game for being proper gamers. You agree to become part of that civilized community when you join our ranks. And we agree to kick you out of the Company if you break that reputation. D.) Outfit Conduct, Discipline and Teamspeak Conduct -- 1) Outfit Conduct All BWC members are expected to conduct themselves professionally at all times, regardless of rank. You will be respectful of all members, and you will be afforded that same respect. Violate it, and your respect will be taken away. It's that simple - team effort, not free-for-all. All members will refrain from engaging in unprovoked or gratuitious TK wars. TK'ing Company members and other allied players WILL NOT be tolerated. If a non-Company member TK's you, you will ask for a reason. If you accidentally TK someone, send them an apology /tell. You are required to set the example of what a model troop is. Do not fall to lower levels. Do not fire warning shots, as this will only provoke those who lack intelligence. If anyone endangers the mission objective or goes against the mission goals or the set objectives, or disobeys Command Rank orders to NOT destroy key battlefield assets, you are authorized to protect the mission through discretionary use of TK and/or other methods UPON OFFICER/LEGIONNAIRE APPROVAL. -- 2) Discpline BWC operates much like a military unit operates, because this is the best system available. Therefore, we expect you to follow our rules. During your recruitment process, you were informed what some of those expectations were, be they for Planetside, BF2, or any other game. While you are here to play games, BWC is also a community of family and friends. There are expectations - if you fail to meet standard, you are dismissed from BWC. Therefore, BWC operates on a three-strike rule. Strikes are documented on the Wiki. After a six-month period, strikes are erased. Serious violations of the SOP may result in immediate dismissal from BWC. Quote If you witness an SOP violation, you may report it up your chain of command. SOP violations are handled by C&S potentially in the form of a "strike". Any strike, or strike recommendation from a NCO, should be posted in the soldier's Company C&S forum so that the soldier's C&S can provide input if necessary and be alerted of the situation. If it is deemed that a strike is warranted, then that soldier's TF CO should issue it (or Company XO where applicable). The officer should tell the member why they are getting it and give some constructive advise on how to solve the issue. This allows the person receiving the strike to feel more comfortable venting his opinion and will probably take the strike better. -- 1) Strikes may only be issued by members of Command and Staff. Outfit members can report something to a member of C&S for investigation, but generally there are enough members of C&S that are online anyway. -- 2) Strikes may be erased after six months of proper performance, provided the strike is not for a serious offense. If a strike is given for a prior offense of the same nature, the previous strike counts. * Example: if PVT Firefly calls CPT Zanduar a fuck-face piece of shit, but six months and one day later has not said anything, Firefly is in the clear and the strike is basically "absolved", aka forgiven but not forgotten (hence the tracking). If PVT Firefly then calls Zanduar a fuck-face piece of shit, Firefly is issued a Strike Two at the very least. If anything else happened between now and then, then it's Three. -- 3) C&S members who issue a strike, but are not the soldier's superior officer, must alert that soldier's officer-in-charge. i.e., if PVT Firefly is being given a strike by SSG Cord for calling CPT Zanduar said name, then SSG Cord must notify LT OptimusPrime as Firefly is a Ranger. We trust that SSG Cord either saw the entire incident, or has checked with both Firefly and Zanduar to see what the story was in case Firefly had justification (must be valid justification, such as Zanduar said to call him the name). The incident needs to be documented on the C&S forum, so that everyone is aware. -- 4) In the case of the strike being issued by the soldier's superior officer (ie TF CO), the issue needs to be documented on the C&S forum. -- 5) In the case of a senior officer (ie, Battalion cadre... Rabbit, SniperSteve, Kurael, Firefly, Zanduar, AntiG, Pilto06) issues the strike, the incident is documented on the C&S forum and the soldier's OIC (TF CO) is notified. -- 6) Upon accumulating three strikes, the individual in question is dismissed from the outfit. This ensures that: * The incident is documented on the forums (and possibly the Ops Server if UP can/will do so) * The soldier's OIC knows about it -- 3) Teamspeak Protocol Teamspeak is a tool to assist BWC in maintaining an effective fighting force. It is not your personal cellphone. Communications procedures are quite simple- if it does not pertain to the mission, don't say it. Think before you speak. The rule of thumb is, "Is this really necessary?" or "Can I type this instead of saying it?" Channel Command is a Teamspeak feature that is reserved for officers, platoon leaders, squad leaders, and fire team leaders. All soldiers are required to bind a key to Activate Channel Commander, and all soldiers are required to bind a key to Whisper to Channel Commander - because YOU may be given the role of SL. Do not engage Channel Commander if you are not in a leadership position. It only adds to the confusion. Because of BWC's relation within the ULTRA Alliance as a prominent and active member of the alliance, all members within a squad leader, platoon leader, or officer-in-charge position are required to activate Channel Command. There are exceptions, and BWC officers (and BWC officers alone) may make a command decision to turn their channel commander off. Quote TEAMSPEAK COMMUNICATIONS PROTOCOL 1a) All BWC members will bind a key to "Activate Channel Commander" and they will bind a key to "Whisper to Channel Commanders". Instructions on how to bind these keys should be instructed at BTI Phase One. 1b) During Primetime operations (when the SL/PL policy is in effect), only the OIC and the SLs need to have Channel Commander on. Anyone else needs to turn it off. C&S members no longer need to have Chan-Com activated. During normal operations (non-primetime), the SLs should have Chan-Com on. Only an officer may make the determination to turn off Channel Commander. The only person who is to TRANSMIT on Channel Commander is the OIC or a person of the OIC's designation. The exception to this is when squads are in separate channels - SLs may need to reply via Chan-Com. 1c) All soldiers should know their squad color (Gold, Purple, Orange) and their squad position number in the squad, and should be stating them in all voice communications. It makes it easier to find you on the map and squad bar. Unless the soldier is not in a squad, there should not be soldiers using their names during transmission. 2a) The SLs will maintain strict No-Transmit policies as a default. BS chatter can go to the AFK/Break Room or one of the Task Force channels (see 3a). All unimportant conversations now go in the appropriate in-game text chat box. 2b) These rules do not apply when five or less personnel are online (Five-Person Rule). They do not apply for operations that call for loose comms (command approval warranted), or during Training (example: during BTI Phase One). They also do not apply in Task Force channels except when specified by the OIC. Task Force Channels generally are not to be used except during operations that call for the TF breakdown, or when the OIC details a section to break away from the main group. The aforementioned exceptions aside, these rules apply in the main channel at all times. 3a) Anyone wishing to transmit on Teamspeak needs to key the mike, pause and state their squad color and squad number, and say "Break". Such as in this example: Code: This is Gold Six, break. They will then proceed with the next part of their transmission unless otherwise told. The ONLY exception to this rule is the Emergency Comms rule (see 4b). 3b) The OIC or PL may interrupt at any point during a regular (non-emergency) transmission and ask for comms to be cleared. In this case, the transmitting squad member is to cease transmitting until the PL has stated that he is authorized to resume. No other squad member may make any regular (non-emergency) transmissions once the word "break" has been said until that transmission has been completed (once the word "over" has been said). This means that if a transmission was interrupted by the PL, then all squad members must wait until that transmission has been both allowed to resume and completed before making any regular (non-emergency) transmissions (when the PL clears comms, everyone shuts up). 4a) The person requesting to transmit will keep their transmission relevant to the game at hand. When they are finished, they will say "Over". 4b) Emergency combat-related transmissions override all regular transmission rules. Emergency transmissions may be made by any squad member at any time. If an interruption of regular communication is required, the sqaud member making the emergency transmission will preface it with the word "Break-break!" Everyone, including the PL, is to cease transmitting once the "Break-break" has been said. An example of a transmission that would be classified as an emergency would be a warning of an imminent threat. However, there are no set criteria for what qualifies as an emergency; squad members must use personal judgment. If this ability is abused, permission to transmit can be temporarily revoked and disciplinary strikes may be issued. 5) The SL will start his/her reply by stating his/her name, since not everyone can do voice-ID. The SL will end his/her transmission with "Over", to inform the group that he is done speaking. This is done for continuity - all personnel, including squad leaders, will first identify themselves by squad color and squad position (ie, Gold Two) before speaking. 6) No C&S members are exempt from this policy. At no point will a C&S member override the SL or break into communications just to flex authority, unless it is SPECIFICALLY to relieve the SL/PL of command for being a moron. The OIC may determine comms are too loose or too strict and may tighten or relax comms accordingly. If Senior Command cadre are online (Battalion-level) and they determine comms are too loose, they may override the OIC and call for Battle Comms. 7a) Channel Command will be answered only by the person in charge at the highest level, be it OIC, PL, or SL. That person, or a squad member of their choosing (such as OIC Radio Relay person) will answer as follows (changing names, obviously) in this example: Code: "Comm, this is Firefly, Black Widow Company" 7b) The Platoon Leader can also designate a C&S member (or an NCO if for some ungodly reason no other C&S is present) to serve as Channel Commander Liaison. IE, the PL says "So-and-so, turn on Chan-Com and relay our SITREPs to the other channel commanders." F.) Hacking And Exploiting Hacking and exploiting are considered dishonorable and against BWC standards. Those knowingly found modifying any game to gain unfair advantage over other players will be dismissed without strikes. Those who unintentionally run across bugs/exploits should do their very best to avoid situations where such bugs/exploits will give them advantage. Strikes may be issues for players who continue to exploit bugs after they have been told of fixes for such bug. This does not include gameplay mechanics which during the course of gameplay are available to all. For Planetside, this includes using an undestroyable vehicle after you been told it's undestroyable, knowingly exploiting dual cores and installing/using zero COF hacks, or using wall hacks. This list is not exclusive and other such similar activities may result in dismissal. The best defense is not install anything that will modify your Planetside Install. 3rd person, removal of mossie/reaver bailing animation and third person "wallhumping" among others are considered gameplay mechanics and are not punishable. For BF2, anyone who comes up with a cheating Punkbuster screenshot, removed by Punkbuster for cheating violations or being added to Punksbusted master ban list will result in dismissal without reconsideration for membership unless proof can be submitted that such bans were in error. For any other games, being removed by anti-cheat utility for cheat violations will result in dismissal without reconsideration for membership unless removal was done in error. In any case, final dismissal approval must happen by 2 senior level company officers and battalion staff member who are not assigned to S-4 division. V) Venom Company (Planetside) Specific SOP A) For Planetside, our rules are - in addition - as follows: -- 1) The only acceptable "Emerald/other empire" membership a BWC member may have is an entirely separate account, Fodderside or not. To further clarify, we are Terran Republic on Emerald, not Werner or Markov. Terran Republic is the only empire you can play on the Emerald server with your BWC main account, but if you have a secondary account, be it a free or paid account, what you do with it is your choice. This applies only for members of Venom Company (Planetside) -- 2) Medium Assault is required for all Main characters (alts do not need it). This is the only company-wide requirement for certifications. Task Forces are special volunteer teams and have their own stipulations. -- 3) You must log in at least every 15 days (alts included) or you will be removed from the in-game roster and your forum access will be suspended. If you plan to be gone longer than 15 days, you must post a valid Leave of Absence. LOAs are considered nullified after 90 days unless under specific cases such as military deployment. -- 4) No alts are permitted in another TR outfit or in another empire on the Emerald server (Markov, Werner, & PTS are not governed). -- 5) It is not possible to be promoted beyond the rank of Specialist without being a member of a Task Force. If you do not have a tab, then you will not be a Sergeant. There is no grandfather clause for this. Legionnaires are not required to serve with a task force, but are STRONGLY encouraged to do so. Officers are exempt, as they are leading their own TF or are serving in another official leadership capacity. -- 6) Planetside ranks follow a slightly different format, due to the limited capacity of the in-game Outfit Panel. Therefore, we have incorporated "Rank Brackets" for Planetside. See the BWC Awards forum for a better definition. -- 7) There is a 30-day "probationary" period when you join a task force. Once you complete a gaining task force's Phase One (Basic), you are assigned to that TF for a minimum of 30 days. Requests for transfer - be they from the parent unit (Venom Company) to a TF, or from TF to TF, require you to notify in writing via Private Message (PM) the Departing CO, the Gaining CO, and the Company XO (departing = the TF CO you're leaving, gaining = the TF CO you're going to). B) Squad Listing (hit P, go to Find Squad) In Planetside, Squad Leaders have the ability to list their squad so that anyone may join, without needing an invite. Squad Leaders may opt to set the squad to allow Outfit members to join without needing the SL's confirmation. Random members must request permission. It's up to the SL if mercs join, however mercs must be kicked if a BWC member needs the spot. -- 1) All BWC squads *MUST* be listed at all times. -- 2) All BWC squads must be listed as an ULTRA squad. The following is what we are using in the Squad Listing box: Code: \#00FF00ULTRA \#FF0000Black Widow Company \#00FF00 All Welcome Which would make ULTRA Black Widow Company All Welcome C) Officer In Charge/Platoon Leader/Squad Leader Policy (OIC/PL/SL) Quote ** CAVEAT INSTRUCTIONS: 1) This breakdown is for usage during Prime-time ONLY, when there is more than one squad. This set-up is *not* required for usage during Operations, FTX, or Training (whoever writes the OPORD sets their organization). When the OIC activates a Task Force during prime-time, they fall under guidelines for "Special Detachment". 2) At no time will any BWC squad, platoon, or OIC position be held by a non-BWC member. If this occurs, where a non-BWC member is given SL or PL, the squad is to request a BWC squad leader. If the SL/PL refuses, then BWC members will leave and start their own squad/platoon and regroup. 3) All personnel serving in the SL, PL, and OIC roles WILL have their Teamspeak Channel Commander feature turned on. All C&S members will have theirs turned on, as well. It is also advised that Galaxy pilots turn their Chan-Coms on, just to monitor. SECTION ONE: Definitions: 1) OIC - Officer In Charge -- Responsible for making all strategic decisions. This includes: -- Continent of Choice (check CR5 cat first, please) -- Priority Designation of Base and Tower Hacks -- Decisions on Forces Deployed (special detachments or squad roles) -- Monitor situation and disposition of enemy forces (should be the focal-point for all battlefield intelligence) -- Overall Coordination of BWC Assets (if more than one platoon) -- Overall Coordination with ULTRA and non-Alliance units (Chan-Com and/or CR5 chat) 2) PL - Platoon Leader -- Responsible for making the tactical desicions for the Platoon. This includes: -- Serving as the Primary (Gold) Squad Leader -- Method of Transportation -- Tactics to Complete Target Objective (If not defined by the OIC) -- Coordination with the SL's within the Platoon. -- Frontline Leadership and Control of the Platoon Forces on the Ground/in the Air. 3) SL - Squad Leader -- Responsible for making the tactical decisions for his squad. This includes: -- Method of Transportation -- Tactics to Complete Target Objective. (If not defined by the PL) -- Coordination with the Fireteam Leaders in his squad. -- Frontline Leadership and Control of the Squad Forces on the Ground/in the Air. 4) Special Detachments -- Responsible for performing in a role or task provided by the OIC. SECTION TWO: Position Requirements: OIC - Officer in Charge This Position goes to the highest ranking Officer online, according to the rank structure provided as an attachment below. The highest officer online (IAW rank structure), whether just coming on or having been on, always has the prerogative (and responsibility) to serve as the OIC. The highest ranking officer online can delegate the authority to another (subordinate) officer only. If only one officer is online, that officer must serve as the OIC. At no time when an officer is online, will any non-officers serve in the position of OIC. If no officers are available then the position of OIC is filled by the highest ranking Legionnaire or C&S Member. If no Legionnaires or C&S members are available the OIC position is filled by the highest ranking general member online. At NO TIME will the OIC serve in more than this capacity. They will concentrate on this job ONLY. The ONLY exception being that no other "capable" or "qualified" leaders are online, or when there is one squad. The OIC should be able to step in and temporarily take over as PL whenever he deems it necessary. He should not do this for prolonged periods of time - ideally, the OIC should never take over as PL unless the PL sucks. PL - Platoon Leader PLs must have CR3. Officers should serve as the PL (Gold SL). If only one officer is present, they should serve as the OIC. Rank has its priviledges - therefore, the PL should be next-highest in rank. SL - Squad Leader Must have CR1. Must be SFC or higher. Generally, officers will be seeking prerogative to serve as SL, but Senior NCOs are also permitted to hold SL spot during Prime-time. NCOs should also be serving as fire-team leaders within the squad (evens and odds - odd numbers Fire Team Alpha, even numbers Fire Team Bravo). Any NCO (SGT to LEG) is able to run a fire-team. SLs should be encouraging the use of fireteams. Special Detachments The OIC may deem it necessary to detach a separate squad for a specific role (such as, but not limited to, tasks within the realm of a TF-specific duty). In these instances, the OIC should select according to who among the online members is best-suited to lead, starting at NCO ranks. At OIC/PL/SL discretion, Squads may be detached from the main force with defined mission goals. The detachment leaders are to be assigned by the OIC. SECTION THREE: Precedence Listings This provides a composite order-of-precedence listing for those who need a quick reference point of who should be in what position. It details each position, and the order in which people should be lining themselves up for the positions. Generally speaking, officers should be the OIC and Platoon Leader (aka Gold SL). Squad Leaders should be coming from Senior NCO ranks (thus providing the responsibility for NCOs). Fire-teams should be put into usage - generally they are not. NCOs of any rank should be running fire teams. Special Detachments may be broken off from a squad and assigned to the platoon as a separate squad, upon order from the OIC. OIC/PL Precedence List: DucusSumus SteelRain13M TF COs Firefly(*) Kurael(*) Zanduar/TheSniperSteve(*) Company 1SG, Palin By-rank, Senior NCOs * = Kurael and Firefly can takeover whenever they'd like (Zanduar and TSS can takeover for Lieutenants), but by default, Company cadre should be leading. SL Precedence List: Appropriate TF Leader (officers) PS 1SG Palin By Rank, Senior NCOs (SFC/Higher) TF detachment leaders/NCOICs Rabbit(*) * = Rabbit can takeover whenever he'd like, but by default, Company cadre should be leading. Detachment Precedence List TF Detachment Leaders TF NCOICs VI: Wolfspider Company (GR:AW, BF2, Red Orchestra) Specific SOP TBD VII: Nightcrawler Company (Unreal Tournament) Specific SOP TBD | ||
 |
||
|
Welcome, Guest. Please login or register. Did you miss your activation email? |
||
 |
||
|
2 Guests, 0 Users |
||
 |
||
 TR Orbital Strike |
||
 |
||
| No polls are currently active, check back later! | ||