Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

$ignoreChannels

See original GitHub issue

Type

Functions: \ $ignoreChannels[channelID;channelID;channelID;…;error message] ~~- Callbacks: <Callback Name>~~ ~~- Handlers: <Handler Type>~~ ~~- Others: ______~~

Description

The use of the command is prohibited on channels whose ID is entered. If used, the entered error message is sent.

bot.command({
name:"hello",
code:`helloooo!
$ignoreChannels[798055313907253279;I was banned from saying hello to you on this channel :(]`
})

There is an example in bdfd.

Issue Analytics

State:
Created 2 years ago
Reactions:3
Comments:9 (4 by maintainers)

Top GitHub Comments

2reactions

dutchman-devcommented, May 2, 2021

Channels are global objects so there is no guildID field needed.

1reaction

falsisdevcommented, May 2, 2021

Type

Functions: \ $ignoreChannels[channelID;channelID;channelID;…;error message] ~~- Callbacks: <Callback Name>~~ ~~- Handlers: <Handler Type>~~ ~~- Others: ______~~

Description

The use of the command is prohibited on channels whose ID is entered. If used, the entered error message is sent.
bot.command({
name:"hello",
code:`helloooo!
$ignoreChannels[798055313907253279;I was banned from saying hello to you on this channel :(]`
})
There is an example in bdfd.
ngl I like your idea but it’s already possible

you can just add $onlyIf[$checkContains[$channelID;channelid1;channelid2;....]==false; This Channel Is Blacklisted]

This Works Like $ignoreChannels so Ig There is no need