A Discord bot made for any guild. It manages and powers a #counting channel. Fully customizable.

With this bot server members can count and compete together. It is exactly how it sounds, members send numbers to the chat in sequence. When admins add the bot, the only setup the bot requires is configuring the counting channel. This can be done with the `c?channel` command: send the command in the channel you wish to count in.

The permissions the bot requests when invited are all necessary to use the full features of the bot. The permission for `Managing Roles` is required for the Fail Role feature. The permission for `Managing Messages` is required for the NoChat feature, as well as features that are in the works.

### Commands

*`<>` denotes no arguments ⚬ `<...>` denotes required arguments ⚬ `[...]` denotes optional arguments*

🔹 `c?automute <on/OFF>` 
Turn the auto mute feature on or off, off by default. The bot will internally judge how long users should be muted for. When this is on, users will receive a DM informing them of how long they are muted for.

🔹 `c?channel [#channel]` 
Set the counting channel to the current channel or another. This is not set automatically. Once set, start sending numbers in the channel to count.

🔹 `c?cleanmutes <>` 
Clear all existing mutes from the counting channel. Anyone muted should be unmuted, but if the bot's permissions or something else isn't set correctly, this may not work.

🔹 `c?cmdchannel [#channel | 'reset']` 
Set the channel that commands will be allowed in. Commands will not be responded to anywhere else. Reset by sending 'reset'.

🔹 `c?current <>` 
Get the current count.

🔹 `c?failrole <role (any form) | 'none'>` 
Set the role to give someone when they reset the count. Being saved will not cause them to receive this role. 

🔹 `c?foulplay <on/OFF>` 
Turn foul play prevention feature on or off, off by default. This will prevent deleted messages from messing up the count.

🔹 `c?help <>` 
Stop, get help

🔹 `c?howto <>` 
In case you haven't already figured it out

🔹 `c?increment <number < 75,000>` 
Set the count difference

🔹 `c?invite <>` 
Invite the bot to your server!

🔹 `c?leaderboard <>` 
Get the global leaderboard

🔹 `c?mutestatus [muted member]` 
Get information about a current mute for a user. If the user is muted, it will show how long is left on their mute.

🔹 `c?next <>` 
Find the next number in sequence. It will warn if a number should not be sent.

🔹 `c?nochat <true/FALSE>` 
Set whether chatting is allowed in the counting channel (non-numeric messages will be deleted)

🔹 `c?recordrole <#role | none>` 
Set the role given to record breakers (when the record is broken, the role will be given; the bot requires role management permissions).

🔹 `c?saves <>` 
View all available saves (guild/server saves and personal saves)

🔹 `c?stats <>` 
Get stats about the current guild (record, current count, top counter, worst counter, etc.)

*Arguments for commands are denoted within the `<>` and `[]` tags. `<...>` means the argument is required, `[...]` means it is optional.*

### Features

**Counting channel:** the counting channel is the place where the bot is configured to accept counting. Any numbers sent here will be registered and validated by the bot.

**Counting:** this is the primary function of the bot. The bot accepts numbers (and numbers only) in the counting channel. If a number out of sequence is sent, the bot will consider it wrong. If someone tries to send more than one term in sequence, the bot will also consider that wrong. counting human encourages multi-member participation in the counting channel. This is also to make the leaderboards as fair as possible.

**Increment:** this setting determines the sequence. The increment determines which number should be sent after the last. To help understand it, just add the increment to the number that was sent last, and that is the next number. **By default, the increment is 1. If this is changed with the `c?increment` command, the server will no longer be allowed on leaderboards.**

**Fail role:** a setting (unconfigured by default) that contains a role to be given to a member whenever he/she fails the count. Soon the bot will feature **timed fail roles**.

**No chat:** a setting (off by default) that allows only numbers in the counting channel. When the settings is on, if a member sends a message that the bot does not register as a number, the message will immediately be deleted.

**Saves:** a more complex feature that allows the count to continue from where it was even if someone fails the sequence. Saves are a unit stored by the bot which are assigned to both servers and users. By default, when a bot is added to a new server, that server is given one free "guild save." That save only affects that server. When a member uses counting human for the first time they also get one free save, a "personal save." When someone fails the sequence, the bot will check if they or the server has saves left. If so, the bot will decrement one save from one in the order of `personal save > guild save` (if both have saves left). If a save has been subtracted, the counting will continue unaffected. If no saves were left, the count will fail as normal. Personal saves are global, so a save used in one server will also affect personal saves in another server. Soon there will be a feature that admins may enable that will disable saves in a server.

**Catches:** measures in place to prevent too much unfairness and outrage within servers. 
- If someone deletes their message (a valid count) right after sending it, the count will remain valid. If someone then sends a number (any number) and gets it wrong, the bot will allow two guesses from anyone to get the right number.

counting human

Count with other server members until someone messes up. Compete to earn a place on leaderboards.

counting human के लिए वोट कर रहे हैं

क्या आप हमारी सहायता करना चाहते हैं?