After Action Review (AAR) Comments for 11 August 2018 25v25 Event

Strength in numbers

  1. Sethious

    Sethious Moderator
    Staff Member Donor

    Joined:
    Jan 1, 2014
    Messages:
    488
    Likes Received:
    776
    RSI Handle:
    Sethious_Artemis
    Issue: Armistice Zone Around Shubin

    Discussion: The plan called for using the Shubin mining complex which the Red Team was supposed to defend, however due to the armistice zone Red Team had to adjust on the fly and rearrange the original engagement zone to allow for a battle..

    Recommendation: Planning considerations for future events should include areas that allow for combat to occur. A Leaders Recon should take place ahead of time with representative from both Red and Blue teams present (preferably the leadership) to ensure that the area will work well as an engagement zone.

    -------------------------------------
    Issue: Party Invite System

    Discussion: Even though the event was published ahead of time, instructions were unclear on how to join up, and the current party system led to many last minute scrambling in order to get everyone involved with the exercise.

    Recommendation: Until CIG releases a party system that is more flexible and easier to begin and integrate large groups, all personnel participating in a scheduled event must register via the event google doc NLT two (2) hours prior to the event. This will allow for the leadership (Red/Blue Leaders, Squad Leaders, and Team Leaders) to add all their assigned personnel to their friends list. Hopefully as the game improves we can reduce the time required to get into the event.

    ------------------------------------
    Issue: Movement to the Engagement Area

    Discussion: While it is recognized that this game is still a work in progress, for event like this, which are ground based, we need to take into account using more than one ship to move all personnel to the engagement area. Having multiple people take multiple ships led to interdictions that caused the start time to continue to push to the right.

    Recommendation: For full ground based events teams will gather at the same location. Equipment lists will be submitted ahead of time and it is the individual players responsibility to have a load out prepared ahead of time. One ship will be used to move all Red Personnel and another for all Blue Personnel. This will limit the amount of excess ships in the area, and allow for teams to know who the ships are. For future ground based iterations the only personnel in ships should be those flying top cover to prevent harassment by players and npcs, and also allow for media coverage (I.E. streamers, video).

    --------------------------------------
    Issue: Night time causes issues with visibility

    Discussion: Again, we recognize this is not a finished game, but night time on the moons is terrible for combat currently. Participants would prefer to fight in the daylight to not give away their position and not be able to see others.

    Recommendation: With Day/Night cycles it will be difficult to find locations in sunlight for any given operation, but planners should take that into consideration and try to find the best areas for outdoor combat. If suitable indoor locations are provided as the engagement area it will help to alleviate this concern.

    ---------------------------------------
    Issue: Combat Power Inequality

    Discussion: While there were published guidelines for what equipment could be used, different people interpreted this in vastly different ways. Not allowing rail guns while allowing ground vehicles made for indestructible juggernauts.

    Recommendation: Establish Rules of Engagement (ROE) for any given exercise, this point will be reiterated several times in this Review, but it is an important point. Everything from when hostilities commence to which weapons platforms are allowed need to be spelled out for all participants. It will be the responsibility of both the Red/Blue Leaders as well as Organization Leadership acting as the White Cell/Observer Controllers. Participants who engage repeatedly in ROE violations will no longer be invited to events.

    ------------------------------------------
    Issue: Gear loadout with change of location

    Discussion: Due to a error in location selection teams were not viably equipped to handle the scenario they ended up facing.

    Recommendation: Again, planning prevents future issues. For formal events a Leaders Recon of the Area of Operations will help to drastically reduce this.

    ---------------------------------------
    Issue: Oxygen running out

    Discussion: While the event was not planned on lasting as long as it did, until CIG improves upon the oxygen system in game, especially for ground operations, oxygen depletion needs to be a planning consideration.

    Recommendation: Planning must include oxygen supply as a logistic point. Ensure that events either take place inside an oxygen environment or stick to a strict time table of operations. While this may cause some people to be left out, it will eliminate the event having to be called early due to personnel dying from oxygen deprivation.

    -------------------------------------
    Issue: Internal Leadership (Command and Control)

    Discussion: There was not an established chain of command prior to the execution of the exercise and personnel were confused as to their position within the structure.

    Recommendation: In order to help alleviate this in the future, personnel will be appointed to a set position within the established Task Organization for the event. The role you fill will be based on your interest in the position as well as input from Organization Leadership in recognized command ability. Leadership is a skill that can be learned if given practice and that is something we want to encourage in TEST. While not all of you have had to engage in this type of leadership before everyone will be given an opportunity within the given constraints of the game environment.

    -----------------------------------
    Issue: Comms Discipline

    Discussion: Talking over each other and friends talking can lead to information not being passed along. We recognized that there are some limitations to Discord and we want to try to improve upon those.

    Recommendation: We have some established brevity for communication, which we should try to enforce. Communicating between personnel should follow standard two way radio communications (You, this is ME, message) While we tried to separate some channels on the fly, lets use the temporary channel creation more in the future to limit the number of people who can talk over each other. Also, leaders of all levels should learn how to use Discord Priority speaking and it be limited to operational pertinent communciations. As Discord and the game itself improves with voice communication the layout of comms will matter. Add communication into the mission planning following standard mission formats. (I'm not dictating, but from personal experience as a going on 14 year US Army Officer the five paragraph operations order is great for laying out this information) Again we want to have fun with these events and having some structure can lead to more enjoyment as our groups in the verse grow.

    -----------------------------------
    Issue: Vehicle Liability

    Discussion: Once again we know this is not a finished game and vehicles/ships will have issues.

    Recommendation: If some vehicles and ships have known, common issues lets try to eliminate having them in the events that require a vehicle. Or find a work around in the mission planning that both Red and Blue Team leaders agree to.

    ------------------------------------
    Issue: No large forum for comments with leaders

    Discussion: No one wants to start large arguments with their fellow members especially in voice chat with large groups. Some form of private chat or channel to take issues need to be worked out.

    Recommendation: TEST Leadership, to include all Staff Members should be available and knowledgeable of the event to help handle issues between personnel. Everyone who has valid critiques and comments should be able to have a platform to bring these concerns for events especially as we give more and more personnel the opportunity for leadership within the events. Observer Controller positions must be leveraged more to facilitate this.

    -------------------------------------
    Issue: Inadequate Mission Briefing

    Discussion: For these very early iterations of event running, everyone should recognize that the game is constantly changing. However, if large, formal events are to take place some form of mission briefing for both sides should be available. While for this event we had very good hand outs for the team leaders, this information was not widely disseminated.

    Recommendation: In order to combat both lay arrivals and to disseminate information, a show up and mission brief start time will be established well before the actual mission start times. Late arrivals will be catered to on an individual basis, but it is the responsibility of the participant to show up and be prepared. The leadership that will be appointed for you for the operation is also responsible for contacting you and if required pulling you into a separate channel to get you up to speed. Events will be handled on the needs of the many and not be delayed by excess questions by unprepared personnel. The leadership is responsible for providing the information ahead of time in a prepared manner. We want everyone to show up and continue having fun like we did today, but not waste the time of others with late arrivals.
     
  2. Sethious

    Sethious Moderator
    Staff Member Donor

    Joined:
    Jan 1, 2014
    Messages:
    488
    Likes Received:
    776
    RSI Handle:
    Sethious_Artemis
    While I understand this is not all encompassing I want this to be the venue for further discussion, recommendations, and planning the next events. Every event I can participate in you can expect me to provide the same level of feedback. Please feel free to comment as you see fit. Any posts that are not conducive to this will be moderated as seen fit.

    Thank you again to @IcaroSP for putting together the event and everyone participated I can't wait until the next event.
     
  3. Ploeperpengel

    Ploeperpengel Commander

    Joined:
    Jun 17, 2018
    Messages:
    71
    Likes Received:
    190
    RSI Handle:
    Sadis
  4. Ploeperpengel

    Ploeperpengel Commander

    Joined:
    Jun 17, 2018
    Messages:
    71
    Likes Received:
    190
    RSI Handle:
    Sadis
    Another rule of thump: have your Handle in SC match your Dicord Handle somehow to prevent friendly fire (changed that now ;))
     
    #4 Ploeperpengel, Aug 12, 2018
    Last edited: Aug 12, 2018
    Rear_Intruder likes this.
  5. Xist

    Xist Admiral
    Donor

    Joined:
    Jan 16, 2016
    Messages:
    571
    Likes Received:
    1,600
    RSI Handle:
    Xist
    Many thanks to those who helped plan and organize this event! It was a lot of fun.

    In talking with some folks last night, one possible way to do a battle like this in the future that solves many of the problems might be something like this (modify to your taste):

    - 2 teams, Red (attack), Blue (defend)
    - 2 Constellations, 1 for each team
    - 1 Rover
    - 2-3 fighter escorts (neutral, help fight interdiction, NPC aggro, griefers at event)
    - ALL QT to location simultaneously, in 1 huge party
    - Both Connies land in the same place initially.
    - Unload Rover here. Rover is now the primary objective for Blue to defend, for Red to attack
    - Move Blue (defend) Connie back a bit. 500m maximum. Players are still inside getting full Oxygen tanks.
    - Move Red (attack) Connie to its starting position. Again probably 500m maximum in some direction. Players are still inside getting full Oxygen tanks.
    - Fighters fly patterns overhead keeping NPCs and/or other players at bay
    - At this point, everyone drop group. Form 2 new parties so nobody can see the people on the other team.
    - When the event starts, Blue team gets a head start to get defensive positions around the Rover
    - Shortly after Blue leaves their Connie, Red does the same. (few minutes, not more, due to Oxygen depletion)

    Basically this keeps the spirit of the defend/attack, but it solves the problem of everyone getting to the same place at the same time, and it solves the oxygen problem.

    If Red gets ahold of the Rover and drives off in it, they win. Other than this, Blue is not allowed to use the Rover for fighting. It is a stationary object unless/until Red gets into it and steals it.

    I'm sure there are other ways to solve these issues, but this sounded fun so I wanted to share.

    Thanks again for a fun event, can't wait for the next one! :slight_smile:

    Edited: Added drop/reform group step which was another issue we had last night.
     
    #5 Xist, Aug 12, 2018
    Last edited: Aug 12, 2018
    marcsand2 and Sethious like this.
  6. marcsand2

    marcsand2 Grand Admiral
    Donor

    Joined:
    Mar 15, 2016
    Messages:
    4,665
    Likes Received:
    14,558
    RSI Handle:
    marcsand2
    2 playing teams, 1 support team of fighters and transport/oxygen
     
    Cauac likes this.
  7. Sethious

    Sethious Moderator
    Staff Member Donor

    Joined:
    Jan 1, 2014
    Messages:
    488
    Likes Received:
    776
    RSI Handle:
    Sethious_Artemis
    Definitely agree on the support team. I spent too much time shooting down pirates and players coming after the ground folks.
     
    marcsand2 likes this.
  8. marcsand2

    marcsand2 Grand Admiral
    Donor

    Joined:
    Mar 15, 2016
    Messages:
    4,665
    Likes Received:
    14,558
    RSI Handle:
    marcsand2
    If we get 50 people in one instance, then there won't be any players to shoot down, only TESTies, but 50 in one instance still will be a huge challenge.
     
    Bambooza likes this.
  9. Sethious

    Sethious Moderator
    Staff Member Donor

    Joined:
    Jan 1, 2014
    Messages:
    488
    Likes Received:
    776
    RSI Handle:
    Sethious_Artemis
    Still will need the support team. Pirates alone almost fucked up the Starfarer. If I see a concept of operations one slider I’ll provide feedback. We aren’t at needing approval yet but a solid conop will equal better all around attendance.
     
    Cauac and marcsand2 like this.
  10. Megamedes

    Megamedes Rear Admiral

    Country:
    Canada
    Joined:
    Aug 12, 2017
    Messages:
    10
    Likes Received:
    34
    RSI Handle:
    Humma_Kavula
    Sethious your absolutely correct with the detailed notes above, thank you for stating the problems and solutions. I would also agree this was due to an inexperience element when forming a new type of event within a testing environment. For this upcoming weekend, I would propose making almost a charter style of rules that should be taken in account for various situations. I will most likely not be able to make it this weekend. But I will be around on Friday to help with such charter if agreed.
     
    marcsand2 likes this.
  11. spectre44

    spectre44 Captain
    Donor

    Joined:
    Feb 4, 2017
    Messages:
    50
    Likes Received:
    165
    RSI Handle:
    spectre44
    Great debrief notes, I was so pissed I couldn't attend last Saturday. Glad to see the notes mention people need to be signed up and contacts added prior to event in order to participate. I think sometimes we are overly accommodating and we spend an inordinate amount of time getting people added and what not.
     
    Cauac and marcsand2 like this.
  12. Cauac

    Cauac Lieutenant

    Country:
    Finland
    Joined:
    Aug 8, 2018
    Messages:
    4
    Likes Received:
    13
    RSI Handle:
    Cauac1
    Also this would have not been a problem had we all travelled as a one group to the location. The Starfarer got into trouble bcs 1. they were unable to identify their position to air support 2. They were unable to QT to location that was named as a rendevouz point by the air support.

    Once we all were at the same location we had an easy job taking care of the griefers and the NPCs. In any case, as long as we don't have a full server of 50 Testies, I wholeheartedly agree we need a support/security team.
     
    marcsand2 likes this.

Share This Page