There's a reason he's the only one to ever be IP banned from perp-kill.

As an outsider who doesn't play, rest assured, each and every one of you is a ***.

Posted some fixes today.

• Navigation for changing months is back.

• Agent and Corp historical kill and loss pagination is fixed.

• Pagination across the entire site sized to better accommodate different screen resolutions.

• Related Kills is back to the old format that breaks participants down into corp blocks.

Sorry everyone, I was called out of country on business this past week at the last minute. I'll try to get changes in this week.

Yeah, I'll probably just switch it to neutral designations. Right now "good" and "bad" are calculated from the perspective of the kill you were viewing.

I haven't forgotten about fixing this page or the other features, I'm just very busy at work this week.

No u.

Everyone calm down. I updated to Bootstrap 3. If you think it's all sized too big, take it up with Twitter. I'll get a dark theme up soon.

Hey DEV Gargaj,

Does every kill have a final blow flag set? I'm seeing some mails where the killer does zero damage, is the only attacker on the mail, but isn't flagged as the final blow. For example:

http://www.perp-kill.net/kill/256734

Just trying to figure out if that's a bug in my API parser, or if I need to change the logic.

Edit - Here's what you're sending:

    <kill>
      <id>39433132423539432d453036462d344441302d423936362d384431354144373934463743</id>
      <date>2215-04-16 01:45:49</date>
      <zone>Novastrov</zone>
      <victim>
        <name>Burial</name>
        <corporation>StateCorp</corporation>
        <robot>Cameleon Mk2</robot>
        <position>
          <x>1519</x>
          <y>881</y>
          <z>152</z>
        </position>
      </victim>
      <attackers>
        <attacker>
          <name>Zombie Hamster</name>
          <corporation>Pretty Hate Machine</corporation>
          <robot>Castel Mk2</robot>
          <damage>0</damage>
          <position>
            <x>1474</x>
            <y>808</y>
            <z>221</z>
          </position>
          <jammer>0</jammer>
          <jammerTotal>0</jammerTotal>
          <demobilizer>11</demobilizer>
          <suppressor>0</suppressor>
          <dispersion>0</dispersion>
        </attacker>
        <attacker>
          <name>Diaper Gravy</name>
          <corporation>Crimson Imperium Reborn</corporation>
          <robot>Troiar Mk2</robot>
          <damage>0</damage>
          <position>
            <x>1635</x>
            <y>692</y>
            <z>174</z>
          </position>
          <jammer>0</jammer>
          <jammerTotal>0</jammerTotal>
          <demobilizer>0</demobilizer>
          <suppressor>0</suppressor>
          <dispersion>260.600006104</dispersion>
        </attacker>
      </attackers>
    </kill>

Yes, which is why this discussion hinges on the implementation of OAuth2 in the API. If added, I would be able to verify the person attempting to post as "Mitix" is in fact the owner of the "Mitix" account. Once that is possible, anonymous posting could be removed.

Taking it a step further, I would be able to store preferences for each of your user accounts on perp-kill allowing you to block individual users. So if "Mitix" posts nothing but racist, homophobic, ethnic slurs you could hide his comments globally on the site.

Long story short, I'm not going to remove, disable, or limit comments simply because there are a handful of immature posters. There are better solutions that don't ruin the fun for everyone.

I have very limited experience with OAuth2, but this sounds wonderful.

Yes, the related kills section can be improved. It's on the list.

Not sure if troll.