Or the story of how we fought 2 Archons , 3 Moros’s, 2 Rapiers, 2 Loki’s for nearly 2 hours.


Most of EvE players that reside in wormholes abide by the rule of “Real Life First”. Sometimes it easy to live up to this and sometimes it is not. This is because wormholes differ from K-space. There is no instant fun to be had. One cannot choose to do a L4 mission (if that is your cup of tea) or hop into a solo Talos to go hunting. Everything needs preparation – to go hunting you have to meticulously scan and scout your system, the adjacent system and the system after that. This is what we call “The Chain”. In addition, the lack of immediate local chat means that you have to rely solely on scouting with Dscan and probes to find anything to shoot at. If you choose to use probes, you’ll probably just scare the prey unless you know how to “one-shot” scan them to 100%. To the accustomed wormhole resident, unknown probes lingering on Directional scan (Dscan) is as subtle as Santa Claus buffalo hunting on the prairie with jingle bells strapped around his neck. Good luck finding stuff to kill with that approach.

The fail

On the 15th of July early EU time zone, we had just started scanning the chain and we noticed that the C6 adjacent to us (=C6s) had two inactive players at a POS belonging to Jedi Knights Orden , formerly of the BLOOD UNION alliance – a formidable WH alliance. We observed these players at the POS for 15-20 minutes and concluded that they were AFK. We then proceeded to scan the system down, knowing full well that by doing that we would be revealing our presence, although with the new Discovery scanner, they probably had seen the new signature pop-up anyway. The chain was quickly scanned, and it contained one Low-sec entrance, one High-sec entrance and the rest were EOL wormholes that led to dead-end null security systems with little activity in them or around them.

The scouts started to head back towards home and when one of the scouts jumped back to the Jedi’s C6 system we saw a flurry of activity at their POS. Several subcaps had logged in whilst we were down the chain and the heavy recon scout placed eyes on them. The POS had Rapiers, Lokis, Damnation and assorted smaller stuff piloted.
After observing the Jedi’s POS for a short while an Archon, Naglfar , Moros and two Orcas were seen logging in to the POS. Boredom turned to excitement in mere seconds. So many questions arose: “Did they miss us coming in?”, “Are they going to run sites?”, “What are they doing?” .These question would be answered momentarily, because as quickly as they had landed to the POS, the Orca, Carrier and Moros had started to align and then warped away. Precious seconds ticked by while we were trying to assemble a fleet in our home system and the heavy recon scout tried to pinpoint where they had warped. After a moment of hesitation and confusion it became apparent that they had just collapsed the way to our home system.
What a failure. They had not missed us coming in; they were definitely not going to run sites but instead they were collapsing us out and succeeded in doing so unobstructed. The disheartened scouts exited the system through the HS we had found earlier and started to head back to a trade hub to await an entry back home.

Spider sense

Whilst the new chain was being scanned out someone asked on teamspeak a simple question: “What are the Jedi’s doing now?”. The heavy recon scout, now 6 jumps out, answered that he doesn’t know. No one thought much about it. What happened next was due to a mixture of spider sense and good luck. Without further comments the scout decided to turn back and return to that wormhole to take a peek inside.

What he found when he jumped back into the Jedi’s home system took everyone by surprise. There were tens of new ships on Dscan and most of the ships seen in the POS not 20 minutes ago were at a new signature. This new signature had to be a new wormhole and the residents were duking it out there with an unknown entity according to the Dscan data. Using the confusion of the fighting to his advantage the scout drops combat probes outside of Dscan range and tried to one-shot scan the capitals estimating the range and direction with the new scanner interface. Result : 98,8 % hit – so close but so far. The scout has to perform an extra cycle of scanning with the probes. That means 5 seconds of more time for them to notice that we are scanning them. We had to know who they were fighting and where. The second cycle lands us a 100% result, probes withdrawn, and the heavy recon initiates warp to see what is going on.
Meanwhile in our home system, the sudden burst of activity has raised interests and more scouts are seeded into the system in addition to the heavy recon already in place. A fleet is organized in hopes of maybe getting to participate in a three-way fight or just maybe gank something.
Once the heavy recon lands at a distance it can clear see that the fight is already over. The defending force of the Jedi’s has forced an unknown entity back into their wormhole. Now sometimes, the tiniest things can have huge implications and end up affecting the whole end result in a huge way. In this case the tiny things that I am referring to , were four Hammerhead drones that had been left behind on top of the wormhole. You may ask:” Why is this important?”. In wormholes everyone knows everyone and one day you can be shooting certain guys, the next day you can be fleeted with the same guys to kill other guys. Confusing right?

These four drones revealed to us who the Jedi’s were fighting against. It was ASH alliance. Communication was established with them quickly and a plan was hatched. ASH alliance would try to lure the Jedi’s into re-engaging at the wormhole by amassing a fleet of theirs at the wormhole. We would simultaneously go through another route and when the already mass reduced wormhole crashes with the weight of ASH alliance ships, we pounce on the capitals from the other direction.
Very quickly events started to unfold in a cascade that was hard to control anymore. A scout at the Jedi POS informed that an Archon was gaining speed and quickly after that she reported that it had initiated warp.

It’s a tarp

And so the trap sprung. The heavy recon at the [ASH] wormhole reported: “Archon on close range Dscan” and then in rapid succession that : “Archon landed at 0km from the hole” . This information was in turn relayed to [ASH] alliance. The scout at the Jedi POS notified that a hostile Scorpion was also aligning and gaining speed. Rapidly after it had initiated warp it was seen on close range Dscan from the [ASH] wormhole and immediately after the Scorpion landed the ominous hum of wormhole activation was heard. Heart rate spiked as simultaneously the wormhole went “mass critical” from just the scorpion jumping. The agitated voice of the heavy recon was heard on comms “Scorpion jumped, its crit, ITS CRIT, ASH needs to jump now”.

With luck three Guardians and a solitary Phobos manage to jump through before the wormhole collapses. The bubble of the Phobos goes up with an Archon and a Scorpion inside it, and the game begins. At the same time our reinforcement fleet jumped from the backdoor entry into the system and initiated warp to the now tackled Archon and Scorpion – completing a classic “hammer – anvil” maneuver.

The fight

Wormhole fights are sometimes over in mere minutes and more often than that they are quick skirmishes leading to few losses before the perceived losing side disengages to their hole. Then there are the drawn out fights that we found ourselves in on the 15th of July, the kind of fights that result from tireless scouting, solid tactics and a healthy dose of blind luck. The C6 wormhole we were fighting in was a Wolf-Rayet star giving +50% to all armor resistances to all ships. These inherent system bonuses coupled with an off-grid booster in the Jedi POS, meant that we were facing capital ships with immensely boosted tanks.

Now, truth be told, I do not know if the Jedi’s knew what they were heading into but neither did we. What I do know, is that they chose to stand their ground and we chose to see this fight through. Within minutes of the trap being sprung, the Jedi’s had on field in addition to the Archon, two Rapiers, two lokis and two Moroses with the third Moros landing at its optimal 20km out of the fighting soon after. Initially we had about 12 ships on grid, a standard T3 armor comp, complemented with Neut-Legions.

We tried to overpower the dreadnoughts, to no avail. We tried neuting the hostile capital ships and then breaking them only to be frustrated when they coasted out of siege/triage in time to get remote repairs and capacitor. To make the situation worse , even with a -50% signature boost given by the environment of the C6 Wolf-Rayet system, we were losing ships at a steady pace to the combined webbing and target painting of the Rapiers and Lokis. We brought ECMgus to counter them but even one missed jam cycle on those ships, meant hard work for the Guardian pilots and a possible 1 bill loss. The hostile Dreadnought pilots coordinated excellently with the Rapiers and Lokis and by combining a poor choice of orbit direction, a judgment from Bob, massive webbing and angry Moros pilots, we sustained roughly a T3/Guardian loss for every 10 minutes of fighting. One single unfortunate (probably multiboxing) guardian pilot managed even to get one-shotted by a Moros without any webs or target painters. I picture the Moros pilots going on comms: “BOOM! Headshot”, (in Russian of course).
The fight had been going on for 30 minutes and we were the ones losing expensive T3 cruisers. By now it was clear that we could not break the tank of these capital ships because of massive boosts the system provided, the fact that three of the capitals were in refit range, and last but not least , we were facing skilled capital pilots.


As the fighting raged on, reinforcements were heading in. Our job was to keep these pilots occupied and pointed until the fleet reached critical mass. Scouts and heavy recons were seeded into the entrance chains to provide warpins for the reinforcements that included additional Neut-Legions, DPS and Guardians. Bringing Bhaalgorns in would have been a total suicide, as we were barely keeping T3’s alive in the withering storm of XL sized antimatter charges. Although we had not killed any of their ships yet, the prolonged fighting (now close to 1 hour) clearly started to take a toll on the Jedi’s also. At this point one of the Moroses is primary again immediately after it enters Siege mode. We slowly chew away at its armor and Void M, Hail M and coalesced beams of light chip away at its armor penetrating for the first time into its structure. Teamspeak was silent apart from the FC who relayed his orders calmly: “Overheat what you can, do not burn out, I repeat DO NOT burn out”. The semi-circle indicating the structure integrity of the target went down painfully slow 75% – 50% – 20%. “He is OUT of siege – he’s getting reps again” the speakers echoed. The disappointment was palpable but at this point we were fully committed – either we win or we all die. We try again, and again. The same Moros is 20 minutes later saved from 2% armor and 20% structure gliding out of Siege mode just in time. To keep the Archon pilots stressed we try to Alpha through the subcaps on field on several occasions but even without Triage mode active the carriers are able to keep the sub-capital ships permalocked and as such provide immediate repairs. No luck there either.

In turn we cycle all of our guns and all of our neuting power to the Archons that now have to spend cap repairing the Moros and themselves. However, when there are two Archons on the field this is a difficult feat to accomplish, because the primaried carrier can save cap by not remote repairing the Moros and only itself while the not-primary Archon repairs the Moros. Our losses accumulate slowly but steadily, but so does our fleet size. The combined efforts of the now reinforced fleet, numbering around 50 pilots, and the heavy stress of continuous fighting gives us a chance to clinch this. The Moros that has previously has been barely saved on two occasions enters siege, with only 70% armor and little capacitor. Simultaneously both the Archons are in triage and one of them is capped out by our neuting and its efforts to repair the Moros. We hurl everything that we have at that Moros – 50 % armor , 20% armor. Yet again , teamspeak resonated the orders from the FC “Overheat your guns, do not burn out, I repeat DO NOT burn out”. That time we got him, the first Jedi ship to die after a grueling 1.5 hours of fighting.

The Archons were struggling at this point with exhaustion, cap management and triage cycling and after the first Moros went down, we proceeded to grind down the two remaining Moroses with ruthless efficiency. It took some time but we had blood lust in our minds and a hunger for kill mails. We then mopped up the Archons and the remaining subcaps on field which included at least one Loki and one Rapier.


I hope the length of the BR hasn’t deterred you dear reader, it only aims to depict the events that led to this glorious confrontation that scouting included, lasted for 4-5 hours. Many people and entities partook in this operation and I’ll try to mention them . Firstly we have to thank Ixtab. and Ash Alliance, without them this fight would have not been possible with the result we managed to achieve. The FC performed admirably, relaying clear orders and coordinating reinforcements. Scouts also did a good job, although failing in the beginning to see that they were collapsing us out the ensuing scouting was good and special points for the “spider sense”. Special mention goes also to the fleet members who despite of 1.5 hours of constant fighting managed to keep combat comms. I don’t think we heard the oh-so frustrating “IM DYING, PLEASE HELP” scream even once . People stepped up, gave short comments when asked, answered questions briefly and followed orders. Excellent work.
However the biggest acknowledgement and appreciation has to go to Jedi Knight Orden, they brought a fight, and they fought valiantly, with skill and determination. It was an honor fighting them. With experience comes skill, and with good skills you are not afraid of fighting. Sometimes when you fight you lose. I am sure they will be back on their feet in no time providing content and fights for themselves and everybody else.

“Train yourself to let go of everything you fear to lose”
Master Yoda, Star Wars Episode III: Revenge of the Sith (2005)

Butchers tally:

15 Ships lost, total approx. 11 bil ISK, that Talwar must be a glitch in Eve-kill again
3 Moroses destroyed, estimated total 14 bil ISK
2 Archons destroyed, estimated total 8 bil ISK
3 confirmed subcaps destroyed,, estimated 2 bil ISK
Eleniti of Polarized. and DEEP-SPACE CO-OP LTD

[EVE Kill Battle Summary]

The title of the BR refers to the Jedi’s fighting like Bears (not carebears but true bad-ass russian bears). Fighting to the last man taking as many of us , the attackers with them, and not using self-destruct.

– Eleniti of Polarized. and DEEP-SPACE CO-OP LTD


  1. Cybus

    so you found some carebears you couldn’t kill and you batphoned like crazy, and you claim it’s a good fight….. is this what w-space has come to?

    July 24, 2013 at 5:21 pm Reply
    1. D-FENCE

      is it really fair to call the defenders carebears? They were technically the only one kicking someone’s ass in this whole cluster fuck.

      July 25, 2013 at 1:05 am Reply
      1. cybus

        that is true, the farmers did a very good job.

        July 25, 2013 at 6:31 pm Reply
        1. GoodFight

          At the end of this article he typed this:

          The title of the BR refers to the Jedi’s fighting like Bears (not
          carebears but true bad-ass russian bears). Fighting to the last man
          taking as many of us , the attackers with them, and not using

          July 30, 2013 at 1:20 pm Reply
  2. Depolarized

    Can’t kill a handful of caps without calling half of w-space and then boring the shit out of the rest of us with a 2000 word essay about how shit you are?

    July 24, 2013 at 5:22 pm Reply
  3. Actual big wormhole entity.

    So your initial fleet size is 10 times bigger. You then proceed to bat-phone ash alliance to get more numbers while bringing your own reinforcements.

    You lose stuff in a fight where you should have no losses.

    Then you brag about it on your own forums.

    Then you even mail it to evenews24.

    And the best part. Evenews24 posts this rubbish.

    Go and hide in a corner, in utter shame.

    I am disgusted.

    There will be repercussions for this.

    July 24, 2013 at 5:24 pm Reply
    1. TiredOfAllTheStupid

      They can consider this an eviction notice.

      July 24, 2013 at 10:11 pm Reply
      1. NotAWHDude

        Put them on a list!!!

        July 25, 2013 at 2:54 am Reply
        1. Listed

          I think Polarized never warns before eviction, they just do it. Maybe you’re next, who knows?

          July 25, 2013 at 6:57 pm Reply
    2. Shana Zera

      There will be CONSEQUENCES!!

      July 25, 2013 at 1:08 am Reply
  4. Tuna

    Polarized needs to be punished :)

    July 24, 2013 at 5:24 pm Reply
  5. Jesus Christ

    No video? C’mon why is this even posted? 2 hours and none of them recorded it? And i get a documentary to read? C’mon…just no.

    July 24, 2013 at 5:55 pm Reply
  6. Dura

    holy fucking blobbyness

    July 24, 2013 at 5:56 pm Reply
  7. Dura

    ”Polarized high as fuck using Star Wars Yedi quotes, blobbing the fuck out of some beares and shit”

    July 24, 2013 at 6:07 pm Reply
  8. StarFleetCommander


    July 24, 2013 at 6:12 pm Reply
  9. JamesWyh

    I only made it to the end but it sure was fun!

    July 24, 2013 at 7:06 pm Reply
  10. real_pro

    So essentially you blob these guys, and then take 3 hours to kill them even when having 10x their numbers. Real pro.

    July 24, 2013 at 7:06 pm Reply
    1. kinda pro.

      To be fair the fight was pro from the defender point of view they held out for that long out numbered like that by harder to damage ships because of sig radius and they still piled the field a mile high with wrecks before getting dragged down. I would love to read a BR from the “losing” side at least they know how to fight.

      July 25, 2013 at 1:03 am Reply
  11. Puberty Bound

    No matter how many words you use to dress this pig up thats all it is, a pig – get over yourself.

    July 24, 2013 at 7:27 pm Reply
  12. oi

    You can’t look purely at numbers, capitals with capital support

    July 24, 2013 at 8:07 pm Reply
    1. lolscrub

      because dreads are awesome at tracking t3s…

      July 24, 2013 at 9:48 pm Reply
  13. SpaceJew

    You are the trash and cancer that plagues the EVE space. Pod yourself and biomass.

    July 24, 2013 at 8:56 pm Reply
  14. Jedward

    This is news?

    July 24, 2013 at 9:07 pm Reply
    1. anon

      Your post is relevant?

      July 24, 2013 at 10:21 pm Reply
      1. Jedward

        I think you’ll find our news is far more Revenant than this.

        July 25, 2013 at 12:32 am Reply
  15. Rhoaden

    You no what make’s me mad none of you mother fucker’s had to read it. Sound’s like a great fight don’t listen to the retards was a decent read.

    July 24, 2013 at 9:33 pm Reply
  16. Guest101

    i would appreciate a small summary type thing so i don’t have to read all of that… i just don’t care about what goes on in an irrelevant wh so far far away to read that.. i’d like to know what your saying though

    July 24, 2013 at 9:48 pm Reply
    1. Arrendis

      He’s saying stuff about ‘an irrelevant wh so far far away’. So I guess you don’t care, after all.

      July 26, 2013 at 6:48 am Reply
  17. Theronth

    ASH and Polarized. together, what a delicious coctail. It deserves it’s own name, what do you think of The Barf Bucket?

    July 25, 2013 at 4:18 am Reply
    1. Justin Cody


      July 25, 2013 at 7:11 am Reply
  18. mynameisnameisnameis

    To big article for fight like this, few words and kb link wuld be enough.

    July 25, 2013 at 11:27 am Reply
  19. Innocent bystander

    What a lot of grudge and anger. It seems to me like a genuin article from some one who clearly had to work hard and had a lot of excitement, fun to read. Are loads of these comment posters hurt by this group? WH space is a strange place in Eve.

    July 25, 2013 at 6:26 pm Reply
  20. Wannabe Rem Seven fan

    So much hate for Polarised, I’m sure too all the haters you would batphone if you didn’t have the online numbers….. Respect to Polarised, article is a bit long but good to read more of w-space fights on here!

    July 26, 2013 at 11:30 am Reply
  21. nev

    great read! love wormhole pvp

    August 2, 2013 at 12:31 am Reply

Leave a Reply