You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After thousands of years, a new release of dimscord has emerged
Dimscord (v1.8.0):
New rest api endpoints and stuff e.g. polls
Fully complete components v2 support \o/ -> add the mfIsComponentsV2 into your flags param when sending/editing messages/responses
Fixed up the stupid fatal jsony error crashes, they should be rare and contain the useful information for debugging. adding -d:jsonyDumps whilst -d:dimscordDebug is enabled will show you what's happening.
Nim v1.2.0+ -> Nim v2.0.6+ required now
Fix weird message update and guild members update shenanigans
Deprecating the naming of the buttons/message component types
Gateway intents are mandatory, for any other advanced events it'll force you to enable the event otherwise you're gonna have a silent response when the event is called.
Cool stuff: message.guild , message.gchannel (-> guildchannel)
it's a shorthand for saying something like s.cache.guildChannels[chan_id], it also accept strings as well. I've seen users not using the intended cache, which I highly encourage to do so. REST endpoints like discord.api.getGuild, discord.getGuildChannel, ... should be a failsafe if it doesnt exist in cache, unless it's discord.api.getUser
changes with set[PermissionFlags] in Roles,
fix weird gateway connection issues when s.resumeGatewayUrl is empty string
components in interaction response messages should work perfectly flawless now
Almost every enum like MessageType should contain a unknown to prevent any potential crashes if type specified not in range
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
After thousands of years, a new release of dimscord has emerged
Dimscord (v1.8.0):
mfIsComponentsV2into yourflagsparam when sending/editing messages/responses-d:jsonyDumpswhilst-d:dimscordDebugis enabled will show you what's happening.message.guild,message.gchannel(-> guildchannel)it's a shorthand for saying something like
s.cache.guildChannels[chan_id], it also accept strings as well. I've seen users not using the intended cache, which I highly encourage to do so. REST endpoints likediscord.api.getGuild,discord.getGuildChannel, ... should be a failsafe if it doesnt exist in cache, unless it'sdiscord.api.getUserset[PermissionFlags]inRoles,s.resumeGatewayUrlis empty stringcomponentsin interaction response messages should work perfectly flawless nowMessageTypeshould contain a unknown to prevent any potential crashes if type specified not in rangeFull Changelog: v1.6.0...v1.8.0
Once again, I'd like to thank you all for your patience and helping out.
This discussion was created from the release Dimscord (v1.8.0).
Beta Was this translation helpful? Give feedback.
All reactions