Closed FoxLisk closed 2 months ago
implementation wise, my plan is to do something like this:
once this is in place, we can probably also leverage it to keep main discord events in sync
ok i changed my mind. annotating everything that updates a race is stupid and liable to be hella buggy. given that cardinality is so tiny, we can just do routine scanning. something like
i dont even know what these comments meant anymore
we now have an asynchronous worker that effects correct event state based on looking at current events + looking at db state. it's only doing things in main discord now; the plan is to have it just also work in other discords. this mostly means a way to join other discord and then a worker that handles creating events in them. my plan is to have this be a separate discord bot so the main one can maintain its assumptions about being a 1-discord bot
Bydey asked for this and it seems kinda fun to build. The idea is to have a separate discord bot that people can invite to their servers to generate events. it'd also be nice to have a way for it to filter the events so people can, e.g., only get their own races