svenbrnn / hazardous-killbot Goto Github PK

Make it possible to filter the posting of the bot by region / konstellation or system.

Ability to use the name when subscribing. Id's should be searched from ESI with a cache in JSON files.
Maybe show a dropdown if there was only a part of the name entered.

Overview: The webhook that connects to get this information will periodically drop sometimes due to network or ip hiccups. The container is still active and healthy, but does not know that the webhook is down and still remains in a healthy state

What it does: The server will sometimes drop the webhook due to outages but does not reestablish, or make the container dirty for it to auto restart.

What I want it to do: 1 of 2 things. EITHER the codebehind should re establish the connection OR the container should become not healthy and trigger a restart.

Reproduction:

• Establish server.
• kill someone for confirmation of km.
• turn on or off router or switch to replicate a network outage.
• notice that the container is still running
• Kill same reportable person
• Notice the notification does not appear.
• manually trigger restart
• kill person a 3rd time
• notice that the most recent km appears.

Using discord.js we can show the user a form or modal on using a slash command.
Enhance subscribing using modals, maybe even with an autocomplete for corperations/alliances/characters/systems/regions/constellations.

Add the filters requested by Kiera Oramara In eve forums.

Add a command to subscribe/unsubscribe using a zkillboard url.

Currently you can only filter for region/system or ship type and not both. For example. It would be very useful to be able to filter kills to a specific region or regions. In this case we would need to filter region and ship type

The kill messages should be created by an embedding which allows us to set a color for kills/losses.

As the title says. The Docker configuration may sort this out, running outside of Docker this issue occurs.

[rkb@lemon src]$ npm run start

> [email protected] start
> cd dist && node index

node:internal/fs/utils:344
    throw err;
    ^

Error: ENOENT: no such file or directory, scandir './config'
    at Object.readdirSync (node:fs:1392:3)
    at ZKillSubscriber.loadConfig (/home/rkb/tmp/hazardous-killbot/src/dist/zKillSubscriber.js:480:24)
    at new ZKillSubscriber (/home/rkb/tmp/hazardous-killbot/src/dist/zKillSubscriber.js:99:14)
    at Function.ZKillSubscriber.getInstance (/home/rkb/tmp/hazardous-killbot/src/dist/zKillSubscriber.js:396:29)
    at Object.<anonymous> (/home/rkb/tmp/hazardous-killbot/src/dist/index.js:11:45)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
  errno: -2,
  syscall: 'scandir',
  code: 'ENOENT',
  path: './config'
}