SinisterRectus
SinisterRectus
Decided to re-open this because the idea here is good. Not yet sure if it will be implemented though.
Caching has been overhauled for 3.0. Caches and cached objects are now hidden internally in a central client state manager. If the client requests permanently cached objects, for example, a...
I'm thinking of making this behavior a client option for toggling between static and dynamic container objects.
You may translate the wiki, but know that sometime between now and April 30, a new version of Discordia will release, and it will have new docs that will probably...
Upon further inspection, I am now noticing that if an object is reused from a cache's weak table, it is incorrectly not updated with new data. This could be fixed...
I think this issue will be resolved, but maybe not in the best way. Due to the behavior of privileged intents and Discord's discouragement, members and presences are currently not...
Going to wait on this one, but not deny it.
Good enough for 2.x. I can always rewrite it in 3.0. I would rather have this as `false` by default though.
> Good enough for 2.x. I can always rewrite it in 3.0. I would rather have this as `false` by default though. I just realized this PR is for 3.0....
I honestly don't like the code. In particular: the concatenation before calling `API:log` then the potential interpolation of an empty string into `%s` in `API:log`.