You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-4Lines changed: 13 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ One of the distinctive features of ChadCounting is the catch-up feature. In case
22
22
- Counts any message that starts with a number.
23
23
24
24
## Usage
25
-
To configure the bot for the first time, add it to your Discord server and use the `/setchannel` command to let the bot know where it should keep track of counting. After that, ChadCounting is up and running and you can start competing!
25
+
To configure the bot for the first time, add it to your Discord server and use the `/set channel` command to let the bot know where it should keep track of counting. After that, ChadCounting is up and running and you can start competing!
26
26
27
27
## Commands
28
28
The following commands could be used:
@@ -51,7 +51,11 @@ pip3 install -U pytz (confirmed with version 2023.3.post1)
51
51
When creating your own fork of ChadCounting, ensure your bot has at least the `Send Message`, `Read Message History` and `Add Reactions` OAuth2 permissions. `Use External Emojis` is an optional permission, but recommended. The scope should be `bot`.
52
52
53
53
### Dev-mode
54
-
In the `Initialisation` region of the `bot.py` file, `dev_mode` can be enabled to facilitate the testing of real-world scenarios. By enabling `dev-mode`, the bot can be configured to operate solely within a designated (testing) guild, thus preventing beta code from impacting production guilds. It is recommended to have two separate Discord bots, one for production and one for development, to safely test new code without putting the production environment at risk.
54
+
In the `Initialisation` region of the `bot.py` file, two development options can be enabled to facilitate the testing of real-world scenarios.
55
+
56
+
The first option, `dev_active_single_guild`, can be enabled to configure the bot to operate solely within a designated (testing) guild, thus preventing beta code from impacting production guilds. The `dev_mode_guild_id` should be set to the ID of this testing guild. This allows you to safely test new code without putting the production environment at risk.
57
+
58
+
The second option, `dev_disable_apis`, can be enabled to disable connections to APIs such as the bot websites top.gg and discordbotlist during development. It is recommended to have two separate Discord bots, one for production and one for development, to safely test new code. This option should be enabled when using a development bot account to prevent pushing the development bot's data to the APIs.
55
59
56
60
[Link to add ChadCounting Dev to a guild](https://discord.com/api/oauth2/authorize?client_id=1069230219094921318&permissions=329792&scope=bot)
57
61
@@ -62,12 +66,17 @@ Counting and guild data is saved to a JSON database, eliminating the need for ex
62
66
For added security and to comply by Discord's ToS, create a .env file in the root directory of the ChadCounting bot folder (where bot.py is located). This file serves as the designated location to securely store bot tokens. To add your Discord bot tokens, follow the example below:
63
67
```
64
68
# .env
65
-
DISCORD_TOKEN=your_discord_bot_token
66
-
DEV_TOKEN=your_discord_dev_bot_token
69
+
DISCORD_TOKEN=token_here
70
+
DEV_TOKEN=token_here
71
+
DISCORDBOTLIST_TOKEN=token_here
72
+
TOPGG_TOKEN=token_here
73
+
DISCORDS_TOKEN=token_here
74
+
DISCORDBOTSGG_TOKEN=token_here
67
75
```
68
76
69
77
### Versioning
70
78
To properly manage versioning, it is recommended to update the `bot_version` variable in the `Initialization` section of the `bot.py` file every time a functional version is ready to be pulled to the `main` branch. This version will be displayed in the output of the `/help` command. ChadCounting uses semantic versioning and a version number is written as `MAJOR.MINOR.PATCH`, where:
71
79
-`MAJOR` version is increased for incompatible changes to previous versions.
72
80
-`MINOR` version is increased for new features that are backward-compatible.
73
81
-`PATCH` version is increased for backward-compatible bug fixes.
82
+
When you are working on a new version and commit to the `dev` branch, ensure the version temporarily ends with `-indev` to indicate that the version is in development and might not function yet.
0 commit comments