Saturday, April 7, 2018

The Medal of Honour, Part 1

How do you know if a corporation harbors Code violators--or worse, actively encourages its members to adopt a bot-aspirant culture?


There were a number of red flags in R.S.INDUSTRY's corp description. There was a less than 100% chance that it was a Code-abiding corporation, and that made it worth investigating.


Dayjha Cuervo slowly made her way from system to system in a freighter. Her slow speed marked her as an AFK autopiloter. Though Levivity was new to R.S.INDUSTRY and eager to make a good impression, she couldn't let her corpmate get away with a crime this big. She took advantage of the corp's friendly fire setting and ganked the freighter with her Proteus.


When Levivity inspected the freighter's cargo, she was horrified to discover unlicensed ice-mining equipment inside. She raced back to the Finanar system, where a corp mining op was ongoing. As Levivity feared, none of the miners had permits. Her Proteus opened fire.


Though ten minutes had passed since the freighter gank, the freighter pilot hadn't warned anyone that an elite PvP'er had joined the corp. Obviously, she was still AFK. Levivity was therefore able to kill two of the corp's ice miners before the rest of the corp docked up in a panic.


Levivity's acts of violence were committed in the name of the Code. She was an Agent of the New Order.


One of the ice miners, DJVande, trotted out some tired old excuses for why he didn't own a permit. In the course of doing so, he inadvertently admitted that he was aware of the Code. Oops!


The Smitty was the other ice miner iced by Levivity. Hoping to avoid DJVande's mistake, he feigned ignorance of the most famous organization in highsec.


Levivity's suspicions about R.S.INDUSTRY were correct: Code enforcers were not welcome there. She would be kicked out at the earliest opportunity. Until then, corp chat would be lively.


Slowly but surely, other members of the corp got up to speed about "the Levivity situation".


Just then, the freighter pilot returned to her keyboard. Now that she knew Levivity was an undercover operative for the New Order, everything started to make sense. That's why the day-one recruit had been asking about freighters!


The Smitty was burning with rage. Fire danced in his imagination. Would his foolishness shock his fellow corpmates into calming down?


If anything, it seemed that the carebears were feeding upon each other's rage. The corporation was in an uproar over the Agent in their midst. Could Levivity calm them all down and persuade them to embrace the Code?

To be continued...

5 comments:

  1. "There was a less than 100% chance that it was a Code-abiding corporation". Lol, much less than 100%.

    The alliance name was close. Savages.



    Holy shit I just found my new meta: join carebear corps that have friendly fire illegal, then scam my way into roles that allow me to set it legal. Then bring the Code to the barbarians.

    That's what I love about EVE, just when you get bored something like this blog can shine a new light on something as simple as a good 'ol safari can take on a new allure.

    Hey, all you carebears! Anyone who applies to your corp after you read this may possibly be me. And the kicker is; if you do deny me entry or roles it will only make me try harder to infiltrate you, with new alts and old friends. Something something catch 22...

    Sux to be a carebear CEO.

    Always!

    ReplyDelete
  2. Wow just wow. If only thomas wasnt stealing isk from the antiganking donations and using it to help people who lose there ships antiganking. Such a shame!

    ReplyDelete
  3. Nice to see a good old fashioned safari in this day and age. If the corp CEO didn't want his members to shoot each other why did he enable 'friendly' fire? Might be a story behind that....

    ReplyDelete
  4. The points you have mentioned in this article are useful.

    ReplyDelete
  5. It is great that you share with us such information, for me such things are very helpful.

    ReplyDelete

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