I have just had my single worst OP as aCO… And no this is not some cope thread but chance to look at why things had gone wrong and why such things happen.
First off lets look at the set up… 3 SO and Me the ASO on the map Chance’s Claim during lowpop. Forcon not only lived but also got the sensor tower up while also killing some number of xenos.(not quite sure as to the number.)
Simple by the books plan, bravo on fob on LZ1 the rest of the techs were to move east to take and get comms up while the rest of the squads move on mass north to north east to link up with forcon.
VARY simple by the book plan. nothing of note.
At first the Op had gone just fine the mass of marines pushed into A-blocks and made their way all the way up to BBall and got stalled out a bit… We got a cords from a squad lead i believe the delta lead.
They tell me the cords will need a fallback… so we dial it, give fallback order to clear way for the OB and fire a cluster OB on BBall. The marines got out but it was dangerclose. But with the new ground cleared we were able to push up to the reacters mouth with not too many issues.
Things started to fall apart when issue with req started to pop up. First off both me and the QM had lost the FOB cords so FOB Seemed to be understocked. Next the front line keep asked for front line crate drop but due to issue of communication it was delayed for long time.
Now when i think back about it there was complaints of req being slow from the very start of the round so add that in with the issue that cropped up its clear to me the QM was ether very rusty or new.
Near the end of the round a SO had asked for req clearance… likely to replace the QM or give aid, was not quite sure as to why i simply knew that req needed unfucking, so i give the SO the needed clearance.
Now we had gotten bogged down at the mouth of the reactors the xenos had some warriors and carriers with nice little capping area set up that made it hard to push one side of the reactors. this in the end netted the xenos a quite a few caps.
Now to break the stalemate the squad leads had gotten us OB cords for our HE shell. First squad alpha cords were loaded in. But the OB needed to be chambered as such the a So ran off to do that before i needed to even ask.
But by the time the OB was chambered the Delta lead had gotten me OB cords… as they had gotten me some good cords before i trusted them. i asked where the cords were placed and they said within the reactors. So i had the SO override the old cords and input this new ones…
Only for it to Hit fob…Yes it hit fob…i at least didn’t see any KIAs from it nor heard any over chatter but was told in OOC at the end of the round it gibbed 4 lads…
Now this was infact not the death nail, yes it was waste and may have costed us some lads but they were likely not mainline combatants. Yes it cold to say so but its likely a large part of the lads that were killed would not been on the front anyways. (that being said this is mostly just conjecture)
No the frontline has simply been ground down, due to the being capped and being killed faster then the medics could heal. Add in the wave of burst xenos having had time to grow the waining front was wiped.
I called out a mass KIA on the frontline ordering any medics to get there… only for me to noticed the xenos wiping out the front just as i gave the order as such i called a full fallback to fob. noting that fob could not hold i ordered the evec and for the alamo to take flight to LZ2 in hopes of the remaining men being able to rush to the mass of dead at the reactors.
But the alamo had not followed orders and simply headed up top side. Now in retrospective the bodies were dead for much to long meaning that they couldn’t be saved even had the alamo followed orders.
At this point i knew we were fucked so by the time hijacked happed had kind of halfassed it. resigning to try my hand at RPing going down with the ship… it was anticlimactic to say the least.
NOW WHAT HAD GONE WRONG?
First off it had been a long time since i had played Command and the interfaces had change to some thing i had little use to. This meant i was slow to get things done.
Next the fact i was playing ASO but had 3 SO’s. Now i am not about to just shit on them, as they did in fact try to do their best to get things done. Issue was that I THE aCO thought i could trust them to get things in order they were working on with out my interference.
This meant i left the SO’s to their own devices this was clearly a mistake not because they were incompetent but because there were stepping over each other and me trying to get everything in order.
Simply put the chain of command broke down, leading to increase confusion as i had not properly delegated. while the ground forces couldn’t get what they needed. This was in part due to my rustiness leading me to be slow to issue commands where as clearly some the SO were infact not rusty. This ended up leading to the SOs in effect taking over command as i had little input as they had been getting to matters faster then i had.
All in all i think my problem was that i was too use to doing solo CIC work so i lacked experience commanding SO’s. Next i believe the SO’s where too willing to put themselves at the forefront of commanding the OP while lacking the confidence to fully try to take over overall command. (Not a mutiny mind you just asking for command access and geting me to unfuck req.)
Next off the matter with the OB…frankly i am going to blame it on req. Fact was the cords i was given was with acceptable margin of error with the cords that alpha got me prior. it was with in a 10 tile difference from what i recall. Add in the fact that delta lead had gotten me good cords before things seem all well to fire off the OB.
Now as to why blame req… Fact was we had issues with getting front line cords out also the issue with Req losing the fob cords meant there was a lot of chatter going on about cords in the chat.
Now i think one of three things had happed… first i copy the wrong line cords from the chat log and was in fact giving the SO the cords or FOB. If this was in fact the case that means it was all my fuck up.
second because of the whole issue with supply cords and the pad perhaps the SO had some how loaded the cords wrongly and mixed up crate drop cords with the OB cords… leading to fob being bombed.
Third perhaps the delta lead had some how given me cords that were in fact meant for fob… after all req had needed to get new cords so perhaps the delta lead had gotten them some at one point and didn’t clear their clipboard of the old cords. meaning they had given me the wrong cords… still that would have meant i miss read the cords as then it would clearly not have been with in the 10 tile margin i saw before.
still i will likely never know as i didn’t save the chat logs.
But the fact is the OBing of fob had likely happend due to my inability to unfuck the issues with req, leading to increase chatter about cords.
OVERALL ASSESSMENT
There was break down of support due to issue of lack of clear and concise delegation. This likely leading to the bombing of FOB due to crossed lines of communication. The unwillingness of the aCO(me) to step away and deal with matters one at the time leading to issues not being dealt with.
The inabilty of the aCO(again me) to ether assert sufficient control over the CIC or step down and let some one who could. leading to a break down of the chain of command which in turned cause the SO to be unsure what to do or if some one had already got to it.
There was a overall lack of clear and concise communication compounding the matters. Last off… the failures of req had causes a compounding issue with the problems of CIC.
Was command to blame for the lost the round? Yes and no… CIC clearly didn’t help matters but there was clearly other underlaying issues at play along side strong xeno cap game. There was definitely a strong case to be made it was CIC fault but in my assessment even if we had been better CIC that round there would have been still fairly high chance of failure.

