#Yeah I can t work out why from what you

1 messages · Page 1 of 1 (latest)

blissful sequoia
#

Well I did some more research.

So far using user.roles.cache.get(role.id) returns the @everyone role for me.

Another thing I've noticed is that it looks like after fetching a role Discord.js swaps the @everyone id with the id of the role I just fetched.
This is reflected by this:

permissionOverwrites: [
  {
    id: interaction.guild.roles.everyone.id,
    deny: [PermissionsBitField.Flags.ViewChannel]
  }
]

Updating the role of the latest fetched role. If none have been fetched it correctly changes permissions for the @everyone role, but as soon as I use await channel.guild.roles.cache.find( role => role.id = roles.id ) it starts using that role as the @everyone role.

I'll do some more experimenting to see if I can get some more information to narrow down the problem

lone coral
blissful sequoia
#

Okay... facepalm
This might have actually been it... I feel like a dump shithead now.

Let me quickly test it

#

Someone please revoke my developer licence...

Would using await channel.guild.roles.cache.find( role => role.id = roles.id ) changing the @everyone be considered a bug?
If so I guess at least something useful came out of this stupid mistake xD

lone coral
#

You are changing it yourself

#

Its not a bug

#

role.id = roles.id you are changing the value yourself

blissful sequoia
#

Makes sense, well thank you very much at least for helping me out!
Must've looked over that almost a 100 times by now pepesweatsmile
But I can peacefully continue my development now