Slack-Eve-Killmail

Requirements

• Slack
• Python 2

Install Instructions

• In Slack, go to /services/new, select Incoming WebHooks.
  • Fill in channel/name
  • Copy URL in config.py in the config_slack_url
• In config.py configure which alliances to track
  • Format is dictionary in array
  • Each dictionary in the array is a separate corporation or alliance to track
  • Key is allianceID or corporationID
  • Value is the ID
    • Go to zkillboard
    • Search your corp/alliance
    • ID is in URL behind /corporation/ or /alliance/
• If you haven't already, bind corporation API key to zkillboard to get all kills listed
• If on ubuntu, copy or symlink scripts/ubuntu.init to /etc/init.d/kbbot and run update-rc.d kbbot defaults (also make sure the killboard.py and other files are located in/around /opt/Slack-Eve-Killmail/killboard.py)

Configurable fields

• config_header = 'Slack-Eve-Killboard/1.0a https://github.com/dimurgos/Slack-Eve-Killmail' # header
• config_owner = [{'': 0}] # Format of: 'corporationID': or 'allianceID': (can be multiple)
• config_check = '86400' # Check for the last day (maximal retrieval amount)
• config_sleep_time = 1200 # Delay between checks (20 minutes default)
• config_slack_url = 'https://hooks.slack.com/services/' # Slack integration code
• config_locale = 'en_US' # The locale to post ISK values in
• config_run_as_daemon = False # Tries to run as daemon instead of keeping the application alive
• config_show_participating = False # True shows the top 10 participating pilots on the kills that are part of your corporation or alliance (default to False), see example below.
• config_extended_name = False # If True, shows (corporationName) on both victim and attacker
• config_discord = False # If True, properly posts for discord (also requires the slack_url to be a discord url ending with /slack)

Result

• Every 20 minutes the list of kills over the last day will be posted in the configured Slack channel
• Posts if it is a loss or a kill (green for kill, red for loss)
• Includes damage dealt, pilots involved, ship, value, system and most damage done

Example config_show_participating = False

Example config_show_participating = True

Example config_extended_name = True

Solutions for possible issues

• 'locale.Error'
  • If this happens, check your locales if the current configured value is supported. Some possible values have been added as suggestions.
• 'IOError'
  • Usually relates to missing database file 'handled_kills.dat', create if not available.
• Exception in processing record: '(corp id)'
  • Check if config_owner is configured like follows:
    • config_owner = [{'corporationID': (corp id)}]