souji
souji
DIAdiscord.js - Imagine an app
Created by Bouns on 5/24/2025 in #djs-questions
Optimizing Cache Management for a High-Volume Discord Bot
i'd say if you have a clearly defined idea of what you want to cache, using the core wrapper is likely going to be more beneficial (you retain the rate limit handling and api interface), but will (as a necessary result, because it is more bare-bones) loose a lot of the convenience you have with the fully cached discord.js
8 replies
DIAdiscord.js - Imagine an app
Created by Bouns on 5/24/2025 in #djs-questions
Optimizing Cache Management for a High-Volume Discord Bot
we've had a system in place at some point that let you define a class that gets instantiated instead of another one think, CustomUser instead of User, every time the client would normally construct a user i'm not entirely sure anymore (has been a while), but you could probably also make it slimmer than the original structure we've dropped that for multiple reasons to do with the same points i've tried to explain above - having a defined set of attributes and values in structures that both the user as well as other library internals can rely on and interact with another version of that sort of system is on the horizon, but there's no ETA as to when or even if that will happen
8 replies
DIAdiscord.js - Imagine an app
Created by Bouns on 5/24/2025 in #djs-questions
Optimizing Cache Management for a High-Volume Discord Bot
if you want to specifically determine which object attributes are kept and sweepers/cache limiters are not sufficient, you will have to do your own caching altogether. discord.js is only as easy to use as it is because of the support of strong caching. for resource heavy use cases and if you are absolutely sure you only need a limited amount of data from structures you may want to consider using the minimal @discordjs/core package instead. that being said, you will loose a lot of the convenience you get from having clearly defined object instances with known values
8 replies
DIAdiscord.js - Imagine an app
Created by WhiteHat Hacker-Dark Team Member on 5/19/2025 in #djs-questions
AutoModerationActionExecution Event Not Firing
then look at the documentation for your version and you will see it's there as well: https://discord.js.org/docs/packages/discord.js/14.18.0/GatewayIntentBits:Enum the bot defaults to the most recent stable version, since that's what you should generally be running 14.18.x -> 14.19.x is also a minor update and shouldn't break anything, so there really isn't much of a reaosn not to update
13 replies
DIAdiscord.js - Imagine an app
Created by Lixeiro Charmoso on 5/16/2025 in #djs-questions
Error: Cannot message this thread until after the post author has sent an initial message.
i just wait 2s before letting it post that :kek:
22 replies
DIAdiscord.js - Imagine an app
Created by ♡⃕Mvk on 5/17/2025 in #djs-questions
in-line vertical
no
5 replies
DIAdiscord.js - Imagine an app
Created by ♡⃕Mvk on 5/17/2025 in #djs-questions
in-line vertical
no. inline in embed suggests to discord that you want those fields to display inline (2), however they will be broken up if the device rendering the embed requires it because of screen width. fields are semantically stand-alone units of information. combining fields to display columns or similar will always break on one platform or the other
5 replies
DIAdiscord.js - Imagine an app
Created by Mist? 🎀 #encode on 5/12/2025 in #djs-questions
Components v2
40 total components per message as per
6 replies