I fixed the API to emit IDs (again)

use those

like we do for feature LP

first only templates for like "SOON", "LIVE" and "UPCOMING".

need to decide how to do when there are multiple lines

(somewhat) depends on #22

.split is bad mkay

Add a command like !info which shows which servers the bot is on, as well as which features are enabled on which channels.

This should also help cleanup the config with servers that don't exist anymore (or where the bot was kicked from) and channels that were deleted/that the bot doesn't have access to anymore.

Store errors in some log.

• scalert/src/scalert/ScPoller.cr

  Line 33 in c5246b3

  puts "Rescued poller exception\n#{ex.inspect_with_backtrace}"

• scalert/src/scalert/ScPoller.cr

  Line 51 in c5246b3

  puts "Rescued live events poller exception (channel: #{channel_id}, games: #{games})\n#{ex.inspect_with_backtrace}"

• scalert/src/scalert/ScPoller.cr

  Line 88 in c5246b3

  puts "Rescued lp poller exception\n#{ex.inspect_with_backtrace}"

• scalert/src/scalert/ScBot.cr

  Line 57 in c5246b3

  puts("Unable to check permissions for user=#{user_id} and channel=#{channel_id}")

• scalert/src/scalert/ScBot.cr

  Line 99 in c5246b3

  puts("Unable to create message on #{channel}")

• https://github.com/vendethiel/scalert/blob/5852858396dc1370b7d9152924311eee87df848a/src/scalert/ScBot.cr

• (?)

  scalert/src/scalert/ScCommands.cr

  Line 323 in c5246b3

  puts("Unauthorized command from #{payload.author.id}")

ANNOUNCEMENTS
EVENTS_COMMAND
ADMINS

we need to return a list and apply range then

otherwise if event *1 is GSL and event *11 is GSL, we won't see "in 2 hours then 1d 2h", because the *11 will have been split off already.

Instead of:

Received from 369748300607389698: foo bar

Show something like:

{SERVERID} "Server" #CHANNELID #Channel @POSTERID @Poster: foo bar

related to #5

fooken legacy code

if real fancy, should:

• first exact match
• then try "starts with"
• then try contains

Should post about the 2 next events top.

Examples:

Bad: (shouln't include name to prevent injections/whatever)

user> !next BAD
bot> No upcoming event.

Exact match, one result:

user> !next Blizzcon: Qualifiers First Round
bot> Next Blizzcon: Qualifiers First Round in 1d 5h.

Exact match, two results:

user> !next GSL Code S
bot> Next GSL Code S in 1d 5, then 3d.

Inexact match, twice same:

user> !next GSL
bot> Next GSL Code S in 1d 5, then 3d.

Inexact match, different:

user> !next BTSL
bot> Next BSL: Europe in 1d 5, then BTSL: Asia in 1d 12h.

Example:

> !events
UPCOMING
 * WCS Regional Challengers - 32m, then 9h 32m, then 20h 2m
> !events all
UPCOMING
 * WCS Regional Challengers - 29m, then 9h 29m, then 19h 59m, then 1d, then 1d 9h, then 2 days

Should give the same results

I suppose the folded event's "date" can be the date of the first one.

So that we don't warn if we rapidire shutdown/start up bot
Just store "upcoming events" as current_events for the lp_poller.

Probably wants a Poller class(?)

maybe also lost new/lost servers
and maybe when someone does something (add a channel etc)?

• Rename banlist to ignorelist
• Add !ignore +/-/etc
• Add a (admin-only) listing (!ignore by itself?) that "ping" so admin can see who they are

should be able to use !feature within a server

also !stream probably.

no one cares

when an event goes live, the event should be able to ping a role(probably), predefined, per-server.
people should be able to subscribe to that role.

related to #4

So you can have channel X > alerts / !events for SC2 and BW.

In the spirit of youtube's 301 views... We show at most 11 events