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.
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.
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.
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.
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!
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.
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.
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.
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.