Announcement

Collapse
No announcement yet.

Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • [AAR] Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

    Fri PM and Sat AM 30-Sep and 31-Sep

    Map: Operation Metro (Rush...Open Beta)

    This is an After Action Review for multiple games starting from early Friday evening until midday Saturday.

    I apologize in advance that this will not be a positive AAR. Frankly, what I saw was pubbie trash.

    ====================================
    Specific Actionable Recommendation:
    *** Play the objective***
    ====================================

    ====================================
    Plan:
    ====================================

    * Objective as attackers is to arm M-COM stations and protect them long enough for them to explode. There are 4 pairs of M-COMs on each map

    * Objective as defenders is to prevent the arming of M-COM stations and eliminate enemy tickets by killing attackers

    1. No plan was communicated

    ====================================
    Performance:
    ====================================

    2. Multiple times attackers were able to arm an M-COM with a "Hey diddle diddle" (straight up the middle). That means that, at round start, an attacker simply ran up to the M-COM and successfully armed it.

    3. Multiple times an M-COM was armed behind the main "gaggle" of defenders meaning attackers were able to bypass the defenders

    4. Multiple times both M-COMs were armed at the same time making it unlikely that the defenders could save both

    5. Multiple times defenders simply did not react to the arming of an M-COM

    6. Multiple times I (58Congo) was disarming and was knocked off of the M-COM by a friendly player. This forces the disarm to start over and it exposes both players to incoming fire. Multiple times, it caused us to lose the M-COM

    7. I (58Congo) was called out as a cheat by a fellow TG player

    8. Gave away lots of easy kills in clusters around portals and corners. Poor light and laser discipline.

    9. Lost close rounds as attackers (ran out of tickets)

    ====================================
    Issues:
    ====================================

    A. No advanced planning. No agreement who goes where with what role and what kit

    B. Not playing the objective. Players rushed to their favorite camping spot to up their KDR regardless of the team outcome (win or loss)

    C. No defense. Force/security was not established at the M-COMs and maintained before projecting outward/forward

    D. Not reacting to an M-COM being armed. Defenders just stayed in their favorite camping spot or used the opportunity to move to their spot to get cheap kills on attackers during the map shift

    E. No "eyes on objective" caused defenders to be surprised and "on their heels" trying to rescue and disarm an M-COM from behind the power curve.

    F. Pushed forward too far to be able to help disarming M-COMs and no collapse back to defense

    G. Basic tactical mistakes like crowding cover, waling into another's line of fire, blinding teammates with lasers or flashlights, and freezing or camping in doorways

    H. Poor understanding of winning condition (preserving tickets)


    ====================================
    Improvement:
    ====================================

    (1. "No plan")

    * There is a 25 second countdown before the round starts, a simply team-chat on a plan would work wonders even if it's (We'll go here. You go there.)

    * A simple standard operating procedure (SOP) would work wonders. Here is one which I will call the YY or "double wishbone" because the squads form a "Y" around the M-COM.


    Alpha Squad (4 players)
    Alpha Buddy Team 1 = A1
    Alpha Buddy Team 2 = A2

    Bravo Squad (4 players)
    Alpha Buddy Team 1 = B1
    Alpha Buddy Team 2 = B2

    Gamma Squad (4 players)
    Alpha Buddy Team 1 = G1
    Alpha Buddy Team 2 = G2

    Delta Squad (4 players)
    Alpha Buddy Team 1 = D1
    Alpha Buddy Team 2 = D2
    ------------------------------------
    Total is 16 players


    ------------------------------------
    Basic diagram for 1st and 3rd M-COMs
    ------------------------------------

    A1......A2.......B1......B2

    ....G1................D1
    ...MC-A............MC-B
    ....G2................D2


    In this SOP, Alpha and Bravo squads are responsible for forward gap control.

    Gamma and Delta are responsible for defense. Gamma buddy team 1 and Delta buddy team 1 have "eyes on objective." They can be in those sneaky spots facing backwards towards either M-COM Alpha (MC-A) or M-COM Bravo (MC-B). Gamma buddy team 2 and Delta buddy team 2 have a wide enough view of the battlefield that they can spot enemy sneaking around the sides of the map. They are also a road bump that those sneaking enemy must encounter.

    This formation is, of course malleable to fit terrain (i.e., be in advantageous positions with frontal cover).

    If one of the M-COMs is lost, the basic formation remains the same. The defenders of the lost M-COM simply create a crossfire defense for the remaining.

    If both M-COMs are lost, the teams bound backwards (aka leapfrog) and reverse roles.


    ------------------------------------
    Basic diagram for 2nd and 4th M-COMs
    ------------------------------------

    G1......G2.......D1......D2

    ....A1................B1
    ...MC-A............MC-B
    ....A2................B2

    If you'd want, the buddy teams could switch positions for the 3rd and 4th layer of M-COMs (i.e., A1 and G1 are behind the flag).

    If you are playing on a mixed server with pubbies, watch what they do and fill in the gap. If they like to camp out at the M-COM, have your squad go forward. If they like to push forward and spawn-rape, have your squad defend the M-COM. Alternatively you can do this using one person for each role instead of a buddy team. Just be careful if the pubbies change tactics (i.e., they are bored sitting by the M-COM and move forward).


    (2. "Hey diddle diddle" at round start)
    (3. "attackers bypass defenders")
    (4. "armed at the same time")

    Simple SOPs fix this.

    SOP 1. If you spawn from the back (default defender spawn), you first visually inspect your M-COM to make sure it's clear. Since you are spawning from the back at round start, you should first check the M-COM at round start before pushing forward.

    SOP 2. If you are on defense, you should visually inspect your M-COM to make sure it's clear. Ever hear the expression "You know the drill"? Well, this *is* the drill. And it's part of having professional discipline.

    SOP 3. It only takes 3 keystrokes. "k" (for team-chat), "a" or "b" (for which M-COM is under duress), and "Enter"

    SOP 4. Someone needs to have eyes on objective at all times. That means in sight of the M-COM watching it and/or close enough to hear the sound of it being armed (preferably both). The "double wishbone" above ensures this. Even if you don't want to use the YY formation, someone needs to assign this task. Squad leader that means it's your task until you assign it to someone else. Besides, this is your opportunity to be cheesy and get some easy kills with your C4 ringed around the M-COM.

    It should never be a surprise that an M-COM gets armed because there should be someone with "eyes-on" the objective at all times.

    * Playing the objective should also improve these
    * Having established roles should also improve these (see above)
    * Having a "gap control" formation should also improve these (see above)
    * Having "eyes on objective" should also improve these (see below)

    (5. not reacting to the arming of an M-COM)

    Hopefully if you are failing so completely that this happen, it at least dings your professional pride somewhat. Why are you here at TG?

    SOP 5a. As defenders, if an M-COM is armed you should collapse back to rescue it. You're likely to pick up some easy "shoot 'em in the back" kills anyways.

    SOP 5b. As attackers, if an M-COM is armed you should descend upon it to protect it. You're likely to pick up some easy "shoot 'em while they're distracted" kills anyways.

    (note: SOP 5a/5b also applies to flags in conquest)


    (6. knocked off of M-COM while disarming)

    Hopefully everyone has played the beta enough now to know that 2 players cannot occupy the same space. If they try, one or the other (or both) get knocked around some.

    Folks, the M-COMs are square. One person per side. If there is already someone trying to disarm it, pick a different side to disarm from. Or, even better, take a forward position and defend the person trying to disarm. The disarm seems to go no faster if 2 people are disarming and only the first person there is going to get the points anyways.

    SOP 6. If you are first to an M-COM you get your choice of sides to disarm from. Pick the safest (frontal cover). If there is already a teammate trying to disarm, PICK ANOTHER SIDE TO DISARM FROM. Or, move forward a few steps and defend your teammate (soak up the rounds meant for him).


    (8. killed around corners/doorways and lights/lasers)

    Again, hopefully people understand that 2 players cannot occupy the same space.

    SOP 7. Don't stop in doorways or at corners. Either take a few steps back or forwards. Back is usually better.

    SOP 8. Don't cross in front of other players. Yes, in the clans and tournaments I played in we actually practiced not doing this. The drill looked like stopping as a group while skiing (i.e., each successive person stops below the previous person). If you must cross in front of another person, change your elevation. Jump if they are prone or forward dive to prone if they are standing.

    SOP 9. Please, relegate your tactical lights to your sidearm (i.e., M9 TACTICAL or M443 TACTICAL). If you want light then switch to your sidearm. A cool "hunter killer" buddy trick is to have one of you with their pistol+light shining on a corner or doorway while the other with their primary moves in the dark. This is a real-life 2-man team tactic by-the-way.

    SOP 9a. If you are flashed, shoot first. Ask questions later.


    (9. ran out of tickets while M-COMs were armed)

    Tickets are deducted when you respawn. If you hear the "Battlefield theme music" start to swell then, as attackers, you are low on tickets.

    SOP 10a. DO NOT RESPAWN if you are low on tickets (music swells)
    SOP 10b. As attackers, make an effort to revive all teammates not stupidly out in the open in the middle of an 8-way crossfire
    SOP 10c. As attackers, accept all revives.

    Yes, it sucks being caught in the middle and getting revived only to immediately die again. You know what else sucks, being only a journeyman ski-racer in the collegiate system where a minimum number of your team need to finish to score. You're the domestiques of ski-racing. It's your teammates job to ski to win and it's your job to ensure that the team has the minimum number of finishers...even if that means wiping the blood from your nose and dizzily putting your ski back on after a crash. This is Tactical Gamer and we need that ticket. So suck it up, cupcake.

    ====================================
    Final thoughts:
    ====================================

    Look I see all of this b!tching and moaning about native VOIP, squad size, squad spawning, etc. Folks, there was teamwork before BF2. BF1942 didn't have squad spawning, didn't have native VOIP, didn't have anything. And yet, we were able to make teamwork work. I barely saw any congregating as a squad and very little playing of the objective. We did not demonstrate that we need or would make use of those features in these games. Time to get our $h!t in order.


    Oh, and calling-out a fellow TG-er for cheating...in game and in all-chat...in a beta when half of the players are running around listing at a 45 degree angle with giraffe necks and rifle magazines sticking out of their heads...well, not sure what to say about that.

    http://battlelog.battlefield.com/bf4/user/58Congo/

  • #2
    Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

    I enjoyed this post/rant.

    I deserve a ribbon for Mortar Specialist

    Artillery conquers and infantry occupies.
    J.F.C. Fuller

    Proud to have been a member of the 5th, 71st and my beloved 19th

    Comment


    • #3
      Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

      Folks, it is extremely rude to accuse anyone of cheating in a public manner. If you take issue with another player, find a BF3 admin. If no one is available, create a post in the CAA forum.

      I'm very disturbed that someone would accuse another TG player of cheating in such a fashion.
      Skud


      Comment


      • #4
        Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

        If that member was part of an IHS you should inform their leader...I know if it was a 3rd member we'd want to know so we can take corrective action

        Comment


        • #5
          Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

          Sorry, I actually found this post un TG like. It was me that typed out "Congo taking no damage" and I was laughing on TS when I said it. I was genuinely stunned that you couldn't see me next to you. I shot 3 whole magazines into you and was describing it the whole time on TS,m I then ran after you and shot pistol rounds at you. I was more amazed then anything. If it came across like I was accusing you of cheating I am sorry, but good job on the post, really great. If you want to discuss it further, pm me.

          I would suggest this thread is locked as it serves little purpose as the 'guilty' party (ie me) has 'owned up'.
          Last edited by Wicks; 10-02-2011, 04:31 AM.


          Comment


          • #6
            Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

            The bugs still exist. I had a game yesterday where I was revived, and became indestructible. I killed about 6 people, then just decided it is wrong, and stood in the middle of the map (we were in the ticket part) and waited to die. Only I didn't. Grenades and bullets would not do it. Eventually someone C4'd me. It happens. :)

            Comment


            • #7
              Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

              ok, so the cheating thing we can ignore now :) Let's focus on the rest of that epic post.

              Comment


              • #8
                Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

                So I am wondering where TG stands on the flashlight concern, in another post someone suggested shooting after being blinded and was told TKing is unacceptable here, but this post suggests

                SOP 9. Please, relegate your tactical lights to your sidearm (i.e., M9 TACTICAL or M443 TACTICAL). If you want light then switch to your sidearm. A cool "hunter killer" buddy trick is to have one of you with their pistol+light shining on a corner or doorway while the other with their primary moves in the dark. This is a real-life 2-man team tactic by-the-way.

                SOP 9a. If you are flashed, shoot first. Ask questions later.
                Can anyone please clarify for me?

                Comment


                • #9
                  Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

                  Inspiring read!
                  "Nemo Saltat Sobrius, Nisi Forte Insanit"

                  Comment


                  • #10
                    Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

                    Originally posted by Zelidus View Post
                    SOP 9a. If you are flashed, shoot first. Ask questions later.
                    Can anyone please clarify for me?
                    TK's are unacceptable. In real-life, does anyone think SOP would be to shoot first, mail a letter to Joe's family later? ("We regret to inform you that Joe shined a flashlight at a squadmate."). We all are responsible for maintaining situational-awareness and not killing our team-mates... regardless of how careless they are.

                    Comment


                    • #11
                      Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

                      Originally posted by WhiskeySix View Post
                      "We regret to inform you that Joe shined a flashlight at a squadmate.
                      LOL

                      Can we keep sending them out the the widows of Zhohar's C4 collateral damage?

                      Comment


                      • #12
                        Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

                        Originally posted by WhiskeySix View Post
                        TK's are unacceptable. In real-life, does anyone think SOP would be to shoot first, mail a letter to Joe's family later? ("We regret to inform you that Joe shined a flashlight at a squadmate."). We all are responsible for maintaining situational-awareness and not killing our team-mates... regardless of how careless they are.
                        When someone is shining their flashlight on you, 9/10 times the bloom makes it impossible to see the squad/team marker and name above them, especially if they are within about 10 feet of you. How do you relegate not-TKing if all you see is a big white spot over half your screen who may or may not immediately unload a shotgun into you? Snap decisions. Shoot and not be killed, or shoot and potentially TK.

                        <04:11:24> *** You are now talking in channel: "TFP - Task Force Proteus"
                        <04:16:25> "|TG-XV| Tralic": this channel is so gay
                        DICE needs to make a comical boxing glove attached to a spring punch the player in the face 40% of the time they get into a helicopter or jet.

                        Comment


                        • #13
                          Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

                          I think the is a clear distinction between accidentally Tking someone who you mistook for an enemy and intentionally Tking someone just because they blinded you with their flashlight.


                          It comes down to UYB

                          Comment


                          • #14
                            Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

                            Originally posted by Specterr View Post
                            I think the is a clear distinction between accidentally Tking someone who you mistook for an enemy and intentionally Tking someone just because they blinded you with their flashlight.


                            It comes down to UYB
                            Who makes that distinction though? The person with the flashlight, or the person getting blinded? Either way I see a lot of cranky people because of the flashlight. =P

                            Comment


                            • #15
                              Re: Fri PM and Sat AM 30-Sep and 31-Sep (Rush...Open Beta)

                              Accidents will happen, but the fewer the better right? So, let's all strive to be more aware. Keep an eye on the mini map and know where blufor is and isn't. If you equip the taclight, be mindful to turn it off when not needed; and when you do have it on, and be aware of where you're shining it.

                              Edit: to be clear, don't shoot unless you're sure they're opfor. You may die a few times this way, but that should give you incentive to quickly adapt and be more situationally aware.

                              Comment

                              Connect

                              Collapse

                              TeamSpeak 3 Server

                              Collapse

                              Advertisement

                              Collapse

                              Twitter Feed

                              Collapse

                              Working...
                              X