Example:

Only allow the command to be ran in a specific channel by administrators.

const F = discord.command.filters;
const ADMIN_CHANNEL_ID = '628887548604841984';

const commands = new discord.command.CommandGroup();
commands.raw(
  {
    name: 'admin',
    filters: F.and(F.isChannelId(ADMIN_CHANNEL_ID), F.isAdministrator())
  },
  (message) => message.reply('hey!')
);

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

This differs from discord.command.filters.canManageNicknames in that the discord.Permissions.CHANGE_NICKNAME permission only allows the user to change their own username, and not the username of others. This means that this filter checks if the user can change their own nickname.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

Note: Since commands are generally executed in text channels, without a channelId provided, this checks to see if the user is able to connect to channels without any specific permission overrides.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

This differs from discord.command.filters.canManageChannelWebhooks in that, this permission checks if they can manage all webhooks on the guild, rather than webhooks within a specific channel.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

Note: Since commands are generally executed in text channels, without a channelId provided, this checks to see if the user is able to speak with priority in channels without any specific permission overrides.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

Note: This filter always takes a channelId, as it's implied that the user has the read message permission in the current channel if they're able to execute a command in that channel. This allows you to check if the user is able to read messages in another channel.

Note: This filter always takes a channelId, as it's implied that the user has the send message permission in the current channel if they're able to execute a command in that channel. This allows you to check if the user is able to send messages in another channel.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

Note: Since commands are generally executed in text channels, without a channelId provided, this checks to see if the user is able to speak in channels without any specific permission overrides.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

By default, will check for the permission in the current channel that the command is being invoked in. However, you can specify a specific channelId as an optional argument, that will override the channel that the permission will be checked in.

Note: Since commands are generally executed in text channels, without a channelId provided, this checks to see if the user is able to speak using voice activity detection in channels without any specific permission overrides.

Example:

Checks to see if the user's discriminator is #0001.

const is0001Discriminator = discord.command.filters.custom(
 (message) => message.author.discriminator === '0001',
 'discriminator must be #0001'
);

This is a lower level function of the can... functions located in this module. For example, the following are equivalent:

• discord.command.filters.hasChannelPermission()
• discord.command.filters.hasChannelPermission(discord.Permissions.MANAGE_MESSAGES)

Note: Providing an empty roles array will cause the script to fail validation.

This is a lower level function of the can... functions located in this module. For example, the following are equivalent:

• discord.command.filters.canManageGuild()
• discord.command.filters.hasGuildPermission(discord.Permissions.MANAGE_GUILD)

Note: This is basically equivalent to discord.command.filters.hasSomeRole([role]). But with a more specialized error message. Internally, if hasSomeRole or hasEveryRole is called with a single role id, it will use this function instead.

Note: Providing an empty roles array will cause the script to fail validation.

Example:

Only allows the command to be ran if the user is NOT an administrator.

const F = discord.command.filters;

const commands = new discord.command.CommandGroup();
commands.raw(
  {
    name: 'hey',
    filters: F.not(F.isAdministrator())
  },
  (message) => message.reply('hey!')
);

Example:

Only allow the command to be ran in a specific channel, or if the user is an administrator.

const F = discord.command.filters;

const commands = new discord.command.CommandGroup();
commands.raw(
  {
    name: 'hey',
    filters: F.or(F.isChannelId(CHANNEL_ID), F.isAdministrator())
  },
  (message) => message.reply('hey!')
);

This is really useful in combination with the discord.command.filters.isChannelId filter (see below).

Example:

Limits a command group to only be usable in a given channel. If the user is not in that channel, and tries to use a command, don't allow it to be used, but also don't tell them which channel they need to be in. For example, if you had an game channel that you wanted to run game commands in:

const F = discord.command.filters;
const GAME_CHANNEL_ID = '628887548604841984';
const gameCommands = new discord.command.CommandGroup({
  filters: F.silent(F.isChannelId(GAME_CHANNEL_ID))
});
gameCommands.raw('d6', (message) =>
  message.reply(`Your roll is ${(Math.random() * 6) | 0}`)
);
gameCommands.raw('flip', (message) =>
  message.reply(`Coin flip is ${Math.random() < 0.5 ? 'heads' : 'tails'}!`)
);

Example:

Wrap the [[discord.command.filter.isAdministrator]] filter, providing a custom criteria message if the user is not an administrator.

const F = discord.command.filters;
// You can now use `coolerAdminFilter` with your commands. You of course don't need to assign this
// to a variable. But if you've gone through the effort of making a cool criteria message, you
// might want to reuse it.
const coolerAdminFilter = F.withCustomMessage(F.isAdministrator, "be an incredibly cool person");