| Name | Name | Last commit date | ||
|---|---|---|---|---|
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
 |  | |||
twilight is a powerful, flexible, and scalable ecosystem of Rust libraries
for the Discord API.
The ecosystem of first-class crates includes twilight-cache-inmemory,
twilight-gateway, twilight-http, twilight-model, and more. These
are explained in detail below.
The main twilight crate is purely an advertisement crate: it has no
functionality. Please use the individual crates listed below instead!
Twilight supports a MSRV of Rust 1.60+.
We recommend that most users start out with these crates:
If you need any other functionality that Twilight provides, you can just add that dependency in.
These are essential crates that most users will use together for a full
development experience. You may not need all of these - such as
twilight-cache-inmemory - but they are often used together to accomplish
most of what you need.
Models defining structures, enums, and bitflags for the entirety of the
Discord API. It is split into a number of sub-modules, such as gateway for
containing the WebSocket gateway types, guild for containing types owned
by guilds (servers), voice containing the types used by the Voice
WebSocket API, and more.
These are all in a single crate so that you can use gateway models without
depending on twilight-gateway. One use case is if you write your own
WebSocket gateway implementation.
In-process-memory based cache over objects received from the gateway. It's responsible for holding and managing information about things like guilds, channels, role information, voice states, and any other events that come from Discord.
Implementation of Discord's sharding gateway sessions. This is responsible for receiving stateful events in real-time from Discord and sending some stateful information.
HTTP client supporting all of the Discord REST API. It is based on hyper.
It meets Discord's ratelimiting requirements and supports proxying.
Event processor that allows for tasks to wait for an event to come in. This is useful, for example, when you have a reaction menu and want to wait for a specific reaction on it to come in.
These are crates that are officially supported by Twilight, but aren't considered core crates due to being vendor-specific or non-essential for most users.
Client for Lavalink as part of the twilight ecosystem.
It includes support for managing multiple nodes, a player manager for
conveniently using players to send events and retrieve information for each
guild, and an HTTP module for creating requests using the http crate and
providing models to deserialize their responses.
Create display formatters for various model types that format mentions. For example, it can create formatters for mentioning a channel or emoji, or pinging a role or user.
Utility crate that adds utilities to the twilight ecosystem that do not fit in any other crate. Currently, it contains:
A trait and some implementations that are used by the gateway to ratelimit identify calls. Developers should prefer to use the re-exports of these crates through the gateway.
The following example is a template for bootstrapping a new bot using
Twilight's HTTP and gateway clients with its in-memory cache. In order to
run this, replace the contents of a new project's main.rs file with the
following. Be sure to set the DISCORD_TOKEN environment variable to your
bot's token. You must also depend on futures, tokio,
twilight-cache-inmemory, twilight-gateway, twilight-http, and
twilight-model in your Cargo.toml.
use std::{env, error::Error, sync::Arc};
use futures::stream::StreamExt;
use twilight_cache_inmemory::{InMemoryCache, ResourceType};
use twilight_gateway::{Cluster, Event};
use twilight_http::Client as HttpClient;
use twilight_model::gateway::Intents;
#[tokio::main]
async fn main() -> anyhow::Result<()> {
let token = env::var("DISCORD_TOKEN")?;
// Use intents to only receive guild message events.
// A cluster is a manager for multiple shards that by default
// creates as many shards as Discord recommends.
let (cluster, mut events) = Cluster::new(token.to_owned(), Intents::GUILD_MESSAGES).await?;
let cluster = Arc::new(cluster);
// Start up the cluster.
let cluster_spawn = Arc::clone(&cluster);
// Start all shards in the cluster in the background.
tokio::spawn(async move {
cluster_spawn.up().await;
});
// HTTP is separate from the gateway, so create a new client.
let http = Arc::new(HttpClient::new(token));
// Since we only care about new messages, make the cache only
// cache new messages.
let cache = InMemoryCache::builder()
.resource_types(ResourceType::MESSAGE)
.build();
// Process each event as they come in.
while let Some((shard_id, event)) = events.next().await {
// Update the cache with the event.
cache.update(&event);
tokio::spawn(handle_event(shard_id, event, Arc::clone(&http)));
}
Ok(())
}
async fn handle_event(
shard_id: u64,
event: Event,
http: Arc<HttpClient>,
) -> Result<(), Box<dyn Error + Send + Sync>> {
match event {
Event::MessageCreate(msg) if msg.content == "!ping" => {
http.create_message(msg.channel_id)
.content("Pong!")?
.exec()
.await?;
}
Event::ShardConnected(_) => {
println!("Connected on shard {shard_id}");
}
// Other events here...
_ => {}
}
Ok(())
}All first-party crates are licensed under ISC