Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/discljord/discljord

A Clojure wrapper library for the Discord API, with full API coverage (except voice, for now), and high scalability
https://github.com/discljord/discljord

clojure discord discord-api discord-api-wrapper discord-bot discord-clj

Last synced: 2 months ago
JSON representation

A Clojure wrapper library for the Discord API, with full API coverage (except voice, for now), and high scalability

Lists

README 

        
![Discljord](img/comp.png)



Discljord is a library for the easy creation of Discord Bots in Clojure! It works asynchronously by default, and has built-in support for sharding and rate-limits, with no extra work for the bot creator. Feel free to drop on by our [support server](https://discord.gg/discljord) if you'd like to try it out or need any help.



## Group ID Update

As of version 1.3.1, discljord has been moved to a new group id in clojars: `com.github.discljord`, to reflect the project's new place in its own GitHub Organization and joint maintainership status between @IGJoshua and @JohnnyJayJay. If after upgrading your build tool has trouble finding discljord, ensure you've updated the group id.



## Quick Start



With [leiningen](https://leiningen.org) you can set up a project really quickly:



1. Run `lein new discljord first-bot`



2. Put your bot token in `config.edn`



3. Run `lein run`



4. Your bot should go online now!



Alternatively, you can start a REPL (Read-Eval-Print-Loop) with `lein repl` and experiment with the API interactively.



If you are new to Clojure, have a look at a [language introduction](https://gist.github.com/yogthos/be323be0361c589570a6da4ccc85f58f) before you dive straight in. You should also get a general idea of [how to use the REPL](https://clojure.org/guides/repl/introduction).



The `start-bot!` and `stop-bot!` functions help you connect/disconnect to/from the Discord API from the REPL.



## Installation



Add the following to your project.clj in leiningen:



```clojure

[com.github.discljord/discljord "1.3.1"]

```



If you use tools.deps, then add the following to your `:dependencies` key in your `deps.edn`:



```clojure

{com.github.discljord/discljord {:mvn/version "1.3.1"}}

```



## Usage



To use discljord, add it to the project dependencies in leiningen's `project.clj` and run



```

lein deps

```



or to tools.deps' `deps.edn` and run



```

clj -e "(println \"Dependencies downloaded\")"

```



After that, discljord should be ready to go, and you can start building a bot!



### Bot Registration



Before your code can connect to Discord and start making API requests, it must be registered with Discord.  This is a one-time activity per bot, and involves:



1. Logging in to the [Discord developer portal](https://discord.com/developers).

2. Creating a new application (blue "New Application" button, top right).

3. Navigating to the "Bot" tab on the left, and click the blue "Add Bot" button.  Confirm your choice (blue "Yes, do it!" button).

4. Copying the bot's auth token (blue "Copy" button) and paste it somewhere secure (**do not save this token anywhere public!**).

5. Turning off the "Public Bot" setting (halfway down the page).  This step is optional, and you can turn this back on once your bot is released if you want others to be able to find it.

6. Turn on the Message Content Intent switch to make it easier to send events to your bot. You can turn this off for bots that don't need it, but it will be used in the examples below.

7. Navigating to the "OAuth2" tab on the left, and select the "bot" checkbox in the Scopes section.

8. Copying the URL generated in the previous step (blue "Copy" button), then paste it into a new browser tab.

9. Selecting which Discord server(s) you wish to add the bot to (note: you must have the "Manage Servers" role for servers to be visible in the dropdown).



After a few minutes, the bot should become visible as a user in the selected server, and it will be able to connect to, and interact with, that server.



### Basic Bot Construction



Bots in discljord are applications which consist of three separate processes. First is the connection on which Discord sends information to the bot. Second is an event handler which takes care of all the events sent to it by Discord. Third is a messaging process which takes messages the event handler (or other sources) want to send, and sends it to Discord, respecting rate limits.



Communication between these three processes is facilitiated via core.async's channels. To create a connection process, simply call the function `discljord.connections/connect-bot!`, which takes a channel on which you want to communicate with that process, and returns a channel that it will send events on. Starting the process to send messages is done with `discljord.messaging/start-connection!` which takes the token of your bot and returns a channel which you need to keep track of to send it messages, via the other functions in the `discljord.messaging` namespace.



In addition to the event channel, starting the connection requires specifying intents. All the examples below will use `:guilds` and `:guild-messages`, but a full list can be viewed [in the developer documentation](https://discord.com/developers/docs/topics/gateway#gateway-intents).



### Examples



Each of these examples can be run in a REPL, either via `lein try org.suskalo/discljord` (if you're using leiningen) or `clj -Sdeps '{:deps {org.suskalo/discljord #:mvn {:version "0.2.9"}}}'` (if you're using the Clojure CLI tools).  All of the examples are blocking (you will not be returned to the REPL until the bots are terminated).



#### Logging Bot



This example prints out all events that the bot receives to stdout, and is useful for learning what events and associated information can be sent by Discord.  Terminate it with Ctrl+C (note: when using the Clojure CLI tools this will also terminate your REPL).



```clojure

(require '[clojure.core.async    :as a])

(require '[discljord.connections :as c])

(require '[discljord.messaging   :as m])



(def token "TOKEN")

(def intents #{:guilds :guild-messages})



(let [event-ch      (a/chan 100)

      connection-ch (c/connect-bot! token event-ch :intents intents)

      message-ch    (m/start-connection! token)]

  (try

    (loop []

      (let [[event-type event-data] (a/")

                                  (:name emoji)))))



(def handlers

  {:message-create [#'greet-or-disconnect]

   :message-reaction-add [#'send-emoji]})



(let [event-ch (a/chan 100)

      connection-ch (c/connect-bot! token event-ch :intents intents)

      messaging-ch (m/start-connection! token)

      init-state {:connection connection-ch

                  :event event-ch

                  :messaging messaging-ch}]

  (reset! state init-state)

  (try (e/message-pump! event-ch (partial e/dispatch-handlers #'handlers))

    (finally

      (m/stop-connection! messaging-ch)

      (c/disconnect-bot! connection-ch))))

```



This bot will send emoji to the channel that a reaction is added in, as well as perform the same hello-world response the previous bot did. The main difference is that the actual dispatch to different handler functions is done via data, rather than via a multimethod. Additionally, this adds the ability to call multiple handler functions with a single event.



## Logging



Discljord uses [clojure.tools.logging](https://github.com/clojure/tools.logging) for all its logging, which means that you are responsible for providing it with a suitable logging implementation as well as configuration. If no configuration is provided, then it will likely default to whatever gets brought in by your other dependencies, potentially eventually falling back to `java.util.logging`, however it should still function even with no intervention by the library user.



Logging levels in discljord follow a basic pattern that anything at a `warn` level or lower is handled by discljord, and `error` or `fatal` will be used to inform the user of something that they can or should take action in an attempt to fix. Besides the generalization, here is a more specific listing of the purpose of the logging levels:



- Fatal :: Used when some condition is met that prevents discljord from continuing, even with user input

- Error :: Used when an unhandled error occurs or when user error causes the application to fail

- Warn :: Used when an error occurs but is handled by discljord without user input

- Info :: Used for application-scale control flow

- Debug :: Used for process-scale control flow

- Trace :: Used for logging all communication events and function-level control flow



## Known Issues



 - When using an SNI client for http-kit in JDK 17, discljord will fail to connect (see [this issue on http-kit](https://github.com/http-kit/http-kit/issues/482))

 - Compression may fail on very large payloads, appearing as an EOF while parsing JSON exception. This can be mitigated by setting the `disable-compression` flag on `connect-bot!`



If you find any other issues, please report them, and I'll attempt to fix them as soon as possible!



## Supporting the Project

If you would like to contribute financially to the creation of Discljord, a [Patreon page](https://www.patreon.com/discljord) is available to support me. There's absolutely no obligation to donate if you use this software, but if you do, I'll add your username to this document to thank you for your support!



## Current Patrons

You could have your name added here if you support the project!



- Johnny JayJay

- Peter Monks

- Jungy

- Ezazel

- Anders Murphy



## License



Copyright © 2017-2021 Joshua Suskalo



Distributed under the Eclipse Public License either version 1.0 or (at

your option) any later version.