aa-killtracker

What it is and what it does

Killtracker is a Django plugin for Alliance Auth that monitors Eve Online killmails from zKillboard and automatically posts matching kills to Discord channels. It lets you define trackers with 20+ conditions—such as location (jumps or light-years from a staging system), ship types, attacker counts, security status, and alliance/corporation membership—to filter which killmails appear in your Discord channels. Conditions combine with AND logic, so you can layer requirements and exclusions to cut through noise and see only the activity you care about.

The package is designed for fast response times and low resource overhead. It integrates with Alliance Auth's authentication system, Discord webhooks, and Eve Online's ESI API via django-eveuniverse. Setup involves installing the package, configuring a Celery beat task to run every 60 seconds, loading Eve Universe map data, and creating trackers through the admin interface. It supports Django 4.2 and 5.2, requires Python 3.10 or later, and uses a task queue (redis-simple-mq) to handle the volume of killmail processing.

Use it for:

• Monitor roaming groups in your region by tracking kills with 20+ attackers within 10 jumps of your staging system
• Alert your alliance when capital ships are destroyed within your jump range by filtering for capital-class losses
• Track war targets or specific enemy alliances to see their activity in real time without manual zKillboard checks
• Exclude high-security space and NPC kills to focus only on player-versus-player activity in your area of interest
• Set up separate trackers for your alliance's kills and losses to monitor both offensive and defensive activity

Worth the install?

AI-flagged interpretation of the facts on this page — verify before relying

Killtracker is an Alliance Auth plugin that automatically filters and posts Eve Online killmails to Discord channels based on customizable conditions like location, ship type, and attacker count.

Yes, with conditions. The package is actively maintained, has low install friction, and solves a real problem for Eve Online alliance operations. However, install only if you are already running Alliance Auth and can commit to a Celery worker setup. Verify the license before production use, as it is not declared in the package metadata. No known security vulnerabilities.

Install

aa-killtracker on PyPI

pip install aa-killtracker

uv add aa-killtracker

poetry add aa-killtracker

Installing aa-killtracker

Before you install

Low install friction with a pure-Python wheel. Requires seven runtime dependencies including allianceauth, django-esi, and redis-simple-mq. Active maintenance with a recent release (20 days old) and no archived status signals ongoing support.

License in practice

License treatment is unclear—no SPDX identifier or raw license text is available in the package metadata. Verify the actual license before deploying in a production or commercial context.

Quickstart

pip install aa-killtracker

# In your Alliance Auth settings (local.py):
INSTALLED_APPS += ['killtracker']

CELERYBEAT_SCHEDULE['killtracker_run_killtracker'] = {
    'task': 'killtracker.tasks.run_killtracker',
    'schedule': 60,
}

# Then run:
python manage.py migrate
python manage.py eveuniverse_load_data map
python manage.py killtracker_load_eve

Requires an existing Alliance Auth installation, a Celery worker configured with threads-based concurrency, and a Discord webhook URL for each tracker.

Verify before relying

• Whether the package has an explicit open-source license published in its repository or documentation
• Performance characteristics under high killmail volume or with many concurrent trackers
• Whether celery worker configuration is strictly required or merely recommended for optimal performance

Package facts

Evidence: aa_killtracker-2.0.2-py3-none-any.whl

Tags

More WWW/HTTP packages