zKillboard is an amazing site that I enjoy browsing from time to time. Every now and then I want to drill down into some specific data further and I always struggle to remember the URL-fu that zKillboard allows. Forget no more, I thought I’d dig in and find as much as I could and document it for next time.

I gathered this from looking at the source code of zKillboard, and trying out some things on the site. One day, when I have some time, I’d love to get the site running locally and have a dig into the database and how queries are constructed to get a better understanding of how it hangs together, if anything here is wrong, or there is more, let me know.

Standalone URLs

Lets get some base standalone URLs out of the way first

That gives you a few quick URLs that might be of interest, and those are also available via the Menu dropdown in zKillboard, so no needing to remember them.

URL Segments

Now lets take a look at the base URL segments zKillboard accepts. These are also stackable, more will be explained on this later:

Each one of those will help you drill down a bit into the enormous dataset of zKillboard. Taking them further, those are also stackable, putting them together can help you drill down even further. The first segment in the URL is what the pages display will use. So if the base is something not player driven, like a system, region, constellation or location, there are only kills, no losses. If the first segment is a character, any kill that player is involved in is a kill, and when they died, that is a loss. You get the picture.

Examples fo stacking segments

Segment Modifiers

With an understanding of the above segments, lets look at modifiers. These modifiers can go on any of the above segments.

There are also a few modifiers that only work on limited segments.

The reset/ modifier

reset/ is an interesting one, usually each new segment you add filters the data more, so if you looked for /alliance/%allianceID%/corporation/%corporationID%/ it would find a victim who was in allianceID AND corporationID, or an attacker who was in allianceID AND corporationID.

If you’d like to find a victim from allianceID and an attacker from corporationID, or vice versa, you can use /reset/. It acts like an ‘involved’ rather than an ‘and’ between segments.

Understanding reset/ full would require I get this running locally to see how it forms the query, from what I can tell, you can’t use the same segment type on either side, unfortunatly, so comparing 2 alliances doesn’t work, comparing 2 characters doesn’t work.

Hope that gave you some insights into how to better use zKillboard, if you know any more, or find anything wrong, please leave a comment below.