From this page a list of the synchronized killmails is displayed. They are sorted by the time when the kill was performed. You can hide/show/delete each kill, you can also reach the killmail report if you need it. Each kill displays: Victim, Date, List of the attackers, Value of the kill. From time to time, might happen that kill(s) you sync do not have a price/quotation. This may happen because plugin fails to retrieve an official price for an item during the price sync ( or an official price might also be missing at that time ). You can identify the killmail that requires an evaluation by the word "Pending" in the "Value" column. The interface will help you with the process, showing some tools to complete the kill estimation:

• Calculate costs : this button will trigger the process to calculate the missing estimations. Process is automated, once complete will update kills that require an estimation
• Missing price: this selector will show ( if required ) a list of items that doesn't have an official price or cannot be evaluated at that time. Simply search the price from the market ( or wherever you prefer ) and insert it into the input field and then save. This price will be considered the updated value for that item, until a new price will come up from the next sync

From this page you can setup the ESI synchronization :

• Corporation Id : your corporation ID. PLEASE BE CAREFUL to insert the correct one or the killmail import ( both manual or auto ) will fail if that doesn't match with the correct one.
• ONLY WITH ESI APPLICATION ENABLED AND SYNC :
  • Client Id : ESI Application ID, is specific for your application. Retrieve it from the ESI Application admin panel. DO NOT SHARE THIS DATA
  • Client Secret : ESI Application Secret, is specific for your application. Retrieve it from the ESI Application admin panel. DO NOT SHARE THIS DATA
  • OAuth version : You can choose which version of OAuth use. I recommend Version2. If you don't know what this mean, just leave version 2
  • Synchronization : this field set up the period of run of the cronjob offered by Wordpress ( WP-Cron ). This process can be run every hour, twice a day or once per day. We advise against the use of it, especially for heavy load platform. If you have direct access to system cron or external service go for it ( there are a lot on the web, some free )
  • Endpoints Name: URL name parameter, required in the call to reach the cronjob endpoints
  • Endpoints Secred: URL secret parameter, required in the call to reach the cronjob endpoints

On the very right side of the page you can see two sections

• Statistics : here will be listed the general stats of your Killboard. Numeric infos about number of capsulers, killmails, corporations and items stored by your platform
• Processing Logs: here will be shown process log ( notice, info or error ) during auto sycn of killmails and prices

From this page you can customize the look and feel of the public Killboard page:

• Killboard title : frontend page title of the Killboard
• Margin : container HTML margin value of the frontend killboard. You can specify any allowed value. Sample: 20px OR 0 10px 0 10px
• Padding : container HTML Padding value of the frontend killboard. You can specify any allowed value. Sample: 20px OR 0 10px 0 10px
• Elements per page : number of displayed element per page in the Admin AND frontend table
• Show kills: choose type of kills shown on the frontend killboard. You can choose between: All, Done ( kills done by corporates ), Suffered ( kills suffered by corporates )
• Font size : font size on the elements ( all ) in the HTML container frontend killboard page
• Image size : image size on the table rows for Capsuler, Alliance and Corporation images
• Custom image styles : CSS style input. Sample: display: inline;
• Custom button styles : CSS style input. Sample: padding: 6px;
• Table columns : allows to choose which columns you want to display on the frontend killboard page. At least one column must be active
• Inspect items : enable/disable kill inpsect items window on frontend killboard page
• Show last page only : if enabled, frontend killboard page will show only a page with the latest synchronized kills
• Display Developer Sign on Frontend : enable/disable the developer sign on the frontend killboard page ( Made with ♥ by jrmarco ), if you want to support me Colors section:
• Kills done -> background color : table rows background color of the kills your corporation perform. Field accept HTML color value ( textual or hexadecimal ). Sample : red OR #008000 OR cyan. You can have a preview moving out your focus from the field
• Kills done -> text color : same as previous settings, but related to text color
• Kills suffered -> background color : table rows background color of the kills your corporation suffered. Field accept HTML color value ( textual or hexadecimal ). Sample : red OR #008000 OR cyan. You can have a preview moving out your focus from the field
• Kills suffered -> text color : same as previous settings, but related to text color
• Header,table header and footer settings -> background color : background color of main frontend page header,table header and footer. Field accept HTML color value ( textual or hexadecimal ). Sample : red OR #008000 OR cyan. You can have a preview moving out your focus from the field
• Header,table header and footer settings -> text color : same as previous settings, but related to text color

From this page you can check and updated synchronized items:

• Each item has :name, current price, source of price and synchronized time
• It's possible to synchronized all the items price via the ESI endpoint
• It's possible to manually edit price of the item, double clicking on the price and insert new value

First of all, if you don't know what Killmails are, read this. Killmails can be synced manually or automatically via an ESI Application. We will now dive into the "How-To" on both scenario:

• Manually load killmail : killmail can be manually imported ( this can be done even if you enabled the ESI Application auto sync ). First of all a Corporation ID must be stored in the Admin Settings page. If you skip this step manual sync won't be possible. From the JRM Killboard :: Main page, use the top field called Killmail URL : paste the killmail link ( links have this format: https://esi.evetech.net/ (LATEST OR V1) /killmails/ KILL-ID / KILL-HASH / ) and click on the Load Kill button. Your kill will be loaded ( if not present ) and all the information fetched. If the kill items are missing or price is missing at that time, process will ask you to provide a price for it

• Auto Sync Killmail - ESI Application : killmails and price sync can be done automatically using the combination of an ESI Application and a Cronjob. The application and the cronjob are not direct part of the plugin, you need to provide them TO the plugin.

  • ESI Application: an ESI application must be requested and created from the Eve Developer website. To obtain one:
    • LogIn with your Eve Online account, go to Manage Application, Create New Application. Here you have to provide some info about your application :
      1. Name and Description : this are not relevant for the plugin. Put what you like
      2. Connection Type : AUTHENTICATION & API ACCESS . This settings allows the plugin to call the ESI endpoint whenever needs to fetch the killmails for you.
      3. Permissions : plugin requires only one -> esi-killmails.read_corporation_killmails.v1 . As description says "Allows reading of a corporation's kills and losses". With this permission plugin will be able to perform ONLY THIS ACTION. At the moment plugin doesn't need any other permission rather then esi-killmails.read_corporation_killmails.v1 .
      4. Callback url : this is the url used by the Developer LogIn API to forward you once the authentication is completed. Pay close attention to this field, callback url MUST BE the JRM Killboard plugin settings page. Sample: http OR https://YOUR-DOMAIN/wp-admin/admin.php?page=jrmevekillboard_settings . You can copy and paste it directly from your Wordpress installation admin menu link: right click and copy the link from the JRM Killboard -> Settings menu link.
      5. Create Application : your ESI Application is now ready to be used
  • Once you have an ESI Application, go to the JRM Killboard Admin Settings page and copy and paste the Client Id and Client Secret into the input fields and Save the configuration
  • Interface will now display the EVE SSO Authenticate button. This will forward you to the Eve Online Account LogIn, after login you will be asked to choose which capsuler you want to sync with this application and will show you the scope ( ESI Application permission ) required by the application you created before. Confirm and you will be redirected back to the Wordpress JRM Killboard Settings page, with the ESI Application details updated. Congratulations you are now ready to sync your killboard!
  • At any moment you can suspent the ESI Application authentication/link using the Remove button, placed next to the ESI Sync status. PLEASE NOTICE: this action won't revoke the ESI Application token, you will have to do it directly from your Eve Online account settings
  • You can now set up a Cronjob ( System Cronjob, External Cronjob ) that will trigger all the sync process. Point it to the endpoints displayed right after the ESI Application sync status