Skip to main content

Search GiselleBot's commands and docs.

Try /ban, or start with / for commands only.

Press Ctrl K anywhere in the dashboard to open this.

Reactions Parsing

Reaction Parsing reports on the reactions added to messages in a channel: who reacted, how often, and which messages drew the most activity.

Note

Manage Messages is both Discord's command-permissions picker default for /reactions and separately re-checked in-code for every subcommand below, including print (see Layer 3).

/reactions print

Command Syntax

/reactions print message_id:{message id} [sort:{username/discriminator/nickname}] [show:{username/nickname}] [emoji:{default or custom emoji}]

Command Description

Prints the list of users who reacted to the specified message.

sort orders the output by the chosen setting; the default is the order Discord returns.

show sets how users are displayed; the default is by username.

emoji limits the output to that emoji.

Note

You can also right-click (or long-press) a message and choose Apps -> List reactions to run this against that message directly, without typing a message ID. That shortcut always shows usernames and does not support sort/emoji filtering - use /reactions print for that.

Permissions Needed

  • User: Manage Messages

Examples

/reactions print message_id:123456789098765432
/reactions print message_id:123456789098765432 sort:nickname show:nickname
/reactions print message_id:123456789098765432 emoji::pikathink:

/reactions summary

Command Syntax

/reactions summary [count:{# of messages}] [csv:{true/false}] [silent:{true/false}] [channel:{channel}]

Command Description

Prints a list of messages with reactions among the last count messages in the given channel (defaults to the current channel), with the reactions on each message and how many times each was used.

csv:true makes the bot send the command author a .csv file with the summary details. The .csv includes every message scanned, not just the ones that have reactions - a message with no reactions appears as a row with 0 in each reaction column.

The reply (and the DM that carries the .csv) reports how many messages were scanned and how many of them had reactions. If count is larger than the number of messages the channel has, the bot says so explicitly, since it has scanned the channel's entire available history rather than the requested amount.

Setting silent to true suppresses the in-channel embed output (this only works if used with csv:true).

If count is omitted, the bot will scan the latest 10 messages.

The maximum number of messages the bot will scan is 500.

Larger scans can take a while, as the bot paces its API calls to avoid rate limits.

Note

If channel targets a channel other than the one you ran the command in, the reply is always ephemeral (visible only to you) - regardless of the silent option - so the summary isn't posted publicly into a channel that may not have access to the target channel's content.

Permissions Needed

  • User: Manage Messages

Examples

/reactions summary
/reactions summary count:20 csv:true silent:true
/reactions summary csv:true

/reactions unique

Command Syntax

/reactions unique [count:{# of messages}] [csv:{true/false}] [silent:{true/false}]

Command Description

Prints a list of unique users that reacted to at least one message within the last count messages in the current channel.

csv:true makes the bot send the command author a .csv file with the details of the output. The file also shows each user's nickname and the number of times each user reacted to each reaction.

Setting silent to true suppresses the in-channel embed output (this only works if used with csv:true).

If count is omitted, the bot will scan the latest 10 messages.

The maximum number of messages the bot will scan is 500.

Larger scans can take a while, as the bot paces its API calls to avoid rate limits.

Permissions Needed

  • User: Manage Messages

Examples

/reactions unique
/reactions unique count:20 csv:true silent:true
/reactions unique csv:true

Note

The age/joined options below take the standard time code (e.g. 1d3h2m) - or a Discord timestamp mention referring to a future time - described in Time Format Code.

/reactions contest

Command Syntax

/reactions contest [count:{# of messages}] [age:{time code}] [joined:{time code}] [members:{number}] [csv:{true/false}] [silent:{true/false}]

Command Description

This command is built for reaction contests. Its output highlights reactions from recently created Discord accounts, to help spot "fraudulent votes": duplicate reactions added by new accounts to inflate one message's reaction count.

The age and joined options define what counts as a suspect user:

  • age defines the minimum age of the Discord account to avoid being flagged.
  • joined defines the minimum amount of time the user needs to be on the server to avoid being flagged.

members defines the minimum number of members needed to pass both checks for a message to be flagged as having fraudulent reaction votes.

As a practical example:

/reactions contest count:50 age:1w joined:3d members:5

flags any message in the last 50 in the current channel when more than 5 (unique) members reacted with a Discord account that is less than 1 week old and that joined the server less than 3 days ago.

If count is omitted, the bot will scan the latest 10 messages.

Omitting age and/or joined disables the matching check (omitting age marks any account as suspect, whatever its actual Discord age).

Omitting members leaves its default value of 0, which flags every message with at least 1 suspect member as fraudulent.

csv:true makes GiselleBot send 2 .csv files to the command author:

  1. A .csv with the same output as /reactions summary, showing the messages with reactions among the last count in the current channel, including the reactions on each and how many times each was used. It adds a "Fraudulent Flag" and a "Fraudulent Votes" column.
  2. A second .csv listing the users that meet the "Fraudulent Votes" criteria, with a separate record for each message they reacted to and how they reacted to it.

Setting silent to true suppresses the in-channel embed output (this only works if used with csv:true).

The maximum number of messages the bot will scan is 500.

Larger scans can take a while, as the bot paces its API calls to avoid rate limits.

Permissions Needed

  • User: Manage Messages

Examples

/reactions contest age:5d joined:1d
/reactions contest
/reactions contest count:50 age:2w joined:1w members:10 csv:true silent:true

See also

Full migration mapping for these commands: Migration Guide.