AAR AAR | Wardogs | Wardogs Saturdays 003| 10OCT26

[Zaren.T]

DEPARTMENT OF THE ARMY
S3 BATTLE STAFF
Headquarters
7th Cavalry Regiment
COMBAT AFTER ACTION REPORT​

Name of Combat Mission: Wardogs Saturdays 003
Campaign of Combat Mission (If applicable): N/A
Number within campaign: 3/5
Game: Wardogs
Server Hosted on: [7CAV] Tactical Realism | discord.gg/7cav
Date of Combat Mission: 10OCT2026
Time of Combat Mission (Zulu): 1900Z
Mission OIC: N/A
Mission Controller: Corporal Zaren.T

Number of Attendees: 100 ( 35 Cav members )

7th Cavalry Personnel Involved in Action:

1. Colonel Budd.D
2. Major Dread.M
3. Major Landini.T
4. Major Hilberg.A
5. First Lieutenant Laui.M
6. Lieutenant Colonel Ronen.R
7. Second Lieutenant Sibley.K
8. Warrant Officer 1 Coner.J
9. Sergeant Rutkowski.P
10. Sergeant Taylor.C
11. Corporal Zaren.T
12. Corporal Lucander.P
13. Corporal Argentini.E
14. Corporal Ashie.L
15. Corporal Jinto.H
16. Private First Class Sprouse.T
17. Private First Class Hill.K
18. Private First Class Brosh.B
19. Private First Class Molitor.K
20. Private First Class Darmody.J
21. Private Church.T
22. Private Deeks.T
23. Private Dent.M
24. Private Trent.S
25. Private Church.T
26. Private Jordan.D
27. Private Gentry.A
28. Private Blackwater.D
29. Private Stevens.J
30. Private Pease.J
31. Private Remington.J
32. Recruit Angels.M
33. Recruit Winter.M
34. Recruit Frost.I
35. Recruit Garcia.N

Non-cav on Discord:
36. Wki


If you are missing from the AAR post, please send me a PM.

 

[Molitor.K]

DEPARTMENT OF THE ARMY
D/DEVCOM
7th Cavalry Regiment
COMBAT AFTER ACTION REPORT
​

Element Callsign: Gunslinger-1 / Pathfinder / Buffalo
Element Leader: Private First Class Molitor.K
7th Cavalry Personnel Within Element:

1. Sergeant Taylor.C
2. Corporal Ashie.L
3. Private Blackwater.D
4. Private Dent.M
5. Private Jordan.D
6. Private Pease.J
7. Private Remington.J
8. Private Stevens.J
9. Private Trent.S
10. Recruit Angels.M
11. Recruit Frost.I

Sustains:

• Group accomplished core aim of impacting the battle space and sustaining combat while testing this configuration. 1st game was a win and the second one was looking promising until the server crash.
  
  
• Organizing and assigning roles definitively enabled tactical flexibility. Gunslinger-1 was able to win gunfights in the hot zone, breach and destroy FOBs (2x), as well as vehicles (2x APC, 1x Minigun LB).
  
  
• Most members outside of leadership reported being able to make a profit.
  
  
• Comms between callsigns were solid and productive. Buffalo was able to assist with insert and resupply. Recon was able to call targets effectively and lay the ground work for several assaults.
  
  
• Squad only suffered two wipes in an hour and a half of play. Succession seemed relatively productive with down members radioing that they were uncon and handing command over.
  
  
• Buffalo conducted full squad landings throughout the night which was a really nice change of pace and awesome to get to be a part of.

Cons:

• Slotting into sides while seeding would have been basically impossible without assistance from S3. Side balancing prevented getting what was over half of the seed pop from getting on the same side.
  Future Mitigation: Potentially run multiple organized squads on each side. Potentially warn players ahead of time during event postings by reserving slots that will be assisted by S3.
• The assistance by S3 triggered some negative feedback from players when sides ended up imbalanced until the server fully populated.
  Future Mitigation: See above.
• Using purely in game comms was very challenging for Gunslinger-1. Fireteam cohesion drifted in and out of viable direct comms range and several members had concerns with enemy ability to hear the direct chat.
  Future Mitigation: Run a trial where fireteam elements are their own, in game squad and use Discord to coordinate leadership elements. Will need easing of S3 requirement to be in single Discord channel for Op credit.
  
  
• Couple of team members had an issue with change in play style from run and gun to more methodical and said it felt very slow.
  Future Mitigation: No current recommendation as some of this comes down to familiarity with the game and coordinating at this level. Something to keep an eye on moving forward though.
  
  
• Fireteam visibility with combined squad was difficult to keep track of. A few members struggled to distinguish which fireteam they were intermingled with.
  Future Mitigation: See trial with fireteam elements as separate, in game squads.
• Buffalo gave feedback that ACE reports were a bit lacking supported by report of a request for new armor not getting passed up through one of the fireteams.
  Future Mitigation: Teach full ACE report as part of training plan, also see Comms issues resolution.

MASCAS Analysis

MASCAS Events
This is a separate section I'm including more for leaders moving forward as we look to refine tactics and individual skills. These are my own musing about what went wrong. I'm extra. Let me be...

MASCAS Situation 1: Sandwich & Casualty Paralysis
Incident Timeline:
00:05:00 - Squad is attempting maneuver towards T1 and is stuttering in movement to objective as sniper fire 300m to the rear is coming in.
00:05:30 - First Casualty Outside T1 - Team stops in foliage to recover casualty.
00:05:33 - Second Casualty Outside T1 - First shooter drops member ~5m from first casualty.
00:05:41 - Third Casualty Outside T1 - Second shooter drops member ~5m from first casualty.
00:05:44 - Fourth Casualty Outside T1 - First shooter drops member ~5m from first casualty.
00:05:50 - Fifth and Sixth Casualty Outside T1 - First shooter drops members ~5m from first casualty.
Unknown - Seventh casualty occurs and two members from maneuver team are left pinned at base of tower ~ 40m from friendly casualties.
00:06:10 - Remaining members breach T1 and kill two before falling.

Conclusion: Movement was indecisive and squad did not seek hard cover when decisively engaged from multiple angles, lingering around casualties rather than maneuvering decisively to eliminate the threat. Enemy elements were able to engage from an elevated position for an extended period and caused mass casualties with small arms, despite being outnumbered 3:1.

Mitigation: When engaged in the open immediately seek cover/concealment and do not sit on casualties. Maneuver if necessary to avoid being stuck in a kill box. Preemptively, maneuvering through terrain using cover instead of straight path may have avoided the situation entirely.

MASCAS Situation 2: Split Fireteams, Friendly Fire, and the Power of APCs
Incident Timeline:
01:00:40 - Squad is split with fireteams ~150m apart. One is pushing to close with an area known to contain contact. The other is moving through and clearing buildings to secure the first's flank. APC had previously been spotted in proximity and was presumed to be heading to enemy fob.
01:00:45 - First two casualties are taken by the team attempting to push into the known contact.
01:00:48 - Third casualty is taken when 3rd team member pushing into clear killer of first two by a new shooter ~ 50m away.
01:01:15 - Fourth casualty is taken when teams encounter a third shooter at building with existing casualties.
01:01:27 - Friendly fire incident occurs when member solo clearing runs out of house from direction of contact. Player is wounded but not killed.
01:01:28 - Fifth casualty is taken when 3rd shooter engages friendly fire recipient and kills him almost instantly.
01:01:45 - Other fireteam responds to call for help and is about half way back to team.
01:02:03 - Sixth casualty is taken when fourth enemy combatant frags casualty positions.
01:02:13 - Seventh casualty is taken from fourth shooter.
01:02:29 - Eigth casualty is taken from fifth shooter.
01:02:57 - Final casualties are taken and call to reset is made.

Conclusion: SL made a critically incorrect assumption that APC was deploying to enemy fob and split fireteams to deal with what was believed to be low levels of contact. Splitting of the teams allowed the squad to be taken apart piecemeal over a long duration when concentrated engagement may have won.

Mitigation: APCs can be very dangerous and large numbers of players can deploy through them, quickly changing the terms of a fight. Treat APCs as the threat they are and do not split teams in the vicinity of one. The situation can turn very quickly.

 

[Rutkowski.P]

S1 Locked.

 

[Mobius.T]

S1 Operations Processed

---

Following trooper is ineligible for Ops Credit per 7CAV-DR-014
Private Engel.M - Does not hold the status of a Private w/ graduation of Boot Camp, and/or had been assigned to a squad at the time of operation.
Colonel Budd.D - Does not hold the status of an active trooper in the 7CAV.