Broken Toys: The Failure of the ‘Fixed’ Logoffski Mechanic
A few weeks ago, my friend Qu1ckkkk, author of the blog Don’t Shoot! X (oddly, not to be confused with the equally good read dontshootx.blogspot.com, home of Aperture Harmonics) wrote a post about his recent adventures in Ninja-baiting and killing mission runners. The stories were amusing, if not standard, until I got to a particular one that made me double-take.
In it, Qu1ckkkk describes a run-in with an extra-shooty mission runner in a Tengu. After having some missiles flung his way in anger, and after swapping for his pew ship, Qu1ckkkk soon realized that he didn’t have the firepower necessary to break the Tengu’s most-likely faction shield boosting. Not taking any damage himself though, Qu1ckkkk maintained point and web on the Tengu and got into a nice orbit to await help that was bringing him bigger firepower to swap into.
At this point, the Tengu pilot logged off. Qu1ckkkk however, continued to fire off a shot every few minutes in order to make sure he kept the timer going while waiting for help. But here’s where things get totally and completely broken: 15 minutes after the Tengu pilot logged off, he was very abruptly no longer red to Qu1ckkkk, despite still being pointed by him.
A petition was filed and amazingly enough, a GM actually arrived on the scene within minutes to investigate. Qu1ckkkk opted to not post the GM chat-log on his blog (like a good little EULA-abiding citizen), but surmised it pretty nicely:
Long story short, there was nothing he could do about the problem. I had him pointed and webbed, but I am not able to shoot at him without getting concorded. It seems like they are unable to make someone red again to the other without logging into that person’s account (which they also can’t do). They also don’t have the “tools” to fix the aggro. Only people who are logged in are to have their aggro tampered with.
He stopped being red to me after 15min WHILE I have him aggressed. So much for the logoffski nerf. Lucky for the tengu pilot, the best thing he could have done was to NOT log back in.
Objectively, you could look this over pretty quickly and dismiss it as bad luck. And the truth is, yes, this time it was a tricked carebear in what was probably a standard mission fit Tengu; shit happens and you lose kills sometimes, and in the grand scheme of Eve, a griefer losing a highsec mission runner kill due to odd-ball bugs doesn’t make much of a ripple. But say the next time this particular glitch happens, its on a low-sec station, and suddenly an entire offensive fleet finds themselves without aggro on the logged-out SuperCap pilot they’ve got pointed; in that scenario, you can bet this will be a MUCH bigger issue. Have a whole fleet go GCC* near station or gate guns because of a logoffski SuperCap pilot, and mark my words, the torches and pitchforks will come out.
Again, despite my niche in Eve, I get that Qu1ckkkk not getting an easy kill on a foolish mission runner won’t keep many people up at night, but lets distill it down into something broader and see if it raises any eyebrows:
Post-Crucible, a pilot in Eve was able to avoid destruction of his aggressed ship by logging out of the game.
…sound broken yet?
*GamerChick24 actually wrote about something similar a little while ago involving Faction War and POCOs here, which was actually addressed by CCP.
Image via Instructables.com