Category Archives: General stuff

A Bad Idea

So we’ve made some ISK lately. By “we” I mean “everyone else” and Wrathammer is in the mood to roam lowsec. Of course, we never do things properly. Wrath wants to welp a Carrier into something. The idea is actually to just hotdrop something for hilarity, but we all know how it’ll end.

So we fit up two HAM Prophecies with some limited RR and Firefly fields a Typhoon. We’re totally not bait. No sir-ee.

Off into lowsec we go, striking out from Amarr. We roam for about 30 jumps with not a soul in sight. We briefly run into a 40 man Naga gang with Scimitar support, but after a standoff over a stargate both sides disengage and continue on our way.

“This is going nowhere” says Wrath. I’m inclined to agree and we make a beeline for the nearest Faction Warfare space. As luck would have it, it’s Minmatar space.

We jump in and scare the crap out of some roaming frigate gangs but find nothing worth engaging/hotdropping. We start heading towards Amamake when Wrath decides to have us light a cyno since his Carrier is almost out of jump range. Normal procedure is to light a cyno on a station with a large docking radius. Not for us.

We cyno’d on the gate.

The Thanatos jumps in and cloaks up off gate. As we do so, a frigate jumps in the gate. He burns for gate as we open fire and decloaks the Thanatos. Whoops.

A 10-20 man cruiser fleet jumps in and engages. We engage back, killing 2 cruisers as their fleet disengages. I warp off to create a safespot when things get worse. The cruiser fleet re-engages as I’m in warp elsewhere. Whilst the fight re-engages, Shadow Cartel jump in with a T3+Guardian fleet. Oh dear. They also have a host of neuting Legions. Oh dear.

Firefly almost insta-pops as I land on grid. I choose a nearby Thorax to engage as our Carrier slowly dies to the neuts. Then the jams land on me.

My HUD glitched out - I was taking full damage but none of it displayed

This is the definition of “oh shit”

I was under the full impression I was not being shot. Turns out my HUD was just bugged and I exploded without warning. Mick dies too, followed swiftly by our Carrier. Oh well.

Battle Report. Nothing fancy. No great victory, just an empty roam followed by a massive blob. I may avoid doing that again!


Battle over Caldari Prime


Last night saw one of the biggest EVE Live Events in history. I was actually at work and missed most of the event, but I’ve collected as much information as I could find.

For a bit of backstory – according to the EVE lore, the Gallente and Caldari both started in the same home system of Luminaire. Some time before Capsuleers came into play, the Caldari were pushed out of Luminaire in a brutal war with the Gallente. Flash forward to 2008 and the Empyrean Age expansion – The Caldari launch a massive assault on Luminaire (whilst CONCORD were being killed in Yulai). This resulted in a Caldari NPC Leviathan-class Titan above Caldari Prime for the next few years. Millions of Gallente citizens were trapped on the surface of the planet. You can actually get a detailed account of these events in the Empyrean Age book.

Anyway. With the rise of the immortal ground troops (AKA Dust 514) the Gallente forces still on the surface have begun fighting back. In order to quell the fighting, the Titan “Shiigeru” has moved into low orbit over Caldari Prime to provide orbital support. Tensions between Caldari and Gallente, already high, came to a crux in orbit last night.

Caldari Prime, 24 hours before the battle

Caldari Prime, 24 hours before the battle

CONCORD released warnings over entering Luminaire as the ground situation erupted into full-scale hostilies (as the DUST forces battled for both sides). The NPC Titan in Luminaire was replaced by a CCP Actor over Downtime and moved into the low-orbit position. 4 Wyvern-class Supercarriers of the Caldari State also moved into defensive positions around the Titan. Multiple Carriers and Dreadnaughts also reinforced the fleet.


As Luminaire was still a High Security system (1.0), the Capsuleers in orbit could merely swarm round the field as the ships moved closer to the surface. CCP had announced the event start time at 1700, but the system was already capped at one thousand people by 1400. At about 1545, a CONCORD vessel approached the planet surface in an attempt to survey the scale of the ground offensive.

The Caldari Navy blew it up.

At 16:45, the Gallente navy (all piloted by NPC actors) launched a full-scaled capital offensive against the Caldari forces. A massive fleet of Carriers, Dreadnaughts and a handful of Nyx Supercarriers began the attack.

At 1700, CONCORD declared Luminaire a warzone and made every player ship in Luminaire Suspect. Meaning anyone could shoot anyone. In High-Security Space. What followed was a massive battle lasting hours.

Time Dilation hit 10% almost instantly. The system cap was raised to almost 1800 players, but the slowdown wasinsane. Hundreds of players, unable to get in, sat on the entry stargates – killing every suspect ship who tried to escape the system. Algogille, next door to Luminaire, hit 1000 people alone – nearly all of which on the stargate. Over 700 ships were destroyed even there.

Meanwhile, in Luminaire, the battle was fiercely underway. These images are courtesy of other players.


As the Federation Navy ships engage the Caldari State, Capsuleers of neither faction engage anyone they see fit

A Federation Navy Moros fires a barrage at a Caldari Navy Chimera

A Federation Navy Moros fires a barrage at a Caldari Navy Chimera

The wreck of a Wyvern sites near the besieged Shiigeru

The wreck of a Wyvern sits near the besieged Shiigeru

As the battle raged for an hour, organised Capsuleer forces entered the system. Alliances such as Goonswarm and TEST made their presence known with organised fleets of Maelstroms and Rokhs, but this was nothing compared to the general carnage of the battlefield. At 1800, the Shiigeru was destroyed. The battle continued to rage for a further hour. The Caldari Navy fleet was almost completely annihalated, with the Federation Navy fleet taking heavy losses in return.

It was at this point I managed to enter the field. I found carnage.

Caldari Prime at 1855

Caldari Prime at 1855

My Taranis was no match for the larger ships on grid, so I tried to steer my ship through the lag and slowdown and pick off some easier enemies.





Sadly, overheating was rather non-responsive

At about 2000 it was all over, unless you were fighting on the planet directly. The Titan had broken up in orbit, and a large section had decided to impact one of the battlefields.


All in all, the event was fun as hell for myself. I can’t comment on the main section (the Titan) because I missed the lot of it. Most of the Capitals destroyed (including the Titan) did not provide a killmail, but here’s the Battle Report of some of the kills.

Rolling a wormhole creates a capital engagement

There’s activity on scan as I log in. I’m alone in the alliance channel, yet an Ares and combat probes light my directional scan. Interesting.  There’s an inbound C5 a few hours old, so I kick the warp drive into gear and head over to check it out. I’m met with a fight.


Two other alliances are currently engaged in combat. In my home! The cheeky gits. It looks like Sleeper Social Club are engaging another force of ships belonging to The Laughing Men. Unable to intervene in any meaningful way, I sit and watch for a few minutes. I do not know the source of either fleet, but my playtime is limited and I am content to watch them fight. I see just one ship (of Laughing Men) die during my time here before a larger SSC force jumps through and they all warp off. A few SSC ships return to loot the wrecks and drones before departing, leaving my home as quiet as before.  I choose this moment to safe up and log out.


Some hours later, Silent Terror and Firefly log in. Upon seeing the inbound, they decide to be done with it. I’m told Firefly asked “ST, help me roll this wormhole”.

A quick scout revealed nothing unusual, and they began the rolling process, dropping a Thanatos to close the wormhole for good, leading to a nice quiet system.

Or so we thought.

As our Thanatos jumped home, a new contact appeared on d-scan. A Vigilant had just landed on grid with our Carrier. ST promptly found himself pointed. As it turns out, we had missed an inbound. This mistake could cost us dearly.

As ST begins maneuvering and applying ECM drones, multiple hostile ships land on grid. It’s The Laughing Men, and they fully intend to do away with their prey. A trio of Guardians with various Tech 3 and Recon support lands and completes the ambush. The battle is on.

Not content to watch his friend die, Firefly commits a Loki and a Tengu into the fight, using the Carrier’s remote repairs to try to pressure the opposition away from the Carrier. Meanwhile, ST is busy gathering our forces. I get a message. It has two words. “PvP. Now”

Dropping the PS3 controller (Battlefield 3, yo) I log in alongside Mick, Splut, Lykwidian and Barrak. Our initial plan involves ECM. Lots of ECM. We’re going to jam out the hostile tackle and extract the carrier – we have no eyes or scan of the enemy wormhole and their fleet is increasing by a ship a minute, so we’d like to avoid losing it. We launch 4 Falcons into warp and await a good opportunity to strike. Unfortunately, a Mistake Was Made and 2 of the Falcons miswarped, decloaking early. One Falcon goes down whilst the others bail off field. Plan A is marked as a failure.

Fortunately, we have a plan B – we commit a second Thanatos onto the field and hit them with armour dps, using a Scorpion as an ECM platform to try and break the Guardian chain. Lacking my Absolution (I lost another one) I grab an old Myrmidon for myself. We gear up and send in the second Thanatos first, with our fleet not far behind.

Landing onto the battlefield

I am aware my overview is a clusterfuck. I like it like that.

First up? The Curse. We landed about 14km away and promptly blow it up before his repairs land. The pod escapes, likely to reship, and we choose a Guardian as the next primary. Our own Scorpion is primaried and explodes before we can repair it. The Guardian dips into low armour before repairs catch on. Dammit. Our two Carriers are keeping ourselves up nicely now, but the enemy have made no move to disengage. They must have an ace up their sleeve. Disregarding the first Guardian, we swap targets to the Oneiros only to get it to 75% structure before the reps land. Moving quick, we swap all DPS to the original Guardian. The swap catches them off guard (hah) and the first Guardian explodes. We burn down the second Guardian and take it down too. The third Guardian warps off as the Oneiros meets his end.

We begin chewing into a Legion as a Bhaalgorn lands and starts neuting out one of our carriers. Firefly gets a point as we continue on the Legion, finally finishing it off. The Vigilant follows,

A silence falls over Mumble as we move towards the next target. A new hostile has landed. “Dreadnaught on grid”. A Phoenix has just landed and began his Siege cycle. This is their ace.

As we start plinking at the Tempest Fleet Issue, a lone Guardian also lands on grid. D-Scan reveals three more. We burn our guns to finish the Tempest and the Loki as the Guardians land. 2 of them burn to range but 2 remain close and we pull the same trick as before, alternating targets to catch one out. We succeed in killing the first. As we start on the second new Guardian, the other remaining two warp, as does the Bhaalgorn – some ECM drones successfully allowing it to evade.

Yes, the drone flight is sub-optimal. In my defence, I grabbed this in a hurry.

Yes, the drone flight is sub-optimal. In my defence, I grabbed this in a hurry.

The last Guardian dies and we start clearing up the remaining subcaps. Our first Thanatos is now dipping into structure, but the remaining enemy subcaps no longer have it pointed, so it simply warps away. Op success?

Only a few enemy ships remain and the Phoenix is firmly in Siege, so we eliminate the remaining Proteus and Onyx. Our remaining Carrier is starting to buckle and the tank is failing, so we warp it out too.

Finally, only the Phoenix remains. He exits Siege and tries to warp but is pointed, so he re-sieges. Confident he is not going anywhere, we warp a few people out to prepare some new ships. I grab my Proteus and start scanning for that possible inbound as we ready *our* ace in the hole. Our ace is 4 of our own Dreadnaughts.


Image courtesy of our Rev pilot

Image courtesy of our Rev pilot

The last of the hostile ships explodes, taking his pod with it. We offer “gf”‘s to any of them still in local and proceed to clean up the field.

The EVE-Kill Battle Report is here but does not include our original Falcons, nor 2 of the hostile Guardians we killed (because they were the same pilots). You can check our alliance kills and losses for a better picture.

All in all, a really fun fight. I’ve never been prouder of our alliance. I honestly thought we were going to end the night down a Carrier. Props to The Laughing Men as well for having the balls to commit such a fleet into an enemy-controlled system.

RvB vs E-Uni – University POS goes down

There’s a bit of a lull in w-space today, but I’ve found something to entertain me.

Red Federation and Blue Republic have declared a joint war on EVE University. The 3 biggest corps in High-Security space are now in all out war. I should indicate that since I have many friends in RvB who pass me intel and killmails, most of this reporting will be from he RvB viewpoint. Not a lot I can do about that! If any Uni pilots want me to add their Point of View or screenshots, let me know!

The reason for the war? As far as I know, RvB did it for the explosions. That’s literally it. The war was declared on Valentine’s Day and came into effect on Friday afternoon.

Day 1

RvB had started the war by moving vast quantities of ships into the Uni HQ system of Aldrat. Several thousand have been moved up for RvB contracts and reimbursement. Thus as soon as the war went live on Friday RvB were already in a rather large Purple horde – some 100 pilots in fleet. Small skirmishes occurred throughout the late afternoon, but both sides were yet to wake up as it quickly entered EVE primetime.

RvB then took it upon themselves to engage the Uni’s POS tower in Aldrat. This tower has some infamy inside RvB – twice they had attacked it in previous wars, only to be beaten back at the last moment. EVE Uni had already removed the valuable items and placed it into full defence mode – lots of hardeners with a good mix of ECM and defensive guns. So RvB dropped a 130 man fleet on it. Uni responded in kind by meeting RvB head-on with a large fleet of their own. This initial clash resulted in the predicted explosion of over 100 vessels with the field going to RvB by the time the smoke cleared. No direct killboard link due to battle reports being warped by the nature of the fights.


The siege in progress

Not to be defeated so easily, Uni decided hit and run tactics would work better and launched raid after raid, primarily with Destroyer fleets, inflicting multiple casualties on RvB in the process. Tier 3 gangs also managed several kills before being driven away. Uni then quietened down for an hour before launching a second large assault. Despite putting up a good fight, the RvB forces were too well entrenched and Uni found themselves driven away.  Not too long after, the inevitable happened.

POS goes into Reinforced

POS goes into Reinforced

The EVE-Uni POS hit 25% shields and entered reinforce mode. It’d exit in 22 hours – right in Saturday Night primetime. This seemed to spur the Uni fleet into action as their largest fleet yet – multiple Battleships, Battlecruisers, 4-5 Basilisks and a swarm of Ospreys as Logistics support – and launched it into the RvB fleet in a fight above Planet 1.

Uni engage RvB over Aldrat I

Uni engage RvB over Aldrat I

Yes, I was in the RvB fleet. How else would I know where to go for screenshots? There is no battle report again, because the BR’s merely show the whole night. However, this RvB loss and this Uni loss give good indicators of fleets involved.

RvB managed to hold the field against E-Uni and that saw the end of the major action in the EU timezone for the day. Smaller skirmishes occured throughout the night, but nothing on the scale of the last fight. There was a 30-minute brawl of constant reships on the Uni’s station too

HERE is the overall kill report of the first day. Professor Clio of RvB did a writeup of day 1 here too.

Day 2

The Uni POS comes out of reinforcement shortly and RvB are gathering a fleet rarely seen in highsec. 240 people are in the fleet 20 minutes before the reinforcement timer ends – over 60 of them Battleships. As the RvB fleet grows in number, so too does the Uni fleet. Most of them appear docked, but a good 100+ are sat in their POS waiting. Local is over 750 – unheard of outside the market hubs. Tension is rising across Aldrat.

15 minutes.

The RvB fleet is full at 255 members. An overflow fleet is created and it’s this one I find myself listening to comms with, awaiting the perfect moment to try actually figure out who will win. As the timer ticks down, more Uni pilots warp into their POS.

5 minutes.

The RvB fleet warps to the edge of the POS shields. Any outlying Uni ships are quick to retreat as even more arrive from their Station. 250 pilots on each side stare each other down (the RvB Overflow fleet was elsewhere)


The POS becomes vulnerable as RvB opens fire onto the shields.

Faceoff in Aldrat

Faceoff in Aldrat

The seconds tick by. The neutrals on site hold their breath, waiting for Uni to make their move.

They do.

The Uni fleet mass warps to the Sun – behind the RvB fleet. They’re going to drop in behind them – a simple, yet effective, tactic – it allows the Uni fleet to position their Logistics ships away from the dangerous RvB Battlecruisers.

The Uni fleet land and all hell breaks loose.

The fleets engage

The fleets engage

The Uni Logistics, landing some 30km behind their main fleet, are quickly landed on by the RvB Overflow fleet and are quickly taken out the fight. Tidi kicks in as over 500 pilots enter one of, if not the biggest, fight in High Security space in EVE’s history.

Blue are RvB. Orange are Uni. Most are drones anyway

Blue are RvB. Orange are Uni. Most are drones anyway

The RvB Logistics team kicks into high gear

The RvB Logistics team kicks into high gear

The fight rages for almost 20 minutes as Tidi swings as low as 25% in places. Finally, the remaining Uni ships disengage and retreat into warp or into the POS shields. The result?

E-Uni got hammered. RVB suffered very few losses and the Uni Logistics ships were decimated early on in the brawl. TEST alliance then dropped 6-7 smartbombing battleships onto the RvB fleet but were promptly CONCORDOKKENED


Once again, Professor Clio of RvB did a writeup on Day 2 here. There’s an E-Uni Logi Member’s thoughts here too!

The final result of Day 2?


Will the war continue? Possibly. I’m looking forward to seeing the next fight.

As usual, if you want me to add anything (or correct a mistake) let me know in a comment or in-game at tgl3.

The skill changes – answers to common questions

There’s a new devblog. It covers somewhat large changes to the skill requirements to many ships. Read it here. Done that? Go do it. Done now? Great. I bet you have questions. Lots of Bads in the forum thread do, and it’s nearly always the same question. There’s some other queries too, so here’s some answers to the common ones.

To clarify, there are two major changes. Those to Destroyers and Battlecruiser skills, and those to general ship requirements.

What are CCP doing?

They are adjusting the requirements for most ship hulls.  Why? Several reasons. The main reason is to allow the ship requirements to actually match the ship. For example – Logistics V and Cruiser V to fly the T2 Battlecruisers? Silly. So CCP are throwing that out and replacing it with needing Leadership skills. For the Command ships. Make sense? The in-depth reason is nice and clear in the actual blog. So go read the blog already.

I don’t have <x> skill for <y> ship, but I can fly <y> now! Can I fly <y> after the change?


Seriously, yes. Let me say this again. Yes. Let me show you an example.

Let us say I have Command Ships to Level 3. CCP are changing the requirements to need Skirmish Warfare 5, which I do not have. OH MY GOD CCP I CANT FLY MY SHIP WTFFFFF GIEV ME SP REFUNDZ.


I already have Command Ships 3. This means I can still fly them, even if I do not meet the requirements for Command Ships after the patch. THIS APPLIES TO ALL THE CHANGES. The skills being changed actually affect the injection of the skillbook, not your ability to fly the ship. One important thing to note it that, without the new requirements I cannot train Command Ships any higher. CCP have said that this last fact is still up for change hereCCP have just announced that even if you no longer meet the new prerequisites, you can still train the skill higher!

What are the Battlecruiser and Destroyer skill splits?

The Destroyer and Battlecruiser skills are being split into their 4 racial variants.  Destroyers becomes Gallente Destroyers, Amarr Destroyers and so on. Same thing with Battlecruisers. With me so far? Good. Now onto how you get the new splits.

If you have Destroyer or Battlecruiser to any level, then you will receive the relevant racial skills to the same level providing you meet certain criteria.

  • For Destroyer racial skills, you need to have the racial Frigate to at least Level 3
    • If I have Destroyers 4 with Caldari Frigate 3, I get Caldari Destroyer to 4
    • If I have Destroyers 5 with Caldari Frigate 1, I do not get Caldari Destroyers
    • If I have Destroyers 1 with Caldari Frigate 5, I get Caldari Destroyer to 1
  • For Battlecruiser racial skills, you need to have the racial Cruiser to at least Level 3
    • If I have Battlecruiser 5 with Amarr Cruiser 3, I get Amarr Battlecruiser 5
    • If I have Battlecruiser 5 with Amarr Cruiser 2, I do not get Amarr Battlecruiser
    • If I have Battlecruiser 2 with Amarr Cruiser 5, I get Amarr Battlecruiser 2

NOTE: If you are granted any of the new racial skills, you will get MORE SP due to the skills giving you the extra SP. The maximum is 6.2 Million SP with Battlecruiser 5 and Destroyer 5, so you need to upgrade your clones!

Can I get a skillpoint refund because I trained <x> when <y> no longer needs <x>?

No. Get out. Noone gets refunds for balancing or other changes (with the exception of Learning Skills a while back)

The Iteron Mk V no longer needs Industrial V!

Correct. CCP are going to adjust all the industrials as part of Tiericide. Details are not known yet.

Why do I need to train <x> for ship <y> now?

Likely due to the skill being more relevant for the ship class than whatever it needed before.

When do these changes hit?

These will arrive with the Summer Expansion (May/June/July) so you have plenty of time to adjust skillplans. I recommend training Battlecruiser V, Destroyer V and the racial frigates and cruisers to 3 NOW to get the maximum refund on these skills.

If you have any more questions, feel free to ask me in a comment or convo me in-game. If you spot a mistake, please notify me. If you’re mad, be less bad.