Tuesday, July 17, 2018

The Bot's Greatest Enemy

EVE's playerbase has long been dissatisfied with CCP's anti-botting efforts. Specifically, players are concerned that CCP doesn't do anything. Some have even gone so far as to suggest that CCP welcomes the bots, since they boost subscription and logged-in player numbers, and because they inflate PLEX prices. CCP may tolerate bots, but we do not.


Kill the bot-aspirants, and you'll find the botters. It began with Agent Super Perforator's gank of a fail-fit Retriever piloted by Kocokacia Podiene.


Incredibly, Kocokacia had the gall to display a mining permit in his bio.


Things escalated when Kocokacia's mining partner, Mining Amatin, was ganked next to him. Mining Amatin was a repeat offender. And he had a permit, too.
Super Perforator > Kill: Kocokacia Podiene (Retriever) Kill: Mining Amatin (Retriever) two retrievers sitting on top of one another.
Ralliana > mmm..both with sweet permits
Super Perforator > sweet and invalid. :(
lady aspin > invalid ?
Super Perforator > yes
Super Perforator > check the fittings.
The chat above didn't come from local; it was from the MinerBumping channel. Yes, today we're going to take you inside New Order HQ.


After the Kocokacia incident, our heroes investigated the alleged permit-owning miners. They strongly suspected Kocokacia and his friends of operating a botting ring in the Otela system. By July 10th, they were ready to make a second strike.
Slutzilla > Kill: Kocokacia Podiene (Retriever) repeat offender with fake permit (got revoked a couple of days ago)
Slutzilla > just noticed I was flying a t1 cat.... got lucky.
Slutzilla > Kill: Vinger Nardieu (Retriever) and the bot fleet in otela keeps warping their pods out to the belts......
The next miner to be targeted, Vinger Nardieu, provided additional evidence of botting. As with so many other botting operations, the pods didn't quite know what to do once they were removed from their Retriever husks.
Haul Melkan > How many they got out there?
Slutzilla > they note the names of gankers....
Slutzilla > we'll send the list to you later! :)
Slutzilla > then you can get them after we are finished / blown! :)
D34dly D34dly > I'm already banned :( They dock up as soon as I enter the system
In addition, these particular bots ran a program where the user could add the names of known gankers and dock up immediately upon detecting them in local. Luckily, the New Order has an abundance of gankers at its command. Some, like Agent Slutzilla, had not yet been added to the list.
Slutzilla > i did one with a T1 cat.... only just.
Slutzilla > last shot
Jarmin Penken > I'm suprised you managed that
Slutzilla > it was an accident... i misnamed it when fitting.... it was supposed to be a t2 scram fit.
Axel Slotermeyer > Kill: Mining Amatin (Retriever) I didn't get the pod despite a t2. They are programmed to warp out immediately I think
Even when mistakes occur, the power of the Code gives our Agents an insuperable advantage.
Benzodiazepine > What's with the permit
Slutzilla > the permits were revoked
Slutzilla > they just display them still.
Slutzilla > watch the pods come in... they wait like 25secs and warp out again
Given the undeniable supremacy of the Code, I suppose we shouldn't be surprised to see botters buying permits--or at least making counterfeit ones. The Otela ring's permits only ensured their destruction, however.
Jarmin Penken > How longs it take the ret to come back?
Slutzilla > Jarmin Penken it seems like a while... different
Slutzilla > we havent really timed the pods yet.
Jarmin Penken > Some pod as turned up
Jarmin Penken > Mining Amatin
The Retrievers had fallen. Now our Agents were eager to snatch all the pods that were zipping back and forth across the system.


Success! Kocokacia's pod had gone haywire after it left the Retriever. For over an hour, it warped around Otela according to its programmed routines. Finally, it was laid to rest.


Two other bots had their pods ambushed in the same way, long after their mining ships were destroyed.
Slutzilla > Kill: Kocokacia Podiene (Capsule) bot pod down.... nice!
Axel Slotermeyer > Kill: Mining Amatin (Capsule) next bot pod with invalid permit
Slutzilla > Kill: Vinger Yuri (Capsule) Another bot pod..... looks familiar.
Slutzilla > looks like we cleand that bot fleet out of local....
Haul Melkan > They'll be back
Slutzilla > well yes, but they will probably dock up when we enter system.
Eventually, the bots were cleared out of Otela. They were expected to return, but something interesting happened.


Notice something missing? Kocokacia deleted his bio. He actually complied with our Agent's demand that he remove his revoked permit.


In fact, all of the bots identified in the Otela ring erased their mining permits. And, it seems, they chose to relocate.


It's a fine thing to gank a bot. Even finer: Driving the bots out of highsec entirely. This report is further proof that that although everyone complains about bots, only one organization in EVE is willing to take action against them. There's no doubt about it--we're the good guys.

12 comments:

  1. That name adding function is easy to defeat when you bump before you enter.

    Miners are not worth T2 cats.

    Flush them down the toilet with meta 1 and let the loot fairy pay for the gank.

    Shardani used meta 1 on his kid.

    ReplyDelete
    Replies
    1. Never forget that shitter or his shitter ag friends that identified with him, some of them still play today. He and thomasinchastity were best buds. Poor thomas, can't save shit.

      Literally! ahahahahahahhahaha


      Always!

      Delete
  2. So...

    Fraternity is where bots go after gankers punish them properly. Sure, why not, should be easy to infiltrate.

    ReplyDelete
  3. wow just wow. antigankers are failing so hard right now - non-stop daily continuously ALL the time

    ReplyDelete
    Replies
    1. Why would any anti ganker stop people from killing bots?

      Delete
  4. Meh seems made up

    ReplyDelete
  5. "CCP may tolerate bots, but we only tolerate OUR bots/alts."

    FTFY, Jamey.

    ReplyDelete

Note: If you are unable to post a comment, try enabling the "allow third-party cookies" option on your browser.