VAKiliner

Results 19 comments of VAKiliner

Everything works correctly If the guild is nswf, then all channels are also nsfw, regardless of whether they are configured that way `channel.nsfw` is the saved channel setting, as they...

Oops, looks like I wasn't fully awake or didn't figure out the issue due to bad formatting on my phone Now I know it's definitely a bug

I have Windows 10 and I can't reproduce the error

> Note: communication disabled checks are a duplicate of [#9730](https://github.com/discordjs/discord.js/issues/9730). > > There is discussion in there on paths forward, but nothing has come of it (yet). I'll add this...

There is also a bug with `Message.crosspostable` that on non-community servers the message is not crossposted, but I don't know which guild feature to check (maybe `News`?)

For `v14`, the **ReadMessageHistory** permission is checked in `Message.pinnable`, but not in `v15`

I found a new bug in `Message.pinnable`; in voice channels, this getter returns true, even though the voice channel doesn't support pins

`Message.pinnable` now checks the **ReadMessageHistory** permission and the voice channel!

I realized what this piece of code is for, but it's wrong Now I'll write how to reproduce the problem