Day 2 of the war with The Bastards. and I decided that we would try something during West Coast USTZ. You see, on Thursday (Day 1) there were no war targets online and available to provide us with content. I fit a few ships we had imported for the war, but was tired and called it a short night.
So, in the morning of Friday, I announced that we would be having a fleet. If the war targets decided to grace us with their presence, then we would try to accept their content generation (and provide Bob with his required sacrifices). If there were no war targets available, then we will go look to pick a fight.
We formed up the fleet at 03:30 with one war target in system with us, Michael Pancake. Seeing as though we outnumbered him like 20:1, I decided to act honorably and request a 1v1:
[ 2015.02.14 03:07:22 ] Kiri Jol > Michael Pancake 1v1 at planet 1?
[ 2015.02.14 03:08:37 ] Michael Pancake > nice joke
[ 2015.02.14 03:08:45 ] Draiv Solregard > no joke, he's serious
[ 2015.02.14 03:08:52 ] Marq Aideron > nah dude, we'll honor a 1v1
[ 2015.02.14 03:09:03 ] Marq Aideron > no links, no ecm, no backup
[ 2015.02.14 03:09:09 ] Kiri Jol > Michael Pancake so, is that a no?
[ 2015.02.14 03:09:12 ] LoKi Wackenbush > I'll stay at the station..
[ 2015.02.14 03:09:23 ] Raoul Herrington > Me too
[ 2015.02.14 03:09:28 ] Michael Pancake > LoKi Wackenbush you are my smallest problem
[ 2015.02.14 03:09:58 ] Kiri Jol > no?
[ 2015.02.14 03:10:05 ] LoKi Wackenbush > didn't I blow you up already tonight?
[ 2015.02.14 03:10:14 ] Argos Gelert > Aww, I was hoping to be your smallest problem...
[ 2015.02.14 03:10:18 ] Kiri Jol > wow, i was told that The Bastards are all about honour
[ 2015.02.14 03:10:30 ] Raoul Herrington > I thought I was the small problem
[ 2015.02.14 03:10:42 ] Matthew Kalidan > I AM the smallest
[ 2015.02.14 03:10:56 ] Michael Pancake > Kiri Jol when im looking on your kb i dont know if you are sure what is 1v1
[ 2015.02.14 03:11:09 ] Kiri Jol > np
[ 2015.02.14 03:11:17 ] Kiri Jol > clearly you refuse a request for a 1v1
[ 2015.02.14 03:11:24 ] Michael Pancake > haha
[ 2015.02.14 03:11:43 ] Draiv Solregard > what's funny is if we didn't honor it you could whine about it on twitter
[ 2015.02.14 03:11:53 ] Kiri Jol > no, just nashh
[ 2015.02.14 03:11:55 ] Draiv Solregard > but I guess that needs to be pointed out
[ 2015.02.14 03:11:59 ] Michael Pancake > some of guys young, some drunk and some just dump
[ 2015.02.14 03:12:02 ] Kiri Jol > he is all about the honr game
[ 2015.02.14 03:12:02 ] Michael Pancake > srsly
Clearly he was not in the mood to provide us with content, so we elected to take a roam out. We debated whether to go in Frigates or Cruisers, and finally decided upon Frigates. We got about 12 dudes in the fleet with 2 Inquisitors for logi and 2-3 ewar frigates as well.
We set destination for Heydieles, but prior to leaving I decided to take care of some house keeping. We had a "few" (honestly about 40% of the fleet) rookie pilots who were literally going out on their first PVP roam. We discussed broadcasting for repairs, turning off safety, and other items. With all of that sorted, we set out for Heydieles with our scout +1.
Things were relatively light until we got to Kedama, Our scout reported that there was a Tristan in a plex and he warped in to obtain the initial tackle. Unfortunately, he was going down pretty fast and went down as our fleet was landing in warp at his postion.
-1 Scout
But, we were able to kill the Tristan and pod him back to Bob:
Tristan
Pod
Things remained very quiet as we waited for our scout to re-ship and for another member of the fleet to catch up from Ishomilken, except for some slips in operational security and the pre-requisite shooting of blues due to overview settings (most likely from a rookie pilot):
[ 2015.02.14 04:12:08 ] Kiri Jol > this is making for a fantastic blog post tomorrow
[ 2015.02.14 04:12:20 ] Kiri Jol > opsec in local, shooting blues due to overview, etc
Our scout caught up to us along with the additional member of the fleet, so we continued on towards Heydieles. It was there that we caught our next action. Unfortunately, the length of warp from the in gate to the plex led to us losing two scouts:
Scout #1
Scout #2
At this point, we had reached our destination. We had gotten one kill for the fleet, and we were about even in the ISK war. I should have turned us back and headed home. But, there was a report of a Kronos in Old Man Star agressed on a station. Clearly in hindsight this was obvious bait, but seeing as our war targets had refused to provide us with content, I went all Leroy Jenkins and had the fleet get onto the Old Man Star gate.
I had another member of the fleet become the 3rd scout and had him warp to a station at 100km. He reported an Exequror on station, so I had the fleet jump in. Ruh ro (in the scooby voice). Gnosis and Ishtar on the gate. We primaried the Gnosis as he was red and i had the logis and ewar setup. Within a few seconds, additional hostiles warped onto the grid, so I gave the command to disengage and get clear. Shockingly we only lost 3 ships and no pods.
FC
Griffin
Inquisitor
Loot fairy said no, and did not drop my scrambler.
So, I had the backup FC get the fleet back to Ishomilken while I went AFK for a few. Fleet arrived safely back in Ishomilken with no further losses.
Then, while in Ishomilken I made one final request to our war target to provide content to us. Again, he refused:
[ 2015.02.14 04:52:14 ] Kiri Jol > Michael Pancake 1v1?
[ 2015.02.14 04:52:25 ] Michael Pancake > to late mate
[ 2015.02.14 04:52:36 ] Gori Thane > Kiri Jol frig 1v1?
[ 2015.02.14 04:53:08 ] Kiri Jol > :( Michael Pancake
[ 2015.02.14 04:53:23 ] Michael Pancake > its rly late in my TZ
[ 2015.02.14 04:53:29 ] Kiri Jol > k
[ 2015.02.14 04:54:07 ] Kiri Jol > Gori Thane planet 1
[ 2015.02.14 04:57:53 ] Gori Thane > haha wow gf
[ 2015.02.14 04:57:55 ] Kiri Jol > gf
Very nice 1v1 at the planet. Once I killed off his drones, his DPS disappeared. And, a very friendly exchange after the fight:
[ 2015.02.14 04:58:37 ] Gori Thane > do you know what your targeting range was>?
[ 2015.02.14 04:58:44 ] Kiri Jol > about 20k
[ 2015.02.14 04:58:52 ] Kiri Jol > never had a problem when i got in that close
[ 2015.02.14 04:58:54 ] Gori Thane > hmm ok cool, thanks =)
[ 2015.02.14 04:58:57 ] Kiri Jol > np
[ 2015.02.14 04:59:12 ] Gori Thane > also thanks for not gang raping me lol
[ 2015.02.14 04:59:22 ] Kiri Jol > ABA honors 1v1 requests
[ 2015.02.14 04:59:29 ] Gori Thane > good to know =)
[ 2015.02.14 04:59:35 ] Kiri Jol > fly safe!
[ 2015.02.14 04:59:39 ] Gori Thane > o7
[ 2015.02.14 04:59:42 ] Kiri Jol > o7
We made one final attempt to have our war target provide us with content, and this time it worked:
[ 2015.02.14 05:19:23 ] Sanders Schmittlaub > Where's the honourable 1v1 Pancake?
[ 2015.02.14 05:19:39 ] Michael Pancake > im to tired
[ 2015.02.14 05:20:14 ] Sanders Schmittlaub > Then you should probably go to bed :)
[ 2015.02.14 05:20:21 ] Michael Pancake > what are trying to achive?
[ 2015.02.14 05:21:13 ] Sanders Schmittlaub > Fights.
[ 2015.02.14 05:21:38 ] Michael Pancake > but only with friends as backup?
[ 2015.02.14 05:21:49 ] Sanders Schmittlaub > Haven't called them.
[ 2015.02.14 05:21:59 ] VanHellin Krovchenko > gf
[ 2015.02.14 05:22:11 ] Marq Aideron > gf
[ 2015.02.14 05:22:13 ] Raoul Herrington > GF to you as well
[ 2015.02.14 05:22:39 ] Sanders Schmittlaub > I'm enjoying this war so far, how about you?
[ 2015.02.14 05:23:15 ] Michael Pancake > some content for you, for me nothing special tbh
[ 2015.02.14 05:23:34 ] Marq Aideron > the smugness...
[ 2015.02.14 05:23:52 ] Dragon blizard > Raoul Herrington thanks
[ 2015.02.14 05:24:11 ] Sanders Schmittlaub > Do you usually cower out of every fight?
[ 2015.02.14 05:24:14 ] Raoul Herrington > NP
[ 2015.02.14 05:25:14 ] Michael Pancake > i will not call friends lol
[ 2015.02.14 05:25:29 ] Sanders Schmittlaub > GF :)
[ 2015.02.14 05:25:50 ] Michael Pancake > dont write gf after blob
[ 2015.02.14 05:25:54 ] Michael Pancake > dont
[ 2015.02.14 05:26:05 ] Michael Pancake > this general rule :)
[ 2015.02.14 05:26:12 ] Sanders Schmittlaub > Call me after the war and we'll 1v1
[ 2015.02.14 05:26:34 ] Michael Pancake > im numnut at pulled 7k range with blasters
[ 2015.02.14 05:27:05 ] Sanders Schmittlaub > Kill: Michael Pancake (Merlin)
With that, the fleet toyed around in the surrounding systems but there really was not much activity at all.
We are still waiting on that content you stated you were going to provide. We'll be waiting at Ishomilken V - State Protectorate Logistic Support.
Showing posts with label pvp. Show all posts
Showing posts with label pvp. Show all posts
Saturday, February 14, 2015
Monday, February 2, 2015
Mistakes Were Made
Sunday morning we encountered some hostiles in our wormhole and unfortunately a series of mistakes were made which lead to an unfortunate level of red on the killboard.
As I awoke and logged into EVE, there was report of some possible hostile activity in our wormhole. The initial report from corp members was of a Proteus on our High Sec static hole, shooting at the Mobile Large Warp Dispruptor II bubble. I jumped into standing fleet, and pinged everyone to join Fleet comms on TS.
One of the members had an alt in the hole who could warp over and sit cloaked at a perch on the hole. He logged in that character, and as he did one of the corp members piped up in Fleet chat that he had engaged a Sabre on the relatively new C4 hole we also had. I attempted to initiate warp to his position, but we received the error message that the pilot was not in our system. Fail, evidently by the time he elected to say anything he was podded back to high sec. Now, never during this time did he say anything to us on TS, as he was not on TS. Mistake #1
Loss #1 Manticore
Loss #2 Pod
I warped the fleet over to the C4 hole at 100, and the Sabre was there. I bounced us off a celestial and back to the hole at 20. We engaged the Sabre and he decided to jump back to the C4. Now, bear in mind no single corp member had elected to scout out the C4. This may have been important as we shall see soon.
Our cloaky scout was at the perch over the high sec hole and reported that the Proteus was indeed in the bubble shooting at the bubble. He also was joined by an Ishtar. I was still trying to organize the fleet and get a relatively decent composition for engaging the Proteus. It was about this time that we had a 2nd member of the corp decide to poke around at the C4 hole. SMH. At least he was on comms and immediately verbalized that he was being shot at by the Sabre. Again, I warped the fleet over to the C4 hole and immediately the Sabre jumped back. There were two mistakes in this engagement. Mistake number one was to fit faction torpedo launchers to a PVP ship with a tank slightly better than an Ibis. Mistake number two was the independent corp member electing to go to that hostile hole where the Sabre was. Mistake #2 & #3
Loss #3 Nemesis
Loss #4 Pod
We now had 5 members in the fleet with us, and with 4 of us in BC/HAC hulls I felt reasonably sure that we had enough DPS to kill the Ishtar and the Proteus, especially as my alt was in a Pilgrim, and the neut pressure from her would shut down any active tank of the Proteus. So, I warped her over to the high sec hole and started to get her positioned cloaked off of the Proteus. Unfortunately, I alt-tabbed between the two accounts and when I did it appears that she was decloaked by "something". The mistake here was attempting to dual box without the necessary precautions. Mistake #4
Loss #5 Pilgrim
Loss #6 Pod
We still had 3 battlecruisers and my Ishtar, so I elected to proceed into the engagement. I had the fleet warp to the bubble and we began to engage. His tank was decent, but we slowly began to chip away at his armor. As he dipped below 50% armor, our Brutix pilot mentioned that he was breaking. We had no logis, so I ordered him to begin aligning out of the bubble, but he went down and the Proteus jumped back into high sec. The mistake here was not getting into optimal range for our weapons. The Brutix would certainly have done better damage projection if he were up close and personal. Mistake #5
Loss # 7 Brutix
Then, as his pod was beginning to slowly trek out of the bubble, an Astero uncloaks and pods him. Afterwards, the pilot mentioned that he was closer to the high sec hole than the edge of the bubble. Mistake #6 was not having him jump to high sec.
Loss #8 Pod
The proteus would now continue to play games jumping into and out of our hole, so we decided to leave him alone for now. With the remainder of our fleet in the POS, the cloaky scout reported a Prophecy on scan and landing at the high sec hole. He was a member of the C4 residents and this should have told us more about their intentions. I had our fleet warp to the high sec hole, but from our POS we were on the opposite edge of the bubble from the Prophecy. He warped back to his hole when he saw us. I warped the fleet to the C4 at range, and the Prophecy jumped into his hole. I left our scout on the C4 hole to hear if anything came through. A corp member in high sec reported that the proteus pilot was back, but he was now in an Armageddon, and he jumped. I warped out fleet to the high sec hole and we began to engage the geddon. He was heavy neut fit and rapidly depleted the cap of many of the fleet members. Within 10-15 seconds, the C4 hole exploded with hostiles. I gave the command to disengage and get out of the bubble. Luckily the Oracle and Hurricane escaped. Sadly, my Ishtar did not. Mistake #7 was the failure to properly scout out the C4 hole.
Loss #9 Ishtar
Loss #10 Pod
Some very expensive lessons to be learned, but if the corporation members learn only one thing it is that it is never sufficient to simply scout a hole and bookmark it after adding it to tripwire. Some holes are empty, but many are not, and the bad scary many may come to inflict space violence upon your ship and pod.
Summarized Battle Report
As I awoke and logged into EVE, there was report of some possible hostile activity in our wormhole. The initial report from corp members was of a Proteus on our High Sec static hole, shooting at the Mobile Large Warp Dispruptor II bubble. I jumped into standing fleet, and pinged everyone to join Fleet comms on TS.
One of the members had an alt in the hole who could warp over and sit cloaked at a perch on the hole. He logged in that character, and as he did one of the corp members piped up in Fleet chat that he had engaged a Sabre on the relatively new C4 hole we also had. I attempted to initiate warp to his position, but we received the error message that the pilot was not in our system. Fail, evidently by the time he elected to say anything he was podded back to high sec. Now, never during this time did he say anything to us on TS, as he was not on TS. Mistake #1
Loss #1 Manticore
Loss #2 Pod
I warped the fleet over to the C4 hole at 100, and the Sabre was there. I bounced us off a celestial and back to the hole at 20. We engaged the Sabre and he decided to jump back to the C4. Now, bear in mind no single corp member had elected to scout out the C4. This may have been important as we shall see soon.
Our cloaky scout was at the perch over the high sec hole and reported that the Proteus was indeed in the bubble shooting at the bubble. He also was joined by an Ishtar. I was still trying to organize the fleet and get a relatively decent composition for engaging the Proteus. It was about this time that we had a 2nd member of the corp decide to poke around at the C4 hole. SMH. At least he was on comms and immediately verbalized that he was being shot at by the Sabre. Again, I warped the fleet over to the C4 hole and immediately the Sabre jumped back. There were two mistakes in this engagement. Mistake number one was to fit faction torpedo launchers to a PVP ship with a tank slightly better than an Ibis. Mistake number two was the independent corp member electing to go to that hostile hole where the Sabre was. Mistake #2 & #3
Loss #3 Nemesis
Loss #4 Pod
We now had 5 members in the fleet with us, and with 4 of us in BC/HAC hulls I felt reasonably sure that we had enough DPS to kill the Ishtar and the Proteus, especially as my alt was in a Pilgrim, and the neut pressure from her would shut down any active tank of the Proteus. So, I warped her over to the high sec hole and started to get her positioned cloaked off of the Proteus. Unfortunately, I alt-tabbed between the two accounts and when I did it appears that she was decloaked by "something". The mistake here was attempting to dual box without the necessary precautions. Mistake #4
Loss #5 Pilgrim
Loss #6 Pod
We still had 3 battlecruisers and my Ishtar, so I elected to proceed into the engagement. I had the fleet warp to the bubble and we began to engage. His tank was decent, but we slowly began to chip away at his armor. As he dipped below 50% armor, our Brutix pilot mentioned that he was breaking. We had no logis, so I ordered him to begin aligning out of the bubble, but he went down and the Proteus jumped back into high sec. The mistake here was not getting into optimal range for our weapons. The Brutix would certainly have done better damage projection if he were up close and personal. Mistake #5
Loss # 7 Brutix
Then, as his pod was beginning to slowly trek out of the bubble, an Astero uncloaks and pods him. Afterwards, the pilot mentioned that he was closer to the high sec hole than the edge of the bubble. Mistake #6 was not having him jump to high sec.
Loss #8 Pod
The proteus would now continue to play games jumping into and out of our hole, so we decided to leave him alone for now. With the remainder of our fleet in the POS, the cloaky scout reported a Prophecy on scan and landing at the high sec hole. He was a member of the C4 residents and this should have told us more about their intentions. I had our fleet warp to the high sec hole, but from our POS we were on the opposite edge of the bubble from the Prophecy. He warped back to his hole when he saw us. I warped the fleet to the C4 at range, and the Prophecy jumped into his hole. I left our scout on the C4 hole to hear if anything came through. A corp member in high sec reported that the proteus pilot was back, but he was now in an Armageddon, and he jumped. I warped out fleet to the high sec hole and we began to engage the geddon. He was heavy neut fit and rapidly depleted the cap of many of the fleet members. Within 10-15 seconds, the C4 hole exploded with hostiles. I gave the command to disengage and get out of the bubble. Luckily the Oracle and Hurricane escaped. Sadly, my Ishtar did not. Mistake #7 was the failure to properly scout out the C4 hole.
Loss #9 Ishtar
Loss #10 Pod
Some very expensive lessons to be learned, but if the corporation members learn only one thing it is that it is never sufficient to simply scout a hole and bookmark it after adding it to tripwire. Some holes are empty, but many are not, and the bad scary many may come to inflict space violence upon your ship and pod.
Summarized Battle Report
Tuesday, January 13, 2015
Red Haired Stepchild No Longer
Proteus was released today by CCP which marks the latest release in the rapid cycle of development and deployment.
This release was lighter than previous ones mostly due to the holiday period occurring prior to the deployment. However, there is one wrinkle in this release that seems to have generated the most amount of chatter on forums and blogs, the tiericide of Combat Recons.
See, for many years the Combat Recon class of ships has been a red haired step child. They really cannot be used as scouts like their little brother, Force Recon ships which can warp cloaked and light covert cynos. They even are really not preferred in fleet doctrines, as use of Strategic Cruisers is preferred as they have the ability to fit a bigger tank than the Combat Recon. No, for many years the Combat Recon has been mostly devoted to a role of small roaming gang ewar platform or possibly solo PVPers. Myself, I have kept 3-4 of them in a hangar in Jita collecting dust. That all changed today.
The part about the tiericide which has generated the largest amount of tears is the buff for the class of ships in relation to directional scanning. For everyone living outside of High Security space (Low, Null and Wormhole) the directional scanner is your best friend. The scanner will inform you of things like probes on scan, other ships, and items in space like containers, control towers and force fields. As of today, these ships no longer show up on directional scanner, ever. There is no module you can fit to help with that, nor is there any skill which would allow it. Sure, there were some other changes to the ships to improve their usability in EVE, but the one change which should drive an increased use of these ships is the immunity to appearance of the ship on directional scanner.
Rixx Javix posted a new post this morning which was a great read. Go ahead and have a read over there, then come back here. Some very excellent points in Rixx's post and I tend to agree that the changes to Combat Recons will upset the apple cart for many people in EVE. I feel that the changes will be mostly felt in Wormhole space, where there is no local for you to appear in. You are actually far better off in a Combat Recon compared to a Strategic Cruiser or Stealth Bomber in wormhole space. Those ships will at least appear on directional scanner when they jump through a wormhole and decloak. The Combat Recon will not.
The other part about Rixx's post that I feel strongly about is the fact that they still are Combat Recons. The do not bring overwhelming DPS to the engagement. They usually are not brick fit as that would compromise their DPS or e-war capabilities. The tank of a Combat Recon usually will hover in the 30-40k DPS tank area if they are also fit to take advantage of their e-war bonuses. What this all means is that you still "should" be able to survive an engagement with these ships, well maybe.
Your survival odds will increase if the engagement is with a Rook or Huginn. The Rook is an ECM platform, so he will be jamming you. The Huginn's bonuses are to it's webs, so they will slow down your speed. Where you are screwed is the Lachesis or Curse.
Lets talk about the Lachesis first. Bonuses to warp disruption/scrambling optimal range and sensor dampener effectiveness. With the 7 mid slots of this ship, I would fit a faction scram and point along with 1-2 dampeners. If a lachesis is the combat recon which appears on grid with you, it is very doubtful that you are escaping. It is not uncommon to see unbonused points of 70km with a faction point and if fit with a +3 scram, even though you are stabbed you will not be going anywhere.
That brings us to the Curse. This nasty ship is getting bonuses for drone hitpoints and damge, tracking disruptor effectiveness, energy vampire/neutralizer transfer range and energy vampire/neutralizer transfer amount. If you see a curse appear magically on grid with you, start aligning to that celestial with your pod. His high slots will almost all be energy vamps/neuts. He will have a scram fit, and drone damage amplifiers in his lows. His DPS are the drones. Within one cycle of his vamps and neuts your capacitor is bone dry. Scotty will inform you that warping is not possible.
Even though these ships have been provided with some very positive changes in the game, I do not feel that they are overpowered. Yes, they will be the FOTM for the foreseeable future, until there is some type of buff due to wormhole corporations who get stupid and run sites without zipping up their holes.
I applaud you CCP for continuing to make EVE better and I can now rename all of my Curse's to non-red haired children's names.
This release was lighter than previous ones mostly due to the holiday period occurring prior to the deployment. However, there is one wrinkle in this release that seems to have generated the most amount of chatter on forums and blogs, the tiericide of Combat Recons.
See, for many years the Combat Recon class of ships has been a red haired step child. They really cannot be used as scouts like their little brother, Force Recon ships which can warp cloaked and light covert cynos. They even are really not preferred in fleet doctrines, as use of Strategic Cruisers is preferred as they have the ability to fit a bigger tank than the Combat Recon. No, for many years the Combat Recon has been mostly devoted to a role of small roaming gang ewar platform or possibly solo PVPers. Myself, I have kept 3-4 of them in a hangar in Jita collecting dust. That all changed today.
The part about the tiericide which has generated the largest amount of tears is the buff for the class of ships in relation to directional scanning. For everyone living outside of High Security space (Low, Null and Wormhole) the directional scanner is your best friend. The scanner will inform you of things like probes on scan, other ships, and items in space like containers, control towers and force fields. As of today, these ships no longer show up on directional scanner, ever. There is no module you can fit to help with that, nor is there any skill which would allow it. Sure, there were some other changes to the ships to improve their usability in EVE, but the one change which should drive an increased use of these ships is the immunity to appearance of the ship on directional scanner.
Rixx Javix posted a new post this morning which was a great read. Go ahead and have a read over there, then come back here. Some very excellent points in Rixx's post and I tend to agree that the changes to Combat Recons will upset the apple cart for many people in EVE. I feel that the changes will be mostly felt in Wormhole space, where there is no local for you to appear in. You are actually far better off in a Combat Recon compared to a Strategic Cruiser or Stealth Bomber in wormhole space. Those ships will at least appear on directional scanner when they jump through a wormhole and decloak. The Combat Recon will not.
The other part about Rixx's post that I feel strongly about is the fact that they still are Combat Recons. The do not bring overwhelming DPS to the engagement. They usually are not brick fit as that would compromise their DPS or e-war capabilities. The tank of a Combat Recon usually will hover in the 30-40k DPS tank area if they are also fit to take advantage of their e-war bonuses. What this all means is that you still "should" be able to survive an engagement with these ships, well maybe.
Your survival odds will increase if the engagement is with a Rook or Huginn. The Rook is an ECM platform, so he will be jamming you. The Huginn's bonuses are to it's webs, so they will slow down your speed. Where you are screwed is the Lachesis or Curse.
Lets talk about the Lachesis first. Bonuses to warp disruption/scrambling optimal range and sensor dampener effectiveness. With the 7 mid slots of this ship, I would fit a faction scram and point along with 1-2 dampeners. If a lachesis is the combat recon which appears on grid with you, it is very doubtful that you are escaping. It is not uncommon to see unbonused points of 70km with a faction point and if fit with a +3 scram, even though you are stabbed you will not be going anywhere.
That brings us to the Curse. This nasty ship is getting bonuses for drone hitpoints and damge, tracking disruptor effectiveness, energy vampire/neutralizer transfer range and energy vampire/neutralizer transfer amount. If you see a curse appear magically on grid with you, start aligning to that celestial with your pod. His high slots will almost all be energy vamps/neuts. He will have a scram fit, and drone damage amplifiers in his lows. His DPS are the drones. Within one cycle of his vamps and neuts your capacitor is bone dry. Scotty will inform you that warping is not possible.
Even though these ships have been provided with some very positive changes in the game, I do not feel that they are overpowered. Yes, they will be the FOTM for the foreseeable future, until there is some type of buff due to wormhole corporations who get stupid and run sites without zipping up their holes.
I applaud you CCP for continuing to make EVE better and I can now rename all of my Curse's to non-red haired children's names.
Subscribe to:
Posts (Atom)