Moon
Moon
Back to you on this one, we don't seem to cache the members of the scheduled events regardless of the code provided being incorrect.
In order to fix this we need to introduce a new ScheduledEventMember that contains eventId - user - member given by discord and make a data model to store it...
Please keep an eye on #631
where is the PR that caused this change?
What do you mean
I've been short on time lately to look into anything that would keep the sealed nature of the events while allowing for extensiblity of the events. Essentially we could assume...
> After 6 hours of testing with an example bot linked at https://github.com/Stonedestroyer/kord-example on a token with 3500 servers I can confirm that the coroutines are getting garbage cleaned and...
> One way to band-aid events for people with frameworks would be to assign a UUID to each event. Another (potentially more accessible) option would be to add a property...
I've modfied the example just before you commented Tho in a real scenario wouldn't you wrap those `extras` into another objects later on?
I still can't figure out if this should be in the library or could be some sort of separate thing