Outfit 418 Field Operations Guide: Platoon Hierarchy Booklet

Confidential, not to be distributed to the likes of Edward Snowden, Julien Assange or any of their ilk. Failure to prevent dissemination will be punishable by cucumbers.

Auraxian Free Publishing, (C) 2013

Table of Contents: THE PLATOON MEMBER (PM), PLATOON LEADER (PL) AND SQUAD LEADER (SL) GENERAL REMARKS PLATOON DISCIPLINE COMMS DISCIPLINE THE PLATOON HIERARCHY PLS RESPONSIBILITIES SLS RESPONSIBILITIES PMS RESPONSIBILITIES 3 3 3 4 5 5 7 8

1 Esamir Alert Celebration

The Platoon member (PM), Platoon Leader (PL) and Squad Leader (SL)
General remarks
Platoon discipline It is up to the platoon leader to designate objectives and it is expected the PMs will act in their best capacity to complete the objective. Generally platoon leading demands sacrificing some fun factor and PMs should recognise that and try not to add to the stress. While in general the PL should always try to provide his platoon with an appropriate challenge and an enjoyable fight (Planetside 2 is, after all, to a large degree about shooting the hell out of other players), everyone needs to be always aware that sometimes this will simply not be a possibility. Sometimes, the population advantage will be skewed too far to either side, making for very boring fights due to how little opposition there is, or due to how impossible the odds are. Nevertheless, odds which may be too high are preferable to no opposition at all: the PL should simply inform his PMs what the situation is and that everyone is in for a rough time, giving people unwilling to participate in such a fight a chance to leave the platoon. Other times, i.e. during an alert, an enjoyable fight might be some time in the making, as the platoon works toward the alert objective, while trying not to become tied down in a single fight for too long (if that is what works best for the current situation, at the PLs discretion). For more details, refer to the Tactical Guidelines section. Outfit 418 has a policy of supporting the PLs and SLs: if you have a different vision than what the PL wants to achieve, then accept it as just that a difference in opinions, but follow the PLs order. As long as they are the PL, its their platoon and their game. Next time you have a chance to lead the platoon, step up and implement your vision of how things should be done. As a PL or a SL, when in doubt, never hesitate to ask one of the officers for advice, using OUTFIT chat, private messages or our Teamspeak server (TS address: aur.dk). In fact, PLs and SLs are highly encouraged to be present on our TS server, if possible. If you think the PLs orders are not the optimal way to go about doing things, either politely make your suggestion via a private message, or if pressed for time due to the urgency of events at hand using outfit voice/text chat, indicating your reasons why your plan is better than the PLs. The reason for using outfit chat is that when leading an open public platoon, wed like to maintain a unified command and not give the other people joining us the impression that it is fair game to debate the PLs decisions, as this runs the risk of leading to a collapse of discipline in the platoon (and sometimes it is difficult enough to have everyone act in unison even without questioning the PLs decisions). If you believe the PLs decisions are terrible and likely to have disastrous results, whisper the PL (or use outfit voice chat, if urgency demands it) and suggest to take over the platoon, or suggest a different PL. If in doubt, contact one of the officers, if any are online at the time. Remember: too many cooks spoil the broth, and in real life military there is a reason why the army is not known as the debate club, but known for its command hierarchy.

Comms discipline It is fair game to banter when in transit to a location, or during down time when capping an uncontested place, or when assembling in a warp gate (WG), unless otherwise requested by the PL/SL. However, once the platoon goes into combat, comms should be kept clear for orders and intel. You can always still use text chat to congratulate your fellow PMs on a great shot, or for discussions of which gun is better for which situation, but a short word of congratulations or thanks in voice is still permissible, provided comms are not busy. Additionally, we have the comms clear command, after which no comms usage is allowed, as the PL/SLs are using the leader chat to coordinate with other outfits, or they want to issue orders for the platoon. Reporting any important intel (like the locations of enemy sunderers, tanks, aircraft, infantry movements, MAXes, etc.): Name the reported object, report its direction relative to the centre of the current objective, e.g. 3 Magriders, N-W; if possible and comms are not very busy, add extra details to help locate the threat quickly: In the ravine next to the ammo tower. When the platoon is engaged in a single location, use PLATOON chat. When the part of the platoon (two or more squads) is in a single location, while the rest of the platoon is elsewhere, use PLATOON chat, but indicate the location you are referring to : The Bastion, sunderer incoming on the road, south. When each squad is operating independently (or at least three squads are in three different locations), use SQUAD chat. Should the SL see the need, it will be reported in PLATOON chat as well. When requesting something, it is suggested that you use your squad designation to help prioritise the requests and differentiate from all other people, for instance on Leader chat; e.g. Charlie Lead, need help against tanks on the Bulwark as opposed to Some Random Outfit Leader shouting on Leader chat: We need EVERYONE, EVERYONE on the Small Facility with 2 enemies. When reporting intel on facilities being lost/taken, ask yourself whether it is important for the moment, or unrelated to what the platoon is currently doing. This will allow you to better decide on the method which you should use for reporting this important information. Immediate needs are things connected to what the platoon/squad is currently doing and this is done via PLATOON chat, or SQUAD chat if squads are operating separately. When reporting a facility that is being lost or recaptured try not to make the comms more busy than they have to be if the information can be conveyed via text chat and still have the same impact, do so, the PL/SL will (should) notice. If during a cross-continent alert, think carefully whether reporting a facility that is being lost/taken on a different continent has any immediate relevance for what the platoon is doing on the continent it is on. If it is not a matter of winning/losing the alert by this single facility, report in text chat if you still feel it is important to report it in the first place. When in doubt, you can always send a private message to the PL/SL indicating what you have observed.

For immediate needs (ammo, healing, repair), try to use SQUAD chat, as you are meant to be operating together with your squad mates. Alternatively, use PROXIMITY chat or the voice command system to ask other PMs or NC nearby. As a last resort, if for some reason all the other options are not feasible, use PLATOON chat. Finally, when being issued an order, SLs acknowledge the order for their squad using their squad designation (Alpha, copy), and individual PMs acknowledge the orders received from their SL using their squad designation (Charlie 2, roger). A simple copy that, roger (wilco), on it, or any other variation thereof from a few squad mates will suffice if comms are particularly busy.

2... and stay down!

The Platoon hierarchy

PLs responsibilities
While it is individual preference and there are no hard rules about it, 418 PLs tend to be separate from SLs, i.e. the PL focuses on leading the platoon, leaving individual squad leadership to the SLs. If, however, a PL wants to maintain his SL position while doing PL duties, there is nothing stopping him from doing that, provided he feels reasonably comfortable doing both at the same time. The PL is then responsible for: Gathering appropriate intel that will help them make informed decisions on the platoons current and future actions. This is done by following the map, taking note of where threats are, deciding whether the platoon is going to be able to overcome these threats, whether it will need help, etc. Additionally, the PL asks for a scout (such as a Reaver) to proceed to a

particular area and report the type of threats found in it, especially before performing a Galaxy drop or a massive vehicle deployment in a given place (but not limited to such deployments). Deciding what the platoon objective is and suggesting how it should be carried out. Ideally this will be done in a sort of a briefing manner: the PL declares what the objective is, how the platoon will get there and which squads focus on which part of the objective. If the PL does not designate details, it is up to individual SLs to carry out the objective as best as they see fit, while announcing their intention/ suggesting what to do to the PL. Designating whether a particular squad should provide air, tank or infantry support. If the PL does not specify the exact details, it is up to the SL to decide what the appropriate exact composition of a tank/air force should be (i.e. if the PL does not specify he wants, for instance, three Skyguards, it is up to the SL to ask for some form of air cover for his armoured squad, if the circumstances demand it). Requesting status updates on whether a given squad is still performing its designated vehicle role and whether it is still able to continue doing so, and should the squad be unable to maintain its current vehicle role assigning a new one (by, for example, switching two squads around in their tank/air support roles; this has the added benefit of making it easier on everyone as far as resource costs go; the squads can regroup at a convenient location and people can simply swap vehicles, if one squad still managed to hold on to the bulk of its vehicles). Using the platoon waypoint to indicate general platoon movement, as well as indicating specific targets during an engagement, such as a specific generator, or enemy Sunderer. Setting intermediate waypoints for the platoon to regroup at when in transit to the final destination. It is up to the PL whether to announce that destination beforehand, or not when the PL chooses not to announce it, SLs and PMs should have enough faith in the PL not to question this, if the PL refuses to announce what the destination is when asked about it (this is often times the result of us having undisciplined random people in our public platoons and the PL not wanting them to rush off to the final destination ahead of the rest of the platoon). Removing the platoon waypoint and asking the SLs to use squad specific waypoints instead, if appropriate to the situation; e.g. squads operating individually across several objectives. Asking the SLs assessment of the situation the given squad is faced with, i.e. whether they can be successful or not with their current task to determine whether to reinforce the squad or redeploy it. Requesting a platoon redeploy to the WG, when the situation demands it, bearing in mind any vehicles the platoon may currently have which may have to regroup elsewhere, or which may have to be abandoned (additionally, the PLS asks himself: do they need to be abandoned for the next objective or can they be still useful?). Asking the SLs (if he is not a SL himself) to put down defensive/offensive markers on the locations of his choice. Asking the SLs to coordinate on LEADER chat (the game seems to take away the PLs ability to access LEADER chat when the SL in the PLs squad also has access to it). This is announced with a comms clear command. Issuing the comms clear command, if he wants to issue important orders.

Issuing clear and understandable orders and asking the SLs to acknowledge them, if they do not do so on their own. Removing people repeatedly not following orders from the platoon, either the ones they spot themselves, or those indicated by SLs. Initially, a grace period of one to two minutes is suggested, giving the AWOL PM a chance to rejoin the platoon, coupled with a spoken caution, e.g. Right, anyone whos not following orders, youve got two minutes to rejoin the rest of the platoon, otherwise youll be kicked from the platoon. A good moment for doing this is when the platoon redeploys back to the WG, or when a particular base capture has just been completed. Informing his SLs and the rest of the platoon about going AFK, possibly temporarily handing over PL lead to someone.

SLs responsibilities
Make sure you are familiar with the Platoon discipline section under General Remarks. The squad leader implements PLs orders on a more detailed, tactical level. The SL is then responsible for: Putting down the squad beacon for his squad to spawn on as soon as possible, taking into account the beacons survivability in that position. He then indicates to his squad that the beacon has been deployed. For some guidelines on beacon placement, please refer to the Spawn Beacon placement section. Deciding how to carry out the PLs order, especially when the PL doesnt issue detailed instructions on how he wants it to be carried out. The SL then announces his intention to the PL to get a go-ahead. Acknowledging the PLs orders using the squad designation, e.g. Alpha on it. Deciding what the squad composition should be, especially when doing an air/tank support squad. In the absence of specific orders from the PL, the SL uses his best judgement to ask for a specific mix of vehicles, if the circumstances demand it. In the absence of specific orders from the SL, the PMs of a given squad announce their intention to pull a specific vehicle and the SL acknowledges it. Reporting to the PL status updates on the squads designated vehicle role capacity: whether the squad is encountering any threats making it impossible for the squad to continue in its current role, whether the squad still has the resources to continue in its designated role, what and how many vehicles it still has. This the SL does on his own initiative, or when prompted to by the PL. Indicating to the PL whether the squad is likely to be successful or unsuccessful in carrying out the PLs request, so that the PL can determine whether to reinforce the squad or redeploy it. Using the squad waypoint to indicate a specific squad objective within a platoon objective, or when the squads operate individually to indicate the current individual squad objective. Removing the squad WP if the entire platoon is working on a single, specific objective. Requesting a squad redeploy to the WG, if their current PL-set separate squad objective demands it. When in doubt, the SL asks for the PLs go-ahead. Putting down defensive/offensive markers when requested by the PL, or indicating their intention to do so to the PL if they feel a marker is needed in a particular place.

Coordinating on LEADER chat according to PLs requests for the PL, if he does not have access to it themselves. Additionally, the SLs listen on the LEADER chat for important intel and relay that back to the PL. Issuing a comms clear command for the PL if he is trying to issue a command, but forgot to issue a comms clear command themselves. Taking note of people in their squad not following orders or breaking off from the squad without announcing their intention to do so, cautioning them to follow orders, giving them a grace period and finally asking the PL to remove them from the squad if they continue to disregard squad orders. Some leniency should be allowed for vehicles, as for instance the squads Reaver may be engaged in a dogfight and unable to rejoin the rest of the squad, or a Vanguard may be in transit to the squad location and simply taking some time to arrive. Indicating focus-fire priority targets. Requesting specific squad movements, such as flank on the left, load up the Sunderer. Regrouping his squad after an engagement, indicating where the squad should regroup and the method of transport to the next objective. In the absence of such orders, the PMs should offer their own initiative and indicate any vehicles they have that could be used to transport the squad. The SL should also set a realistic time limit in which the squad should regroup that is appropriate to the situation, or order the squad to move out if his squads PMs have been particularly slow to regroup. The stragglers will have to rejoin on their own, feeling guilty if their tardiness has gotten their squad into trouble. Making sure there is a squad (guarded) Sunderer/Galaxy, if the situation permits it, and requesting replacements should the need arise. Informing the PL about going AFK for some time, possibly selecting some other 418 member to temporarily be SL.

PMs responsibilities
Make sure you are familiar with the Platoon discipline section under General Remarks. The PM acts on the SLs orders to carry them out as best as they are able to. The PM is then responsible for: Following the SLs requests. Helping out his squad mates. Scouting out ahead for his squad, if possible and equipped appropriately and relaying this information to the squad. Reporting to the SL whether they can continue in their designated squad vehicle role: whether they are encountering any threat making it impossible to continue in their current vehicle role, whether they still have the resources to continue pulling vehicles, etc. Informing the SL on the state of the squad Sunderer/Galaxy (whether it is under attack, still up, location.) Deploying squad AMS Sunderers in sensible locations, balancing the risks and rewards: i.e. making sure it survives long enough to make an impact in the fight with its spawning capabilities. In the absence of a specific request from the SL, the PM should use their best judgement to deploy the vehicle in a defensible location that is close enough to the target. Informing the SL that the squad spawn beacon is unavailable (destroyed).

Informing their SL in text chat about going AFK for some time, switching over to a non-vital position if in a vehicle (e.g. when on one of the guns, switch to a passenger position)