AGGRESSION DOT FC meets Phreeze in battle {BSA Forum Dump}

**Phreeze** · 2010-03-19

Right...

What should of happened

Titans should of been in place to bridge perfectly from 9DQ to our destination system, we would arrive in system about 30-40mins before the POS came out of Reinforced, Carriers would position themselves on the edge of the POS, and RRBS be ready to duck outside of the POS and blow the crap out of the hostiles, whilst support ducked in and out of the POS to get tackles. Allies were to be on standby incase Caps were dropped onto the tower. Tower should of been saved, lots of hostile caps downed, and there ships dead.

What really happened

The titan that was ment to be bridging didnt show up, so an alternative titan pilot was brought in, this ment that nobody really knew the route that was setup, nor had the cynos in place, this slowed us down alot getting to the destination system, this made us seriously late to be into the destination.

Due to being late, goons were pretty much already ready and jumped into the system, this caused us to be at the safe tower, when we should of been setting up at the reinforced tower.

A warp was called, note that aligning would of alerted goons sooner, and bubbles would of been dropped, several people hesitated, FCs included, the warp was ment to bring everyone inside of the Reinforced POS, however... Warp in was 57km off the POS, and some people clicked warp late.

1 Carrier was stuck in a drag bubble, I expected more carriers to of warped, so I called for carriers to go up to a bubble, and warp down to the stuck carrier, between all the carriers we would of easily had the logistics to tank it out, however, only 2 carriers, one being myself did the warp up.

3 carriers were lost, and many RRBS and support killed.

Problems?

Clearly communication was a huge problem, from the bridging, to the warp ins. Another huge problems is assumptions being made by the FCs about fleets that havent really flown together for too long, thus things that would happen in a experianced, long time flying gang didnt happen.

Solutions?

In future more time needs to be allowed to get to target systems, aiming to get to a system 1 hour before a POS is out of reinforced is going to have to be a must from now on.

Less assumptions, more communication, ill admit that I should of been alot clearer with the orders, etc.

Conclusion

As I said on teamspeak, our PVP force is like a new sports team, for the first few matches mistakes are made, players do things they expect to happen, etc, but they begin to merge as a team. This is us, alot of different ideas, and ways of doing things, were improving as a whole, but were not quite league winning yet.

Carriers will be replaced quickly, and hopefully we will allow a few days R&R for people to gain new ships for this OP, I will personally ensure that new modules, ships and ammo are on the market in our home constellation so we can recover quickly.

This could of gone alot worse than it did, as the FCs, myself and treph, both agree we are to blame, not the person who was the warp in, nobody else, and we will do all we can to ensure that next time, we will rape alot of face!

/5n4ke

good write up snake and fitting up a RR Geddon now i suggest everyone else who was in support fit up a BS the more BS we have more dps we do and more logi available

another problem is telling people to load bs overview and then calling sub bs ships primary. we had goons out numbered they had 0 caps we had many and we got owned. we should have had many strike points around the pos to warp back and for the b/w. RR was fail plain and simple, dps wa fail also. we should have raped these gonnies instead we look like a bunch of shitties again... maybe we should re-evaluate our "senior fc's". Mauler is primary WTF i mean i know they put down some crazy dps (sarcasm there) In closing i just want to say WHAT THE FUCK!!!! oh and who was the fc i have no idea was there 6 of them?

I think from now on we should have Carriers seperated from normal fleet with a dedicated fc. When having all your fleet under one command it becomes confusing for carriers as it takes them several times longer to warp then others they can get stuck and what not alot easier. Also we should not ever fleet warp carriers, unless know in advanced. If your in a carrier and get a random fleet warp your gonna stop ship, so other then that good write up.

ince this was planned, there should have been a recon team there to get warpin bookmarks etc well before the CTA was even announced

we kinda went in there blind from what i could tell and even tho we outnumbered them and had caps, we nullified that major advantage through splitting our own fleet up and letting them pick off a third of us at a time.

aside from that what happend to the target calling, the ball was turned over every single play...

I don't understand why having 10+ carriers against 2 we did not made spider tank on pos (especially with rrbs gang).

Tower gunners did well. 3 Ravens, 2 drakes, 2 canes, 2 Apocs - killed by the reinforced tower. Judging by Goonwaffe KB - more than 1/3 of what our fleet did.

so far we have following incomplete reports.

https://killboard.goonfleet.com/battles/1760
http://blastkb.com/?a=kill_related&kll_id=15241

The fact that system had no bookmarks set prior to combat is very poor. There 20 officers in FC channel. One should have been sent to do proper recon.

Not me. I got up by alarm clock at 5 in the morning, brought command ship in fleet and commanded POS gunnery. Think it is enough.

----

Strategically all went wrong the moment that instead of saving POS we started to hunt enemy fleet.

On positive side having our allies in joint fleet was done well. Mess with POS password was bad, but we still managed to get it set at the last moment.

Its because the Fc's made no attempt to.... They ran the gang poorly and it was destoryed because of shitty leadership... Being able to make quick decisions is different then making good ones...

5n4ke wrote:

The problem is we should of been setup on the POS before the hostiles engaged it, problem is we wasnt due to the titan mishaps.

Getting everyone to the POS once the hostiles were there was always going to be a royal bitch, had we of been lucky and got everyone onto the same spot, it would of played out very differently, however, only 3 carriers that I saw left the Safe tower, and landed next to the Reinforced tower, thus a problem.

Agreed some panic happened, and poor communication, and very bad timekeeping all played there part.

Have bookmarks off pos warp to tactitcal get warp in on enemy fleet yada yada yada not that hard

TurboDog2 wrote:Well - you can blame this partly on me. I feel asleep and didnt wake up until well after the battle was over so I couldnt bridge anyone. However, from what I have heard, there were a few other minor problems. We can fix these and do better next time. Thanks to all who came and tried.

Due the delays we landed late so that caused us a lot of stress

I thank everyone for showing up you lot did everything very well

We need to work on the RR Bs`s we should be able to hold together and rep but we need more people to skill up

Question, do u think you did well?

Things got a little messy.

I wouldn't say it work out the way i expected

Not my best results

We can look at what happend, see how we can work better on the next op. not one person is to blame here, the RR bs`s where not repping the light support was not killing the dictors that's things we need to look at and work towards a better fleet

They spread fire to enough people that caused broadcast to flood because people weren't seeing that they were not fully primary. So by the time we locked the actual people that were primaries, it was to late. Not to mention calling targets went from BS overview to calling non BS targets... which caused the DPS to not be there, but the flood of RR requests i'm sure kept every busy trying to rep everybody....

Carriers should have been in their own channel and ONLY worried about the tower, support should have been able to handle themselves fine. Along with their own FC to focus on their specific task. There should have been bookmarks made all over the place prior to us even getting to the system, research done on whats around the POS whats going to be done by the carriers whats going to be done by support.

We should have been sitting at the POS well longer then an hour waiting for them to come. So even if the normal jump bridge wasn't there, we would have had plenty of time to make our way there and sit there and tell each other knock knock jokes while we waited.

We should have never went on the POS kill earlier, as it caused a lot of us to be burnt out for this op. I understand things being kept a secret, but ffs i thought we were moving our ships up, not shooting a POS.

Comms, mute everybody ffs. Only the FC and scouts should be unmuted, assign somebody who is in a cloaky or some shit to relay info thats put in fleet chat. The multiple FC shit needs to stop, setup wisphers between yourselves.

Agree the change at the being was bad but once my lag had gone the BS`s where to far away hance the change to closer targets

Another note, with target calling. I do not wanna hear anything but the primary name being repeated and in what ship type, until the target is down. Secondary repeated also, but not as much as primary. There was to many orders being past around between the different groups. You never said to switch off BS overview, so it took me a bit to catch we were no longer on BS.

i did say switch back to normal we might of had cross coms

Thanks for you imput i can work on this

he said to switch overview but coms was a mess so yeah all future big fleets everyone but scouts and command should be muted

I didnt get the prep time i needed due to work etc and the delay on the move up

and im still trying to work out TS3 there is a function (iv been told) to talk over people

Delegate it to trusted others that know what they are doing. Not having time to lead a big op should then be handled by someone who does have the time to prep. At least with something like dealing with a POS.

Sigh... Embarrassed

I wasn't able to make it but I am sorry for the losses.

I have a question for the FC - Before the op did you assign groups of 10 RRBS and ensure that prior to heading out each member of that RRBS squad had each other on their watchlist and one of those pilots in the wing of 10 was the circle/focus point?

Also, I'm really amazed that caps were not in a separate comms channel with their own FC, like the whole RRBS subject this has been discussed over and over again after other 'unfortunate' losses. If we were actually learning from our mistakes it would be ok, but we aren't are we?

**tekscru** · 2010-03-19

Stock up on ball gags goonies, they're going to rape alot of face next time.

**Rotor** · 2010-03-19

5n4k3 or what's his name is cancer in its purest form. He's killed more alliances than anyone else.

**Kalnov** · 2010-03-23

This whole "should of" mess makes my eyes bleed.

It's "should have" or "should've".

**tekscru** · 2010-03-24

Originally Posted by Kalnov

This whole "should of" mess makes my eyes bleed.

It's "should have" or "should've".

He would of wrote it like that if he were'nt a stupid cock gagger.

edit- this particular shitpost deserves a cricket

**Farham** · 2010-04-02

TurboDog2 wrote:Well - you can blame this partly on me. I feel asleep and didnt wake up until well after the battle was over so I couldnt bridge anyone. However, from what I have heard, there were a few other minor problems. We can fix these and do better next time. Thanks to all who came and tried.

Good ole TurboDog still a shining example of his former Intrepid Crossing glory. This is the guy that lost a titan because he used the same safe spot against RA 3 days in a row.

You can take the pilot out of IRC but you can't take the IRC out of the pilot.

**Lord Gabriell** · 2010-04-03

Originally Posted by Kalnov

This whole "should of" mess makes my eyes bleed.

It's "should have" or "should've".

Out of that whole wall of text, you had issues with that one example? You can't go more than a sentence /wo running into a typo or grammar error. I will give the person the benefit of the doubt, they probably don't speak English as a primary language.