Saturday, November 10, 2018

Highsec Miner Grab Bag #170


Either LoNeNg wants our Agent to die in-game, or he's practicing his German. Welcome to yet another thrilling edition of the Highsec Miner Grab Bag!


How do so many carebears end up finding this "phantom" provision of the Code that requires an Agent to send them a warning before ganking? And why do they always miss the actual provision about buying a mining permit? Mysterious.


Miner, taking a blingy loss doesn't earn you a permit. There is a bright side, though: Our Agents enjoy juicy killmails.


Keep up the good work... dog.


The rule of thumb is, if you're not sure whether you're in New Order territory, behave as though you're in New Order territory.


Poor grammar, or just Russian? The )) gives it away every time.


The mighty CODE. alliance has destroyed over a quarter million ships already, so destroying a thousand from a single person is not outside the realm of possibility. In fact, maybe it already happened in a Bonus Round or something.


When an EVE player experiences a "Eureka!" moment, it's invariably followed by a permit purchase.


It's the truth. I hope there are still people at CCP who understand that PvP keeps people interested in their PvP game.


Sounds like another retained player. Let's up the ante a bit:


Where can the "ganking is bullying" crowd go to feel safe, when you can see a conversation like this in the Anti-Ganking channel?


The CODE always wins.

Foreva and always!

3 comments:

  1. The mind boggles... BOGGLES... if there is enough backlog of tears that James is even now rolling out stuff from a year ago.

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

    ReplyDelete
    Replies
    1. I still think it would be good if James put an antiganker status tracker on the page. That way we can get real-time updates on whether or not they are failing and get an estimated time they are expected to stop failing.

      Delete

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