You are reading the Countegrity Community Edition documentation. Countegrity Enterprise docs are private and available to licensed teams only. Talk to sales

Commands

The setup commands and allowsame require Manage Messages (or administrator); status is open to everyone. There is no manual state-editing command: the checkpoint is always derived from the log, and the only repair is the admin-confirmed wipe.

Command Effect
[p]count setchannel [#channel] Enable counting (default: the channel you are in). Verifies the Message Content intent and the bot's permissions, then derives the checkpoint from the existing log. Refused when the log is not a clean sequence from 1 (a log that is clean except for same-author increments is enabled with the author lock frozen at the current count); nothing is deleted on refusal.
[p]count removechannel Disable counting and delete this channel's state, including any pending repair notice.
[p]count allowsame [before <count>|off|<count>] Control the author lock. before N (or a bare N, which means the same) accepts same-author increments for counts up to and including N (bot-era history, or single-account testing) and enforces alternation from N+1 on; the limit can only be raised from the current count. off is a shortcut for before 0 (in a live channel that only works while the count is still 0, since the limit cannot be lowered). A bare call with no arguments shows the current setting. Inside a counting channel the command line is deleted on arrival and the reply is a transient notice, like a rejection message.
[p]count status Show current count, next expected, last counter, ledger size, pending repair notice and permission warnings.

Aliases: [p]count disable (removechannel), [p]count show (status) and [p]count allow-same-author (allowsame).

Edit this page