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
{{ message }}
This repository was archived by the owner on Dec 1, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,3 +14,32 @@ docker-compose -p javabot up
14
14
For your convenience, the docker-compose file also includes admin tools that can be useful for debugging.
15
15
- MongoExpress is available at [localhost:5050](http://localhost:5050)
16
16
- PgAdmin is available at [locahost:5051](http://localhost:5051)
17
+
18
+
Once those services are in order, you can run the bot as you would any Java program, and it will generate a `config` directory. Stop the bot, and set all the necessary properties in `systems.json`.
19
+
20
+
## Commands
21
+
Commands are defined in YAML files located in `src/main/resources/commands`. The data in these files are transformed into an array of `CommandConfig` objects using JSON deserialization. These commands are then used in `SlashCommandListener#registerSlashCommands` to register all slash commands.
22
+
23
+
**Each command MUST define a `handler` property whose value is the fully-qualified class name of a class implementing `SlashCommandHandler`**. When registering commands, the bot will look for such a class, and attempt to create a new instance of it using a no-args constructor. Therefore, make sure your handler class has a no-args constructor.
24
+
25
+
## Privileges
26
+
To specify that a command should only be allowed to be executed by certain people, you can specify a list of privileges. For example:
27
+
```yaml
28
+
- name: jam-admin
29
+
description: Administrator actions for configuring the Java Jam.
In this example, we define that the `jam-admin` command is first of all, *not enabled by default*, and also we say that anyone from the `jam.adminRoleId` role (as found using `Bot.config.getJam().getAdminRoleId()`). Additionally, we also say that the user whose id is `235439851263098880` is allowed to use this command. See `BotConfig#resolve(String)` for more information about how role names are resolved at runtime.
39
+
40
+
# Configuration
41
+
The bot's configuration consists of a collection of simple JSON files:
42
+
- `systems.json`contains global settings for the bot's core systems.
43
+
- For every guild, a `{guildId}.json` file exists, which contains any guild-specific configuration settings.
44
+
45
+
At startup, the bot will initially start by loading just the global settings, and then when the Discord ready event is received, the bot will add configuration for each guild it's in, loading it from the matching JSON file, or creating a new file if needed.
0 commit comments