Recounting My Destruction, Part 1

My last post, I identified the explosion of XQ0058. Before my extended break from Eve, I posted the boom of XQ0034. Many ship kill mails to catch up on, so here we go.

XQ0035 Kill Mail
Dramiel fit

Dramiels continue to give me problems. Ciba LexLulu represented Stay Frosty well here, but I do not think a Tristan really stands any sort of chance in this match up. Especially this kiting fit against his howitzer fit.

I was able to locate a possible fit on ZKillboard.

ZKillboard, throughout this time, became a mixed blessing. I enjoy the intel it provides, as well as the reflection opportunity to improve my PvP knowledge. However, the stats inspire a lot of competition within me. Competition against whom? That is the question. I discovered that I begin to set goals for myself, or maybe it is more accurate that I began to fret over my stat image. During most of this time I was maintaining a ZKillboard rate of 50/50, and a dominant solo stat. I have to admit that I enjoyed this, and wanted to expand the lead of kills versus losses.

I mention this, because I feel some of my losses here began to take a toll. If I’m to be honest, I do not believe I was as reckless as I meant to be as I started this challenge. The remaining kill mail messages that follow contain a little more emotion than they should, and I think may have also contributed to my break. That and real life obligations of course.

You will see near the end of this parade of kill mails I enter a bit of a slump. As I reflect back, I do believe I put too much emphasis in maintaining, improving a perceived stat standard, and this led to me focusing on the wrong details – adding a certain level of stress to the experience.

This emotion is not new, I understand, but a genuinely believe it is an important detail that I need to put aside to improve my game. Focus on the battle at hand, without worry of the perception of others, or stats. As I re-engage in this challenge, I am aware of this, and my latest loss, (which I will post in a future entry), reflects my determination to fly dangerously with intent to burn.

XQ0036 Kill Mail

XQ0036 went on the attack into a plex. Once I was scrammed, not much I could do to pull the necessary distance needed for the drones to take him down. Important note here, the Loyalty Points awarded back when I was killed here, versus the Loyalty Points awarded in my last kill mail: 192 LP vs. 1,528 LP. Great boost! So happy this got more attention, and boosted.

XQ0037 Kill Mail

XQ0037 was defending a plex. Kalmaaron in his Imperial Navy Slicer was just too fast. He was able to quickly close the distance, scram, and finish the job – quickly.

XQ0038 Kill Mail

XQ0038 was the victim of my logging after some time within my break. My log ins were sporadic, and I was not really paying attention to CCP events taking place. I believe I was inspired to go to a local asteroid field to kill a rat, in hopes of collecting bonus skill points. I did not intend on a rat getting point on me, and being a bit more challenging than normal. I believe I prefer the kill mails were the station guns took me out, rather than this one. Oh well, XQ0038 sacrificed.

XQ0039 Kill Mail

XQ0039 attacked Physical Removal’s Kestrel. This is a skill I need to focus on when attacking a plex in a kiting fit. It is so challenging to pull distance from the target, distance needed to survive the fight.

If I remember correct, I researched his fit as I was surprised at how little damage I was able to inflict before exploding.

XQ0040 Kill Mail

The kill mail for XQ0040 may seem like a gank, but it was actually more fun than that. It would have been presented better as a stand alone post, but my slacker break prevented a proper story roll out.

Revenge for my 64th & 65th kills

Captain Arimanius and Hyper Codar brought a friend to redeem themselves after I took both of them out in their Kestrels. I guess when you can’t gank with two, bring a third! It was fun though, and totally worth XQ0040’s demolition.

XQ0041 Kill Mail

Following up a fun ambush in XQ0040, XQ0040 was just an ambush. Heading to a novice plex to attack a condor, Lauralite Ann Brezia sat in wait in her Lachesis. XQ0041 was quickly locked, pointed, and destroyed. Sakein even got to get some credit for lobbing a few missiles in the ambush. I am happy for the changes CCP has made to the plex gate proximity. Although I have not fallen victim to this strategy too much, it is annoying.

The story on this is not closed though, there will be revenge!

XQ0042 Kill Mail

Dramiels are just death for this Tristan. Again, XQ0042 was defending, and just could not go the distance. However, when I scanned this Dramiel was about to enter the plex, I began to pull away from the plex entirely. Porphyrios Malchos had to steam forward quite a distance to catch me, while I was quick to set drones on him. By the time he closed the distance, my drones were well into his armor as I established point on him. He had just inches of internal structure left on him when he finally blew me up. Although this strategy and his determination made this an interesting fight, it just establishes further how dominant Dramiels are against my poor little ship. Porphyrious Malchos was a great sport about this as well, and donated 10 million ISK to me for my effort. Hey, every bit helps, and I appreciate the gesture!

XQ0043 Kill Mail

XQ0043 was defending a plex when six “brave” pilots attacked the mighty Tristan. I forget which ship it was, (although I seem to remember the Merlin), but I was focusing my attention on one in hopes of getting a kill out of the gank. The only joy I was able to get from this endeavor was the fact that they had to hurry and finish me, before one of their pilots lost a ship. I deprived three of them from getting in on the kill. I will glean such a victory condition from a one sided fight as this.

XQ0044 Kill Mail

Pretty straight forward fight here. XQ0044 defended the plex when Teo Enat in his Federation Navy Comet came in, closed distance, and melted me down.

XQ0045 Kill Mail

In contrast to XQ0044, XQ0045 began to pull distance away from the plex as Lufax was scanned at the entrance of the plex. Similar to the strategy I employed with the last Dramiel, I depended on Lufax’s determination to kill me to commit to closing the distance. Meanwhile, my drones spent the time clobbering at him. Overall, I was happy with the way I managed my speed and distance, but the extended fight depended too much on such details. In the end I blew it, and he was able to close distance to blow me up.

XQ0046 Kill Mail

There must have been a Federation Navy Comet fire sale during that time. XQ0046 was defending a plex. Ultimately I was just too conservative with my Microwardrive. Too slow, and made it easy for him to catch up to me. One interesting note here about ZKillboard, later Judge Sarn shows up on my Kill Board. The damage I applied to Judge Sarn, (apparently never completely repaired after our fight), allowed me to be tagged on to Nuke Cave’s kill mail. Unfortunately this takes away from what I am sure was a solo fight. However, this helps me to understand that the stats prevented on ZKillboard are not perfect.

XQ0047 Kill Mail

XQ0047 was defending a plex when Reiner Hass in his Incursus attacked. This turned out to be a long, long fight. Reiner Hass could not close the distance on me right away, and began to work on my drones as he continued to get to me. This began the drone dance that I have become comfortable with, removing and deploying as each begin to take damage. Unfortunately the details that go into this take a toll on my attention. However, I have to say in this fight I was up to the task. As modules burned out from both ships and drones finally fall after many drips in and out of the drone bay, Reiner Hass finally closed enough distance to finish me off.

XQ0048 Kill Mail

XQ0048 went on the attack, but ended up chasing off an LP farmer. I began to pull some distance form the plex entry point to think about my next move when I scanned this Worm at the gate. Pretty straight forward fight from here on out, as the Worm just has too much power over the Tristan.

XQ0049 Kill Mail

XQ0049 attacked this plex with Fat Zero’s Federation Navy Comet defending. I was still attempting to engage my Microwarpdrive for one burst – hoping to pass through far enough past his scram. No luck.

XQ0050 Kill Mail

Seeing this was my 50th ship in the challenge and my interest/frustration with attempting to attack plexes, I changed my fit up to a brawler. I needed a little change as well. I was beginning to feel comfortable with the kite fit, and felt I could manage more modules. Additionally, my ZKillboard was just so full of the previous fit, I started to feel some pilots were beginning to prep specifically for my engagements – or at least they would be able to.

XQ0050 was able to gain a kill before meeting this end, (and the kill was sweeter as it was revenge). However, this kill mail demonstrates the need to experience more fits. Hilary Clinton Ongrard met me outside of a plex. I was able to experience the Coercer’s massive dps in this fight. So intimidating in fact, I went full stupid – I did not turn on my armor rep during the fight. Again, I need to get used to managing other modules and other fits.

The end to my 50th ship is probably a good place to stop this long post. Although some details may have been lost over time, I hope it enjoyable to read over.

Part 2 coming soon.

A New Personal Best, but Still so Much to Learn

As work dragged on toward holiday break, (in the process almost breaking me), I was able to squeeze in a few hours here and there to play. The night began with me setting course to a highly contested system. A few jumps into my trek, I decided to just defend a complex, and see what fate brought me.

Ha te later entered system, and he seemed to want to play. He slid into my complex at just over 30km from me. I clicked my orbit button, and quickly followed up with a desire to slap myself. At that moment I realized my orbit button will simply direct my ship straight toward this Incursus. Once the auto distance program detected that my desired distance had been reached, my ship would bank away to begin orbit. While my ship is banking, my velocity would slow as Ha te could continue to steam ahead, and close the distance more. Maybe even enough for him to pin me down with his warp scrambler.

I quickly work the camera view on my combat grid to position my view to center my ship with the incoming Incursus. I double click off to the right to create more of an angle to my approach, and repeat this a few times until I close enough distance to begin to orbit. I had my micro warp drive overheating this entire time. Once I settled into a orbit, and shut down my micro warp drive to see how this speed versus the Incursus’ speed treats our distance separation. Meanwhile, my drones were going to work on him.

My frustration chatter

Ha te banks away during one of my off warp drive cycles, and warps off before I have the chance to overheat my warp disruptor in order to extend the range. My reaction in local reflects my disappointment. I mean, come on! I only have a limited time to play, and after all he attacked me.

As I finish my local chatter, I notice my Medium Shield Extender II has burned out. I am a bit confused on how that happened, but take the opportunity to dock up for repairs.

Quickly, I pay the repair bill, and head back to the novice complex. Hey, what do you know, Ha te is waiting for me at the gate! Considering I was landing right on his position, I decided it is my turn to scoot out. I wait for the warp engines to shut down, then immediately slide into the complex. As soon as I land out of warp in the complex, I hit my micro warp drive. I was not concerned about establishing an orbit or anything, I just wanted to pull some distance. As Ha te flew in right behind me, he was able to lock and warp scramble me for just a moment. Fortunately my velocity was already high enough to coast me past his scramble range. I establish a nice orbit of 20km around him to watch my drones go to work.

This time I am attempting to be more aware of our distance, since I did not want him escaping again. While I go through this mental check list during combat, I discovered something unfortunate. Here’s a not-so-pro-tip for any would be PvPers out there: when you repair a module that has been burned out, you must online the module before you undock. Imagine my shock as I learn that most of my shield strength is not online. Well, all the better that I was able to keep my distance.

19th kill

Double armor rep Incursus. Look at the damage I needed to apply – over 8000!!! Nice fit.

I felt that I was making too many errors, since I was tired. Considering my shield status, I just scooped up the loot, and docked up for the night. I was not even up for completing the defense of the complex.

The next night, I log in to see a flashy in local. I undock and see a Coercer on d-scan. My first reaction is intimidation. I have identified the complex he was attacking, but I never fought a destroyer, and destroyers have so much more dps than a frigate. Keeping to the tenants of my challenge, (to take on all fights), I set course, and slide into the complex. Pablo Emirio is waiting for me, as I jumped in too close to him for my comfort. As I slow down out of warp, I just begin to click on my micro warp drive. My plan is to get at least a cycle to run in order to increase my velocity and pull some distance – in case he has a warp scrambler fitted. As I fly into my 20km range and deploy drones, I see that he has a disruptor – that’s good for me!

My Tristan orbits him from a nice distance, as his pulse lasers fire away ineffectively. The Coercer goes boom, and I am amazed! I “gf” Pablo in local, but he is silent. This is, to date, my largest FW kill.

20th kill

Not much action after that. Seems the night started on a high, but whimpered out. I was not able to log in for a few nights. Work was just awful.

Saturday night, and I am free to roam. I set course for a contested system, and head out to look for mischief. Oh look, an LP bot.

21st kill

With these kills, there really is not much to write about, other than identifying a kill. This one, however, was a little funny. There were actually two bots in system. Bino Koraka here was at the gate leading to the novice complex, which was already occupied by the other LP bot. He did not attempt to fly away, nor use the jump gate to slide into the complex. I get the impression his program was stuck, “Caldari Atron in complex… I’m a Caldari Atron… does not compute…” Fortunately I come in to put him out of his misery. I did not pod him, and his pod stayed there for such a long time. The pod’s inactivity is what convinced me the program was stuck.

The little sucker that was in there was able to fly out as I came in. Oh well. I defended the complex, dumped off the loot I collected, and continued along the set course.

Frarie had a few LP bots in system. I chased them off, and decided to sit in and defend a complex. The system had a decent contested percentage. HUNZY 0511 and Arien Licinius jump into system. I see that they belong to the same alliance, and since one of them is in Stay Frosty I know this will be a fight if they are in a ship that will fit in this complex. I just hoped it was only one that would be able to take me on.

HUNZY slides into my complex in his Tristan. His distance was a little further than my comfortable orbit, so I manually move toward him, maximizing transversal, before settling into an orbit. Within this time I order my drones to pound away on him. I click on my “drone” overview tab, but no drones are present. Strange. I watch his shields melt, and significant damage applied to his armor. About the time I see that he is active armor tanked, I see Hobgoblins deployed. I decide not to work on his drones when I see they are tech I, but I commit to myself to monitor the situation. If he started to attack my drones, his will die.

Soon after this as HUNZY and I are dancing and working well into his armor, Arien slides into my complex in his Incursus. HUNZY and I have made our way out a little ways beyond the complex, so Arien has some distance to fly to catch up. This gives my drones enough time to make the enemy Tristan go boom!

22nd kill

I spend a moment or two sorting things out. I had HUNZY’s drones targeted in preparation for my change in plan, and I thought I had the Incursus targeted as well. I was wrong. Although I was monitoring Arien’s distance, I targeted him – again, and manually piloted into position to orbit at 20km. Again, drones going to work on the Incursus. He too was active armor tanked. His blasters were ineffective at my distance. HUNZY hung out in his pod watching his wing man get whittled away until he finally went boom as well.

23rd kill

We all exchange “gf” in local. I was very happy, and just stunned if I’m honest. As soon as I saw the Incursus land, I could have sworn that was the end to XQ0018. I scooped up the loot from both wrecks, and dock to repair and drop off the cargo. I also take a screen shot of the kills marks, since XQ0018 is now the record holder.

6 kill marks – sweet!

It is always tempting to put ships like this away for a bit, to try and build up these marks, but that leads to sloppy play style. Take a picture, and move on. I finish defending the complex, and decide to take my loot back to my home station to continue my profit effort.

After I take care of some in game house keeping, I am feeling pretty good about myself, and decide to continue to roam effort. I noticed too many LP bots in systems as I passed through to my home station, so I set off to do a little policing.

Agoze is fairly busy with pilots, but I manage to nail an LP bot.

24th kill

As I scoop up the loot from this Atron, I pick up two ships on short d-scan: a Tristan and an Imperial Navy Slicer. I set orbit distance around the button, as I see that these two pilots are sitting out at the gate. Obviously they are coordinating their efforts to gang up on me. Both ships slide into my complex at a distance to my advantage. I decide to primary the Slicer. I know that this Slicer is the ship that will push my distance requirements to the limit, and if I have any chance at winning it may be as a result of out pacing/distancing the Tristan as we battle it out. I also know that the Tristan’s drones will be an issue. Essentially there is going to be just too many targets on the field against me.

The fight does not go on too long. Maybe longer than my opponents expected. My drones were able to work into the Slicer’s armor throughout the fight, but he was active armor tanked. He had to rep constantly throughout the entire battle. To my surprise the Tristan’s drones were not much of a factor. The Slicer was the threat, as I speculated.

No response from them in local after the fight. I will have to keep an eye out for their corporation and alliance. My brief research into each of these pilots confirms my impression of them, they are gang pilots. Not too many, if any, solo kills cataloged by them.

Anyway, for the record, XQ0018 holds the record at 7 kill marks! Obviously I was not able to capture this fact with a screen shot, but that does not diminish the accomplishment. This was a great streak.

Record: 82 ships ready to explode: 24 kills recorded.