galaxysh / cr-counting-bot Goto Github PK

Add ESLint, Jest, and Husky to automate and streamline the development proccess

I was thinking it'd be cool if admins on a server could set a custom increment function where you specify an equation that determines the next value that a user should send in the counting channel, for example c?increment f(x)=(x^(1/2)+1)^2 would have it so the values the users have to put in are 1, 4, 9, 16, 25, 36, ect. where x is the previous value output from the equation and the first value put in as x(before the first user provides a number) is 0

explained in the title syntax could be c?botchannel add #some-channel which adds a channel to the list of channels the bot will respond to commands in and c?botchannel remove #some-channel will have it stop responding in that channel

This behaviour can either count as foul and reset the behaviour, or it may just decrement the count (if it was the most recent one)

You should add an option to build up personal saves for sending correct numbers so if you have said 10 correct numbers got 1 personal save or something. could add a cap to stored saves aswell.

this would be done to prevent a mistake from occuring when 2 people send a message at almost the same time if not the same time command could be c?margin 5s

errors due to lack of guild access

Hey would it be possible for you to implement the following into the counting human?
An achievement role for #counting participants in a record breaking count. Every member that sent n or more messages gets the role and previous record breakers then get their role removed.

Codec

• Add needed record tracking
• Add record role management
• Add single record role holder
• Add support for multiple at once (somehow figures out who is involved in a record breaking count)

This mode which will be enabled through a command will enable the features described in #26 , among others in the future.

If you type something that would be invalid, it just says that it's within the threshold.

I believe that this server is at 0 lives in total.

First, for every message make whether nochat is on a property of the passed client variable. Second, if nochat is on and the people mess up arguments to things like c?curr (where they could attach messages and images to chat), delete the messages, thus enforcing nochat.

Make a public viewable lb command.