I developed a small tool to notify you of your structures getting reinforced or running out of fuel.
This functionality is typically covered by Alliance Auth and SeAT for larger groups, but for smaller groups it might not be reasonable to set up such a big and complicated system just for this one feature.
This bot does the following things:
Gives you a notification when you structures are actively getting reinforced (e.g. hitting 95% shield)
Gives you notifications when your structures change state e.g. got reinforced, finished anchoring etc. including potential timers in your local timezone and UTC/EvE-time.
Gives you 30, 7, 3, 2 and 1-day warnings when your structures are running low on fuel.
Allows you to check structure states at any time with the /info command.
Currently allows to authorize up to 12 characters to reduce the cache delays and notify you faster, similar to how Alliance Auth and SeAT are doing things (10 minutes divided by #characters for notifications, 1h divided by #characters for state changes).
Gives you warnings once daily for all kind of things that would cause notifications to not work. E.g. incorrect corp permissions, authorized character leaving corp etc. including instructions how to fix them.
You can find the bot and instructions how to setup on github. For the user-side setup e.g. authorization and adding structures there is also a short video guide.
You can self-host this bot or use my community instance. I give my best to run the community instance as a piece of eve-online “critical infrastructure” but can not make any promises. The community instance can be invited to your discord server by the following invite link.
In case you do end up running this timer-bot please also join my community discord and mention that you are running this thing so I can notify people about downtime / migrations / failures etc.
that is very nice, is there a way to set the channel it makes announcements?
Yes, you can use !callback command to set it somewhere else
also any chance there could be nun Upwell stuff added like POS?
I think POSes are quite a bit more complicated in terms of states etc. than Upwell Structures so I don’t think this is an easy add-on in the short term. And long term days of POSes are probably also numbered anyway.
Btw I saw you needed to use command a few more often to get set up than I anticipated. If you can PM me any details what was unclear or went wrong I can try to make that more streamlined.
my bad, i was too fast reply here, it works now just as expected, i set one struture into low power and minutes later the warning came up as expected.
we attacked it (yay friendly fire is fun) .. and we got the attack notification too,
however there was never a fuel warning, i removed all the fuel to leave it on for a day, beyond the initial “new structure” post there is no indication about the low fuel state of the structure since then.
if i do !info it shows up with acurate levels, so the bot knows is going to be in low power n a few hours, but there is no warning about it. is there a way to set this up?
I agree friendly fire is fun, did it way to many times xD.
The fuel expiry was a problem on my end. The exact behavior when running out of fuel wasn’t set tested that well since my friends and I just refuel as soon as we get the 30-day warning. So all the n-day notifications worked alright up to the 1-day one. I fixed that one and now also added a 0-day notification e.g. running out of fuel right now.
just made another test and it shows this “FINAL WARNING” haha love it
works just fine now.
just refuelled a athanor to see how log it takes for the refuel notification to show (or does this only show when the pwer state changes?)
two suggestions:
use slash-commands (since the !-thing is a bit 2020
allow to specify a channel .. (i fooled myself a few times by just doing !callback #111 (channel ID)
which the bot confirmed but my ADHD ignored the wording on the response as it just sets the channel one executes the command in.
not big things, just ideas. i can fork it and push some of those things if you interested in help.
Fuel notifications are quite slow because of the 1h cache. They do show even when the state does not change however.
For your suggestions, I can add an optional argument to the !callback command so you can set it elsewhere as well. I think for slash commands I will probably do it at some point, but then update all my discord bots at once, nothing more confusing than having to use different systems at the same time.
could you add a 15 Day warning ?
it’s maybe too specific but we start taking fuel seriously when it gets below 15 ish .. and 7 is where things getting serious .. so having one before would be really nice.
