Wormhole Treasures

The Captains Log 15/7

Solarsystem: Unknown

Shiptype: Armageddon Class Battleship

In wormholes there are plenty of treasures to be found; such as POS’s that are about to come out of reinforced. Now you may ask how is this a treasure? Well its quite simple. If a POS is in reinforced it means that someone has put it into reinforced and therefore someone has to come back and finish destroying it; which means we can get ourselves a fight.

Read More

Oh no you Didn’t

The Captains Log 2/7

Solarsystem: Unknown

So I was catching up on blog posts (I haven’t read or written a blog post for about three weeks due to uni exams etc) when I came across a post written by Wench with a Wrench. Essentially her corporation, Adhocracy, had decided it was great idea to take down another corporation WH POS. The defending corporation then decided to hire Noir to A) save their POS and B) remove the enemy POS from the WH.

Read More

Welcome to the Noir. State

Welcome to the Noir. State

Providence Murder Train

The Captains Log 9/4

Region: Providence

Shiptype: Manticore Class Stealth Bomber

The war, or should I say murder train, continues in Providence. So far Noir. has been keeping our little pocket of Providence thoroughly pacified and there has been a rather large lack of resistance (there has been some but only limited).

Read More

Resistance is Futile

The Captains Log 6/4

Region: Providence

Shiptype: Cerabus Class Heavy Assult Ship

So our operation went off without a hitch last night, the goal was to deploy Sovereignty Blockade Units throughout a constellation in Providence, which is part of a larger initiative tacking place across the whole of Providence to remove CVA from providence completely.

Read More

Tower Defence

The Captains Log 29/3  

Solar System:  Uedama  

Shiptype: Apocalypse Class Battleship   

Since I have joined Noir. I have to clean my up my act a little bit. No more can flipping, no more suicide ganking, no more smack talking, no more  neutral remote repping and most galling of all I have to defend POS’s, not blow them up, and that was what we did last Saturday; defend someone’s research POS.  

The op started with us all gathering on a gate with our RR battleships and support fleet, only for one our Falcons to get suicided ganked by a Tempest. 

Read More

A tale of two battles

The Captains Log 27/12

Solar System: A1-AUH; Esoteria. Amarr; Domain

Shiptype: Drake Class Battlecruiser, Prophecy Class Battlecruiser, Harbinger Class Battlecruiser

GoonSwarm in all their might and glory came to our space in a Drake and support gang.  While the battle raged there another fight was brewing in Amarr in agains Privateer Allaince. Who was to win these battles. Read and find out.

Read More

Invading Goons

The Captains Log 25/11

System: TPAR-G; Peroid Basis

Ship: Rokh Class Battleship

For those of you who have being regularly following my blog you will know that GoonSwarm tried to invade Esoteria not to long agao, which failed miserably.  Well over the last week or so the StainWagon Coalition has returned the favour and launched a invasion TPAR-G, a GoonSwarm held system in Period Basis.

Read More

Esoteria War Update

The Captains Log 26/10

The last week has seen the steady grind of POS warfare on both sides of the fight. Goonswarm would put our POS’s into reinforced, we would then rep them and then put some Goon POS’s into reinforced only for Goons to rep them. So far this has only taken place in two systems, A1-AUH the chokepoint for Esoteria as it divides the region into four parts (North, East, West and South) and G-YZUX, which is one of the station systems allowing for SOV 4 to exist. There is little actual fighting going on between us due the time zone differences between the alliance (Goons US and Sys-k Euro), despite this there have being a few battles when the play time of both the alliances overlap, with Goonswarm putting Stealth Bomber fleets to good use when attack the Sys-k battleship fleets.

The start of the war also saw the start of a new propaganda war with the Mittani releasing chat logs of a Simmering Rebellion taking place in Systematic-Chaos, in which the CEO and a Director of I.M.M and a i.NET director were talking with Zapawork about siding with Goonswarm in the coming war. Liam Freeman (the Sys-k leader) passed this off as a joke of which he was fully aware of. The fact that these chat logs have being released to me indicates that any deal that may have been made has fallen through otherwise the Goons would not be releasing this information and giving away their hand. Furthermore, as a member if I.M.M I can say that there is a lot of anti-goon feelings in the rank and file and that any pro-Goon decision made by the leadership would not sit well with them and probably lead to a insurrection in the corp ranks.

The biggest battle to take place so far occurred on the weekend when 16 Goonswarm POS where coming out of reinforced, which lead to a 500+ strong allied fleet turning up for the fight giving them the numerical advantage. The battle resulted in a large number of Goonswarm capitals being destroyed along with the majority of the POS’s that were coming out of reinforced. Goons claim the capitals lost were a suicide fleet as their insurance was about to expire.

While this loss may have not bothered the Goons much the loss of their Titan in a separate battle with Red Overlord probably did. Apparently a Goon mining POS placed in ROL space came under attack so Goons jumped in a Titan without support which was promptly tackled and engaged. So Goons launched a rescue mission with another Titan, which successfully allowed the original Titan to escape only for the second one to be caught and destroyed.

So the big question is why is Goonswarm invading Systematic-Chaos space? Well the first and the simplest answer is to give their members something to do. As a PvP alliance they have to keep their members active otherwise they may just disappear forever. However, the possible strategic reasons for the invasion offers further insights, which can be seen in the Goon post here. Basically the objective of this war is not about territorial conquest but to induce a failure cascade in Sys-k as they are the alliance the fields a lot the sub-capital support in the Stainwagon coalition. Be removing Sys-k from the equation the Stainwagon coalition will have a large cap fleet but limited sub-capital support, thus removing the whole coalitions as threat for awhile. Furthermore there had being rumours going through the alliance that Sys-k would soon be invading the space formally occupied by KIA and now Zenith Affinity. Invading Esoteria therefore is a pro-active from of defence.

So how long is this war going to go for? Well providing that Sys-k doesn’t failcascade I don’t foresee this war going on past Dominion (depending on how Sov is going to work) as with the release of the new Sov system all the major alliances are going to have to pull back and consolidate what they currently hold. Also from what CCP has released so far it does not seem that interregional wars are going to be the norm now, instead there is going to be more intraregional wars. Even if Goons mange to obtain the space occupied by Sys-k they will most likely not be able to hold it very easily post Dominion (again depending on how Sov works) thereby allowing Sys-k, or whatever it is afterwards, to reclaim it. So all Sys-k has to do win is hold the fort for one month. If we can do that we have won the war.

Part 2 – Capital Destruction and Titan Take Down

The Capatins Log 24/8

Capital Destruction

So after I logged off the day began to go badly for Sys-k. Goonswarm got a couple of cyno alts into J-A and proceeded hotdropped 40 capital ships on top of our fleet. Reading COAD (horrible I know) it seems that Goonswarm and Brick are not allied (or they weren’t at the time of the hotdrop); instead Goons saw an opportunity to take out our caps and took it. The result was around a 20 capital ship loss for Sys-k. There is a Frap available here to watch (if it does not work it is at the bottom of page 5 on the COAD link above). You would think that our members would be disheartened from such a heavy loss, but we weren’t and we came back the next day and repaid this loss many times over.

Titan take down

About 12 hours latter (or there about) we began setting up in 6QBH for another op into enemy space to help a friendly POS, when it was noticed that two Burn Eden titan pilots logged on. For all we knew they could have logged on to do some ratting, but they didn’t, instead they cynoed into 6QBH and proceeded to double doomday our fleet. In amongst this field of destructive energy my CEO, Hawkeye (his alt anyway) flying his Onyx not only survived both doomsdays but also got a tackle on one of the titans piloted by Syrian. He then had to survive and hold the tackle for one minute before the rest of our fleet was able to get to the battlefield and beging taking the titan down.

Burn Eden Titan is tackled

In an effort to save their allies titan, Brick Squad also cynoed in their capital fleet only to have it tackled. The result was the destruction of Burn Eden’s Titan and the Brick Capital fleet. The second Titan managed to escape. The final battle report is (thanks to Manasi)

Brick/BE:  lost 1 Titan, 11 Dreads, 10 Carriers, 4 BS, 2 recons, 2 interceptors, 1 dictor, and a few others…( total of 43)

The combined allied fleet lost:

4 dreads, 2 BS,1 BC, 1 Stealth bomber, 1 Heavy Assault, 1 Dictor ( a total of 14)

As with any great battle there is much discussion on the forums so go to COAD and Manasi’s blog for other perspectives. Also there is a YouTube video of the take down as well.

Now that I have recounted what happened I have to say I MISSED IT. I got up one hour too late to find out we had killed a titan without me being there. I am very unhappy.