46 releases
0.16.0-rc.1 | Feb 21, 2024 |
---|---|
0.15.3 | Sep 10, 2023 |
0.15.1 | Feb 26, 2023 |
0.14.0 | Nov 14, 2022 |
0.2.1 | Nov 2, 2020 |
#326 in HTTP client
297 downloads per month
Used in twilight
1.5MB
32K
SLoC
twilight-lavalink
twilight-lavalink
is a 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. It will automatically
handle sending voice channel updates to Lavalink by processing events via
the client's process
method, which you must call
with every Voice State Update and Voice Server Update you receive.
Features
http-support
The http-support
feature adds support for the http
module to return
request types from the http
crate. This is enabled by default.
TLS
twilight-lavalink
has features to enable tokio-websockets
' TLS
features. These features are mutually exclusive. rustls-native-roots
is enabled by
default.
native-tls
The native-tls
feature enables tokio-websockets
' native-tls
feature.
To enable native-tls
, do something like this in your Cargo.toml
:
[dependencies]
twilight-lavalink = { default-features = false, features = ["native-tls"], version = "0.2" }
rustls-native-roots
The rustls-native-roots
feature enables tokio-websockets
' rustls-native-roots
feature,
which uses rustls
as the TLS backend and rustls-native-certs
for root certificates.
This is enabled by default.
rustls-webpki-roots
The rustls-webpki-roots
feature enables tokio-websockets
' rustls-webpki-roots
feature,
which uses rustls
as the TLS backend and webpki-roots
for root certificates.
This should be preferred over rustls-native-roots
in Docker containers based on scratch
.
Examples
Create a client, add a node, and give events to the client to process events:
use std::{
env,
future::Future,
net::SocketAddr,
str::FromStr,
};
use twilight_gateway::{Event, EventTypeFlags, Intents, Shard, ShardId, StreamExt as _};
use twilight_http::Client as HttpClient;
use twilight_lavalink::{http::LoadedTracks, model::Play, Lavalink};
#[tokio::main]
async fn main() -> anyhow::Result<()> {
// Initialize the tracing subscriber.
tracing_subscriber::fmt::init();
let token = env::var("DISCORD_TOKEN")?;
let lavalink_host = SocketAddr::from_str(&env::var("LAVALINK_HOST")?)?;
let lavalink_auth = env::var("LAVALINK_AUTHORIZATION")?;
let shard_count = 1u32;
let http = HttpClient::new(token.clone());
let user_id = http.current_user().await?.model().await?.id;
let lavalink = Lavalink::new(user_id, shard_count);
lavalink.add(lavalink_host, lavalink_auth).await?;
let intents = Intents::GUILD_MESSAGES | Intents::GUILD_VOICE_STATES;
let mut shard = Shard::new(ShardId::ONE, token, intents);
while let Some(item) = shard.next_event(EventTypeFlags::all()).await {
let Ok(event) = item else {
tracing::warn!(source = ?item.unwrap_err(), "error receiving event");
continue;
};
lavalink.process(&event).await?;
}
Ok(())
}
There is also an example of a basic bot located in the root of the
twilight
repository.
Dependencies
~7–20MB
~299K SLoC