Clusterfuck Roams – SOP

1st Rule of Clusterfuck Roams…

“Don’t fly what you can’t afford to lose!!!”


 *** A#1 Rule of any Fleet Op – Listen to the FC! ***

I am brand new to FC’ing and I can guarantee you that I will make mistakes.

Hopefully the experiences I do have in PvP Fleet Ops under some of the best FC’s in the game have rubbed off and these Clusterfuck Roams won’t regularly end in massacres.

There is a lot of info below but being brand new at this I’d truly appreciate it if you at least took a cursory glance through it to familiarize yourself with my outlook and mindset towards FC’ing and PvP Fleet Operations.

 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

Chat Channel & Voice Comms Protocol:
TeamSpeak – We’ll pick a PvP Channel on TS during form up.
Fleet Chat Channel – For general chit-chat, fleet destos, and scouting intel. Please don’t fill up Fleet Chat with spam messages
Logi Chat Channel – If we have Logi, please set up a separate Chat Channel from the Fleet Chat to organize on.
Local Chat Channel – Please no ‘Smack Talk’ in Local, lets be respectful, give a “gf” and move on.

Fleet Doctrine
♦ Form Up Location
♦ Planned Route
– This information will be sent out via an in game email

♦ Nothing guaranteed, all loot we get should be passed to the FC upon our return home. Clusterfuck Roam losses will be replaced out of this and anything extra will be added to the Alliance SRP.

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

Clusterfuck Roam Pre-flight Checklist (should be performed before you Undock.)

1) Check your clone – do you have implants in, are you okay losing them?
2) Check Insurance on the Ship
3) Check Repair Status
4) Load Preferred Scripts.
– Sensor booster
– Range
– Resolution
– Various EWAR
– TD-SD Scripts
5) Load Ammo
– Missiles
– Gun charges
– Probes
5) Drones.
– What type are they, are they damaged?
6) Check Cargo Bay, Load Misc
– Cap Boosters
– Nanite paste
– Extra ammo
7) Identify ship role/range – check optimals on weapons, ship’s speed, etc…
8) Identify Leadership abilities, check for proper Squad
9) Setup Watch list (this can be done before you undock):
– FC, XO, scouts, squad members
– Remote rep targets for logi
10) Check Voice Comms, Mic Check on proper channel – can you hear the FC, XO and scouts clearly?

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

Clusterfuck Roam In-flight Checklist (performed as soon as you are undocked and safe.)

1) Check Default Orbit and approach settings
2) Check Overview, is it properly set up, review and assign proper Overview Tab Settings (ie: Clear blues/militia/fleet from overview). If you don’t know how to do this or have never messed with your Overview ASK!!!
3) Module Setup
– check Module Activation Order
– Check Scripts
– Activate Sensor Boosters – lock times are critical and you should be ready for combat in a moment’s notice.
4) Travel settings, ensure when you set a destination you have the same settings as the FC (ie; choose shortest route, system avoids, etc…)

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

Combat Engagement Checklist

The Approach
1) Warp in
2) Activate non aggressive modules during the warp in
– Sensor boosters
– Hardeners
– Damage Controls
3) Identify Targets
– Zoom out
– Check your overview
– Sort by Name
– Listen to FC!
– Identify Primary and Secondary if called (The Primary is the target you should be shooting. The Secondary is usually next in line to get blown up.)
4) Approach Primary at weapons Optimal
5) Release Drones (the FC may ask you to assign to a specific fleet member, if you don’t know how to do this ASK!)

The Engagement
1) Engage Primary Target
– Ctrl-Click on your Target in the overview.

*** Don’t spread your damage, put all your DPS on the primary called by the FC! ***

2) Activate Warp disruptor
– call “Point on Target Name XXX” on comms
– FC may call to spread points around, make sure you call your point
3) Activate Web
4) Activate Painter
5) Activate any Missiles/Turrets for targets in range
6) Activate other EWAR Module
– Sensor Damps
– Tracking Disruptors
– ECM (If the Jam is Successful, call the “Target Name XXX –Jammed ” on comms)
7) Check Drone Status
– Reassign Target
– Pull in if damaged
8) Repeat for Next Target
9) Prepare to Warp-Out.
– Only Warp out on FC Command or all is lost
10) If you are going down…
– Overheat all your Modules!!!
– Select a celestial object and align to it
– Spam warp button till you GTFO of there.

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

If Logi is available make sure you know how to Broadcast for Reps!

Also… broadcast early! Yellowboxed? Broadcast now! Redboxed? Its probably too late but try not wait until you are low in shield (or armor) to broadcast.

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

PvP Fleet Communications

*** A#1 Rule of PvP Comms… If you’re not the FC – NEVER EVER say the “J” word! ***

There is a solid write up on PvP comms protocol here:

It is an even longer read than this but if you’re planning on coming out for PvP Fleet Ops on a regular basis it’s got some really good information – to get us all on the same page I’ve cut out some of the basic concepts of Fleet Comms from that post.

The key reason for use of voice communications in PvP operations is for the quick and efficient transfer of information from the FC to members of the Fleet or for transfer of information from the Fleet scouts to the FC and Fleet members. As a result, any voice communication that doesn’t meet one of these two goals is — on the whole — bad for the operation.

Clear Comms – During a PvP operation, if you don’t have orders to convey to the Fleet, or information to convey to the FC, it’s generally best to keep quiet in the voice communication channels.

Chit-chat – Humans are humans, and the defining characteristic of humans is that we love to talk. As a result, a good FC will try to keep communications open to general chit-chat as much as is possible.  Still, do what you can to keep the communications channel clear!

“Battlecomms” – Once actual PvP combat begins or is imminent, the FC or scout may call for “Comms”, “Tight comms”, “Combat comms”, or “Battlecomms”. This means to keep the communication channel clear unless you have critical information to relate. If you do have critical information, you can ask for a break in communications by saying “check”, “break”, “break break”, or “break” and then your name.  Say this once, then wait for the FC to acknowledge you — usually by saying “go break” or “go” and your name — then you can share the information you have.

Giving orders – Be careful about giving orders — orders are the domain of the FC. If you see something obviously incorrect happening (the FC has asked you to recall drones, and one of your Fleet-mates still has drones out), you can remind your Fleet-mate to recall his drones. The one exception to this, though, is the word “JUMP”. NEVER EVER say the “J” word unless you are the FC.  Tensions are high during PvP operations and if the Fleet is at a gate awaiting the orders to jump, you saying it unnecessarily could cause someone to jump through the gate

Broadcasts – Sometimes the FC will broadcast commands to the broadcast window, sometimes he won’t. Sometimes he’ll remind everyone what they’re supposed to be doing, sometimes he’ll be too busy doing other stuff. PS… If there is logi available make sure you know how to broadcast for reps!

Local Chat – Never say (type) anything in LOCAL chat during Fleet Ops unless your FC gives explicit permission. This is typically done only to say ‘gf’ (good fight) after a battle.

Destination – If the FC sets a destination, make sure you have the same autopilot setting. If he doesn’t specify, ask in Fleet Chat if autopilot setting should be ‘shorter’, ‘safer’, or ‘less secure’. You can change Autopilot setting by pressing the big ‘A’ icon on the left side of your Route Display, on top left of your screen.

Attacking – Do not attack unless the FC gives the order. If you attack when you shouldn’t, you could get stuck on the wrong side of a gate if the FC decides he’d rather have the Fleet elsewhere.

Targets – The Primary is the target you should be shooting. The Secondary is usually next in line to get blown up.

Get blown up? – If your ship is destroyed, your first priority is to try to get your Pod out. Once out let the FC know what he’s lost by saying your Name and minus one “ship type” or if Comms are busy link your name and loss in Fleet Chat. If you have been podded, let him know that as well.

Post Fight – After a fight, only loot or salvage if the FC says to do so. He may want specific individuals to loot. After the Op all loot and salvage goes to the FC.


PS… If you’re not the FC – NEVER EVER say the “J” word!


And… don’t forget the A#1 Rule of any Fleet Op – Listen to the FC!!!

3 thoughts on “Clusterfuck Roams – SOP

  1. Pingback: Háttr Skapari | New Eden Vagabondage

  2. Pingback: Veðr Járnleikr | New Eden Vagabondage

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.