TRS - Fitting Discussion: Armor Logi Frigates

Logistic ships are an important backbone of more advanced fleet operations. In the past, there was exactly one T2 hull for each race available to fulfill that role.

Since Retribution we have T1 logistics cruisers and frigates available. That opens the way for pilots to grow into the role of "healers" without having to train up to a T2 ship at first.

For the new pilots who would like to train for that role, the logistics frigates are an ideal entry point. I will feature all four of them, but I will begin with the two armor logi frigates.

The Amarr Inquisitor is the one I have most practical experience with. A good standard fit for that ship looks like this:

[Inquisitor, Logi Standard]
400mm Reinforced Rolled Tungsten Plates I
Pseudoelectron Containment Field I
Energized Adaptive Nano Membrane II
Energized Adaptive Nano Membrane II

Cap Recharger II
Experimental 1MN Afterburner I

Small 'Solace' Remote Armor Repairer
Small 'Solace' Remote Armor Repairer
Small 'Solace' Remote Armor Repairer

Small Remote Repair Augmentor I
Small Remote Repair Augmentor I
Small Remote Repair Augmentor I

The Inquisitor's drone bay has room for one small drone. Personally I would suggest using a Warrior II because it can be directed at targets quickly to get on killmails. Using a single repair drone or ECM drone is hardly effective.

This ship is quick to train for and easy to fit, but I would suggest training Amarr Frigate and Remote Armor Repair Systems to V as soon as possible. Both skills reduce the amount of capacitor needed by the RR modules. Being cap-stable is important for this ship, as I will explain.

To begin with, you want to be able to run your RR modules permanently if possible. You will also be in need of something to help you survive, because logi ships tend to get primaried often. Apart from a decent tank for a frigate, you will rely on a low signature and speed to avoid incoming damage. That makes the ability to permanently run your afterburner particularly important.

With your extended range for the RR modules, you can stay out of range from the main fight, and you should. Pay special attention to ships with stasis webifiers and energy neutralizers. Both can mean the end of your ship really quickly. Enemies with medium to long range are best dealt with by keeping your radial speed up to challenge the tracking of their guns.

Often fits for this ship will use an anti-explosive rig. Personally I consider the speed-tanking advantage of running your afterburner permanently a better asset in combat than the extra explosive resistance. So I prefer going for three Remote Repair Augmentors to stay comfortably cap-stable with everything running.

The Pseudoelectron Containment Field is chosen above the Internal Force Field array because of the price. If ISK is not an issue, and you are not worried to have a needlessly expensive frigate on your list of losses, by all means, go for the meta 4 version.

Of course you are not only there to avoid damage, but mainly to repair it.

The main challenge for the beginning logistics pilot will be to time their repairs properly. Because armor repair becomes effective only at the end of the cycle, you need to be proactive. Keep as many friendlies as possible on your watchlist and pre-locked. Start repairing once they take damage. Do not wait until they enter armor or your reps could be too late. Especially in frigate fleets one missed cycle can mean the the difference between exploding and surviving.

For those who do not have Amarr Frigate trained, the Navitas is an alternative.

This weird-looking fish-like ship has one less low slot but an extra mid. This means a less effective tank, but on the other hand you gain a bit more versatility. You can fit an ECCM in the extra mid to protect yourself against electronic warfare, or you could provide some EWAR support like in this example:

[Navitas, TD Logi]
400mm Reinforced Steel Plates II
Damage Control II
Energized Adaptive Nano Membrane II

Experimental 1MN Afterburner I
Cap Recharger II
Balmer Series Tracking Disruptor I, Optimal Range Disruption Script

Small 'Solace' Remote Armor Repairer
Small 'Solace' Remote Armor Repairer
Small 'Solace' Remote Armor Repairer

Small Ancillary Current Router I
Small Remote Repair Augmentor I
Small Remote Repair Augmentor I

The main problem with the Navitas is it's powergrid. Even with maximum skills you will need a rig or an implant to fit propulsion, three reppers and a 400mm plate. Even with a Tungsten Plate you will have too little powergrid, so better use that rig and fit a T2 plate if you have enough CPU with your skills. Because you are forced to use a powergrid rig, you will have a much harder time to get this ship cap-stable. Only with maximum skills in Afterburner and Fuel Conservation in addition to others that's achievable.

Personally I find that the Navitas is a bit broken in that respect. With maximum skills this fit should be possible without a rig. It's only 0.75 that's missing!

In total you end up with more hitpoint buffer, but still a good 1000EHP less than the Inquisitor because of lower resists. The signature of the Navitas is slightly higher, but it is also faster than the Amarr ship. Together those factors balance each other out nicely.

Just like the Inquisitor, the Navitas has space for one drone. Again, I'd suggest a Warrior II.for the killmails.

This concludes the first part of logistics frigates discussion. The next time I will deal with the shield versions: The Burst and the Bantam.

TRS: Enaluri 2103

Yesterday Friday the 21st of March, the Faction Warfare system of Enaluri was the site of a large fight escalating from cruisers to capitals and finally to supercapitals. It involved several different parties and made for an interesting story. I am not attempting to write a complete and concise battle report here, but rather a single Gallente Militia line pilot's perspective. As a consequence, the following can contain inaccuracies and bias.

The beginning

Gallente Militia is currently in a state of resurgence. After a recently successful campaign to recapture the Placid system of Oicx, our military command had set it's sights on Enaluri in Black Rise. I had just listened in to our CEO instructing a new pilot when the call came to join a cruiser fleet to go fight for system control. I was a few jumps away but got into my trusty Vexor to join the fray. While listening to the coms channel I became witness of a change in plans. The Caldari weren't putting up much of a fight, but the notorious outlaws of Balkan Express were showing up in Enaluri with a fleet of Legions and Guardians. Our intelligence officers also reported that the BALEX Titan pilot was online, and so we expected a possible escalation. While I was in transit, a call went out for heavier ships.

Now, I am a low skillpoint character and flying HACs, T3s or even Battleships is beyond my reach for now, so I just kept on course while more powerful militia capsuleers prepared to commit everything up to capital ships. We went for the fight and jumped in a Thanatos and an Archon for support while trying to destroy the enemy logistics at the Enaluri - Hallanen gate. To our surprise, BALEX did not stay and fight, but rather chose to leave the field after the loss of only one Guardian logistics ship.

An unexpected turn of events

Considering what was to come, I have to wonder whether they knew something we did not. In any case, our cruiser fleet FC commanded us to follow the fleeing BALEX force into Hallanen. Our carriers prepared to extract themselves and we jumped through the gate. But then the unexpected happened: One of our carriers got pointed by another enemy ship that seemed to have come out of nowhere. The pilot of that ship lit a cynosural field and within seconds we had a very different fight on our hands: Snuffbox jumped in a fleet of carriers, dreadnoughts and battleships. Seeing no other choice if they wanted to get their carrier out, Sicarius Draconis, Blackfox Marauders and Monkeys with Guns counterdropped with militia capitals to fight Snuffbox.

Nobody wants to stand by on the other side of a gate while militia brothers and sisters are fighting and dying, so our FC ordered us to jump through and attack the battleships. Very soon it became clear that we could not break through the carrier reps that the enemy battleships received, but the onslaught from our own heavy weapons platforms did force Snuffbox carriers to enter triage and their dreads to go for siege mode. Since that made the enemy capital ships incapable of receiving repairs, our FC ordered us to primary them to support our own.

A third party and a fourth

It was a pretty even fight with our militia forces being at a slight advantage when Sniggwaffles warped in with a fleet of sniper Nagas. Quickly militia diplomatic operatives were scrambled to convince Sniggwaffles to shoot at Snuffbox rather than us. It worked only to some degree. Having no affiliation with either side, they spread fire among all targets of opportunity. With at least some firepower added to our cause, Snuffbox got put on the back foot and began to lose both carriers and dreads. They decided to escalate further in an effort to hold the field. Nyx supercapitals were dropped into the fight and now things began to look grim for us

The situation became even more dire when yet another group appeared on the battlefield: Pandemic Legion with their infamous supercapital force dropped in. They opened fire on both Gallente Militia and Snuffbox with an overwhelming force of approximately 30 Nyxes and Aeons supported by a contingent of Slowcats and their Sniggwaffles affiliates. The system hit heavy TiDi and PL prevailed. Nothing on the field could withstand such firepower.

Everyone who could, did their best to get out of there. I myself almost died to a smartbomb on my way through the gate to the adjacent system of Nennamaila. None of our capital ships made it out of there alive. When we collected our losses, we had fared better than Snuffbox, losing less capitals and other ships. Pandemic Legion - however - turned what could possibly have been a narrow victory for our side into a route of our forces.

In retrospect

While I have lived in nullsec for most of my EVE life and am no stranger to large fleet fights, this was definitely the largest one I have seen since I resubscribed and lived in lowsec. The development of the fight from the seed of a usual skirmish with Caldari Militia to a fight against outlaws and then into a capital brawl certainly was a special experience that is much different from the large nullsec fights which tend to occur around timers. I can only thank all involved parties for a great fight and I'm happy to now have one Vindicator and six capship killmails on my name ... I even got into the top 25 damage dealers for most of them with my little Vexor.

Good fights all around.

Edit: As of today, 2203, Enaluri is Gallente

TRS - A Newbie Guide to FC Commands

Like I said, I am currently engaged in Faction Warfare, and because of the relatively easy access to that playstyle really new pilots are regularly coming in. For them and newbies everywhere else I decided to write this short guide, so you don't have to ask embarrassing questions in the middle of a fleet op, or - even worse - get yourself killed or screw up a fleet operation because you did the wrong thing. In here, you'll find commonly used commands that are pretty universal all over the game. I will also explain for each command on how you properly follow it and which keyboard shortcuts you can use.

You can also use this as an aspiring fleet commander to know how to issue commands to people in a way that is generally understood in EVE.

EVE Uni also have a nice guide on the subject but it is in many ways rather specific to their way of doing things. I would still recommend reading it.

A few things in general:

Once you are on fleet coms during forming up the fleet, be sure to identify the voice of the FC. If you are not sure who it is, then ask. That is the person you keep listening to for instructions, and nobody else. Always pay attention to every word the FC says.

If the FC issues an order and you didn't understand it, ask the FC to repeat it, but don't start a long explanation like "Sorry, I'm new here so I didn't quite get that last thing you said. Could you be so kind to tell me again what I am supposed to do." just keep it short and clear like "FC repeat last order." or "FC repeat destination."

If you are just a normal fleet member with no special role, then you wont have to say much yourself during an operation, so don't. Often enough you will end up in fleets where lots of people seem to talk about random stuff. Don't let yourself get dragged into this. Those people are either experienced enough to judge the situation and know when it's OK to relax, or they are just idiots who mess up coms. If you belong to the intended audience for this post, then you are most likely not experienced enough yet, and you certainly don't want to be one of the idiots either. 

Ok, with that out of the way let's get to the things you will hear the FC say and what they mean:

Moving Around:  

• Warp (to) ... This command is followed by a destination. That can be a gate, a station, a planet or anything else in system. It means that you warp to zero distance. Click on the destination on your overview (BTW most of the actions that follow here require you to click on your destination on the overview, so I wont repeat that for each command) Now hit the "Warp to" button on your selected object panel (or S on your keyboard). Most importnatly, if your destination is a gate do not jump through.
• Jump on contact This is the exception to the last sentence above. If you hear an FC say that after issuing a warp to gate order, you are supposed to jump. You can warp and jump on contact by hitting the D button on your keyboard after you selected a gate.
• Jump You will hear this order if you have been sitting at a gate and are now supposed to jump through. Do it immediately. Again, you can hit D for that. Just make sure you have the gate selected if you do.
• Hold/Gate is Red This command is usually issued after you have already been ordered to jump but things have changed due to new information. So you do not jump through the next gate. If you are already in warp, you hit Ctrl+Space to cancel the jump command that would follow your warp. Also FCs often use this command to emphasize that people should not jump, even if they were not ordered to and should actually stop at the gate anyway. Once you are free to jump the FC will declare the gate Green.
• Warp at range/Warp to optimal Here the FC will give you a destination and either tell you to which range you should warp, or assume that you just warp to the range that is best for you. If you are in a frigate with guns that can fire up to 5km optimal range, then you warp to 5km. If you are in an electronic attack frigate like a Griffin that jams targets from 30km optimal, then use that range as your reference point.You do that by right clicking on the destination and selecting the proper distance to warp to.
• Align ... This will also be followed by a destination. Your selected object panel has a button for that too, and hitting A is the keyboard shortcut for it. Some FCs will use the term Soft Align. That means you align, and once your ship has turned into that direction, you stop it's engines to hold position.
• Set Destination This command will be accompanied by a link in fleet chat. If it is not, request it. You can click on that link and set destination. It is important that you use the same autopilot settings as everyone else. If in doubt, ask. "Prefer Shorter" is usually the default. The autopilot settings can be found by clicking on the A next to the route that usually appears at the left top of your screen as a series of blocks.
• Best Speed/Free Burn ... Again, this command will be followed by a solar system destination. Like above, someone will link that system in fleet chat so you can click on it and set the destination. You are then supposed to just warp to and jump through all the stargates on the way there without detours or delays.
• Anchor on ... This command will be followed by the name of a fleet member. You can either orbit that fleet member at reasonably close range, or use the "Keep at range" function. Don't get so close that you can bump off eachother. Something like 5-10km is usually fine.
• Tac/Ping on ... This is the FC asking for someone to either warp to a previously existing tactical bookmark or otherwise create one at a destination gate or station. A tactical bookmark is one that is far enough from a gate or a station to be at minimum warp distance (+150km). If you have such a bookmark or want to create one (best done in a fast ship) then you can respond by announcing that.
• Go plus one This one will come with a qualifier that tells you whether the command is meant for you or not. Something like "Scout go plus one" or "Fast Tackle go plus one" If the role description fits your ship and role, you jump through the next gate on the way to the destination solar system. When everyone else is ordered to just warp to a gate, it means you jump through it. If everyone is jumping through, it means you go to the next system on the path to the destination.
• Hold Cloak This will be issued after a jump order. It means that you jump through a gate and do not move. Do not click anywhere in space. Just do nothing and take a few deep breaths because usually that command is given when you jump into an enemy gatecamp and things are going to turn exciting very soon. Also take a second to sort your overview by name. You will see in the next section why.

 Fighting

• Primary is ... This command is followed by an enemy pilot's name. Hold Ctrl and click on the pilot's name on the overview to achieve a target lock, and then hit them with everything you have. If you are too far away from the primary, then fly closer until you can engage them. If you now have your overview sorted by name, then you will find your target much easier.
• Secondary is ... Again followed by an enemy pilot's name. You lock that pilot too, but you do not hit them yet. The exception is, if your position is such that you happen to be out of range with the primary, but right next to the secondary, and if the primary target is a ship that will go down really quickly anyway. If the primary is a battleship and you are a small gang, your DPS will definitely be needed. If the primary is a cruiser, shooting the secondary is acceptable. Some FCs will call tertiary targets ... the same applies to them.
• Spread Points ... If you have a warp disruptor or warp scrambler (and you probably should have in a PVP fleet), lock up the first hostile you see on your overview that is close enough to be affected and activate the module. A good way to select a target is to take someone whose name starts with the same letter as yours, or the next closest one. Once you have one pointed call "Point on [Pilot Name]. If someone already has called point on the one you were targeting, target and point someone else.
• Weapons free Just attack and shoot whatever you like that's in range. Usually, when you hear this, you can start feeling good about things. An FC will normally only issue this command when success is a certainty.
• Deaggress Means you stop shooting, locking, pointing, everything that you are doing to people from the hostile fleet. Also, if you have drones out, do not forget to recall them. Usually this command is issued with the intention to escape through a gate or dock at a station when your aggression timer has run out, so approach the closest gate or station until you are in jump- or dock range but do not stop moving. Best orbit the gate or orbit a fellow pilot close enough for jumping or docking.
• Overheat You need to have the Thermodynamics skill for that. In it's general form it means to overheat your weapons for maximum damage. Hold Shift and click on your weapon icon to do so. If you want to stop overheating, do the Shift+Click thing again. Sometimes you will be ordered to overheat your propulsion or something else. The Same Shift+Click action works for that too.
• [Role/Name] Down This is not something the FC tells you, but something you tell the FC. You inform the FC that the fleet has lost a ship with a special role if you get killed and you were assigned a special function that the fleet has in limited supply. If you fly in a fleet of thirty blaster fit Thoraxes, you don't call out "Thorax Down" when you get blown up, but if you were one of two jamming ships or a logistics cruiser that the fleet is depending on, it makes sense to announce your loss. If you are sure that the FC knows what you personally are flying, then you can also use your name.
• Scatter/Warp Out/Run When you hear that, it's all about saving yourself. The battle is lost and all you can do is to try and get out alive. Warp to the first faraway thing that you can find on your overview. Ideally a planet. If you can not warp, align your ship in the direction of an object away from the enemy and overheat your propulsion module if you can. You might be able to shake people tackling you or get out of a bubble and still make it, but be prepared to warp your pod instead.

Other stuff

• Clear Coms A family friendly way for an FC to say "Shut the fuck up you bunch of retards!"
• Break/Check Usually called by people other than the FC. Most of the time by a scout. This is meant to get everyone to stop talking and start listening because something important is going to come up. It could even be you who calls a Break because you might have noticed something nobody else did. Like for example if you are the last to jump through a gate and a whole fleet of hostiles landed behind you just before you jumped.
• Chill (or something to that effect) This is the FC telling you that you can drop your guard. Now you can talk about random stuff until you either hear a Break or a Clear Coms.
• X "tack" Y This is not so much a command but a jargon thing. You will hear that in nullsec space when an FC gives destination. Nullsec systems have alphanumeric names like F-YH5B. The hyphen in those names will generally be spoken as "tack" like eff-tack-why-age-five-bee in the given example.

This sums up all generally used FC commands that I can think of. Some corps and alliances might have special codes or commands that I did not list here, but the above should get you through almost any fleet operation without seeming completely clueless.


I wish you good luck out there, and good fights.