S13 Zulu Unit - "Swift to Destroy"

S13 Zulu Unit - "Swift to Destroy"

Sunday 4 December 2011

Section 13 - Operation Shakedown

The Problem

Due to the recent change of game to BF3 numerous problems and issues have been encountered that have hindered the effectiveness of Section 13, battlefield performance, organisation and enjoyment. Here are a list of prominent examples:
  • BF3 in game communications are unreliable, unclear and as a result unusable.
  • Members are not as committed to BF3 while others are more committed.
  • Current structure does not allow the 'online population' to identify a clear leader.
  • Current structure spreads out our most experienced and skilled players.
  • Current structure does not effectively establish a chain of command and squads.
The Solution Proposed v1.0

Communications

New communications system utilises Teamspeak 3 Client through computers.
  1. Download Teamspeak 3 Client to your laptop (make sure latest version).
  2. Search the server list for New Zealand servers
  3. Look for ON3Network.co.nz l TS3
  4. Scroll down near the bottom to the green BF3 folder and enter it.
  5. Any questions ask a knowledgeable S13 member.
Reasons for use of teamspeak
  • Instant.
  • Clear.
  • Communications maintained outside the BF3 framework.
  • Customisable.
Rank Structure

The following is an example of the former rank structure implemented by Section 13.
Characteristics
  • Rank structure positions are fixed in place.
  • Each squad is seperate from the others and have their own memberships.
Weaknesses
  •  Most experienced players are spread out.
  • Online population never large enough to implement the structure.
  • Confusion over who leads when there are those of equal rank.

Strengths
  • Good for setting up running units.
  • Friendly competition.
  • Clan matches.
  • Getting to know individual players.




Vertical Rank Structure



 So firstly a description of the new ranks structure.
  • There is one line of chain of command.
  • Your rank depends on your total game time.
  • MikeBravo9er is at the top regardless of game time.
  • At the end of every week the rank structure is reviewed by MikeBravo9er who has the power to promote someone above where they should be according to game time.
  • These changes are then communicated to Ritterkreuz352 who updates the standing rank table of S13 personnel on the S13Z blogspot.
  • You have to put in more than 4hrs a week to attain a rank otherwise you are regarded as a casual member.
How does it function in game
  • Ideally everyone would be online all the time so we would have this situation occur given the example above.
  • However not all of us are online constantly, therefore if MikeBravo9er was offline then 007_eleven would become overall commander and Sierrabravo would move up to a Sqd Ldr.
  • Now you can only have sqd ldrs if there is a sqd for him/her to command.
General Tactics development
  • The General Commander assigns objectives to the SQD LDRs
  • The SQD LDRs are then there to utilise SQD members individually to achieve the tasks.
  • The General Commander is free to do as he/she pleases.
  • Example would be General Commander orders Bravo SQD to hold position then the SQD LDR would tell the individual members of their sqd what to do.
Reasons for the New Structure
  • No matter who is online we can have an effectiv rank structure.
  • Flexible.
  • Allows other players to experience leadership.
  • Rewards commitment.
Some handy ideas
  • S13 members required to have battlelog and be members of S13 Platoon.
  • S13 members required to have teamspeak.
  • S13Z blogspot to be changed and modified to be come the official S13 webpage and spot to look for current S13 rules, activities and tactics.