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.

Tuesday 8 November 2011

S13 ZULU UNIT BF3 - PHASE ONE

Hello there team.
Up until now we have been having a free run over BF3 learning how the game is working and where our strengths and weakenesses are.
Now we are entering PHASE ONE of S13 ZULU Unit for BF3. This requires that members with the unit actively participate in attempting to reorganise ZULU into the effective unit we used to see on the fields of BFBC2. How are we going to do this? I have outlined a number of steps and issues as this is largely a test run of methods to achieve this (Expect PHASE TWO to be a further refinement).

Known Problems and Solutions
  • Servers are always full and we end up on different teams.
    • Stay in the game and attempt to "Switch Side" when numbers allow within the "Team and Squad" menu.
    • Maintain type chat comms as per standing orders so you can let people know whats going on.
  • Voice comms are broken and unreadable
    • BE ON TYPE CHAT so then you can organise breaking into smaller squads (better comms this way) or switch Voice Channel in "Team and Squad" menu to Team Channel.
  • S13 Zulu Unit lack of organisation
    • EVERYONE HIGHLY ADVISED to read Unit Standing orders on the blog page and encourage them for yourself and other team members.
    • EVERYONE HIGHLY ADVISED to maintain type chat comms.
    • Try to set up battlelog.battlefield.com and monitor unit page there. Not alot of people can do this so we are keeping the blog as the primary reference.
  • How do I get input as a member
    • Post your feedback to my PSN account or too the Zulu Unit page in battlelog and this will be posted to the blog.
    • Encourage your team mates to adopt Unit Standin Orders.
Extra Notes
  • Please confirm your main BF3 user account for posting on the blog.
  • All unit instructions are guides only not orders, it is your decision and effort wether to follow them. In other words you are not told how to play the game, we are here to MAXIMISE ENJOYMENT.
  • Expect practice sessions in the not to distant future.
  • Ritterkreuz352 is on a break from BF3 for a while.
IMPORTANT - If you have read all this you can confirm with a post on the Unit wall, or email to my PSN account.

Thursday 29 September 2011

Section 13 Personnel List

Current S13 Roster
ALPHA-Leader: MikeBravo9er
kneedeep46,schade509,gthot76,KAEL1234.

BRAVO-Leader: SierraBravo-M78
triplecde,SIX-AHEAD,tootusmaximus,uxguy,DROP_THE_SOAP_.

ECHO-Leader: s3kShUn08
DeathRose88,alexander1313,KLip-kNoTiCk,Crossbreed-.

GOLF-Leader: Goryinche
007_eleven,jaydenrooks,ARC_666,igenecide45.

YANKEE-Leader: Jootino
KZ4LIFE808,PardOxKitsune,wtfANDY,KCcitystar.

ZULU-Leader: Ritterkreuz352
Malikant,Flt-Lt-Wilco,The_Commando-666, MY_REAPER, nzpm.

Wednesday 28 September 2011

Standardised Team Chatter

Issue:
Everyone very much appreciates getting vital intel on the battlefield but it is not always conveyed in the best way. The crux of the problem is that everyone talks differently and has different terms.

Advantages of  a Possible Solution:
Better conveyed intelligence to team members resulting in better overall situational awareness on the battlefield in turn resulting in better performance.

Suggested Solution:
Standardised terminology for example
Opposition unit = Contact
Main battle tanks = Heavy armour
Amphibious Assualt Vehicle = AMTRAC
Growler = Jeep
Anti-air = AA (Aae, Aae)
Rib Boat = Rib
Scout Helicopter = Scout Helo
Attack Helicopter = Attack Helo
Gunship with 50.cals = Helo
Jet Fighter / Fighter Bomber = Jet
Vodnik/HUMVEE = Humvee
Stationary weapons = Stationary

 
When giving intel follow the steps and skip steps that are unknown
(General Guide not strictly adhered to)

Number of Contacts
Weaponary/Class
Mode of transport
Direction
Direction they are covering
Their intentions

Example of a intel report
"2 Contacts snipers on foot moving to bravo covering area in between aiming to arm charge"

 
Notes
  • Be careful calling position reports and direction reports, reference to a commonly understoood feature or leave it out all together to resolve ambiguity.
  • Think before you report.
  • If your having trouble just use plain language.
  • There is no pressure if you get it wrong this all just an idea to get things running smoothly.
  •  Lastky enjoy your gaming.