#discord #discord-api #twilight

twilight-standby

Utility to filter wait for filtered incoming events for the Twilight ecosystem

35 releases (15 breaking)

new 0.15.0 Feb 5, 2023
0.14.1 Jan 20, 2023
0.14.0 Nov 14, 2022
0.12.1 Jul 26, 2022
0.2.1 Nov 29, 2020

#53 in Asynchronous

Download history 55/week @ 2022-10-16 41/week @ 2022-10-23 65/week @ 2022-10-30 59/week @ 2022-11-06 107/week @ 2022-11-13 79/week @ 2022-11-20 66/week @ 2022-11-27 29/week @ 2022-12-04 83/week @ 2022-12-11 62/week @ 2022-12-18 31/week @ 2022-12-25 125/week @ 2023-01-01 152/week @ 2023-01-08 93/week @ 2023-01-15 115/week @ 2023-01-22 74/week @ 2023-01-29

442 downloads per month
Used in twilight

ISC license

1.5MB
29K SLoC

twilight-standby

codecov badge discord badge github badge license badge rust badge

Standby is a utility to wait for an event to happen based on a predicate check. For example, you may have a command that has a reaction menu of ✅ and ❌. If you want to handle a reaction to these, using something like an application-level state or event stream may not suit your use case. It may be cleaner to wait for a reaction inline to your function. This is where Twilight Standby comes in.

Standby allows you to wait for things like an event in a certain guild ([Standby::wait_for]), a new message in a channel ([Standby::wait_for_message]), a new reaction on a message ([Standby::wait_for_reaction]), and any event that might not take place in a guild, such as a new Ready event ([Standby::wait_for_event]). Each method also has a stream variant.

To use Standby it must process events, such as in an event loop of events received by the gateway. Check out the [Standby::process] method.

When to use futures and streams

[Standby] has two variants of each method: a future variant and a stream variant. An example is [Standby::wait_for_message], which also has a [Standby::wait_for_message_stream] variant. The future variant is useful when you want to oneshot an event that you need to wait for. This means that if you only need to wait for one message in a channel to come in, you'd use the future variant. If you need to wait for multiple messages, such as maybe all of the messages within a minute's timespan, you'd use the [Standby::wait_for_message_stream] method.

The difference is that if you use the futures variant in a loop then you may miss some events while processing a received event. By using a stream, you won't miss any events.

Examples

At a glance

Wait for a message in channel 123 by user 456 with the content "test":

use twilight_model::{
    gateway::payload::incoming::MessageCreate,
    id::Id,
};
use twilight_standby::Standby;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let standby = Standby::new();

    let channel_id = Id::new(123);

    let message = standby.wait_for_message(channel_id, |event: &MessageCreate| {
        event.author.id.get() == 456 && event.content == "test"
    }).await?;

    Ok(())
}

A full example

A full sample bot connecting to the gateway, processing events, and including a handler to wait for reactions:

use futures_util::StreamExt;
use std::{env, sync::Arc};
use twilight_gateway::{Event, Intents, Shard, ShardId};
use twilight_model::{
    channel::Message,
    gateway::payload::incoming::ReactionAdd,
};
use twilight_standby::Standby;

#[tokio::main]
async fn main() -> anyhow::Result<()> {
    let token = env::var("DISCORD_TOKEN")?;

    // Start a shard connected to the gateway to receive events.
    let intents = Intents::GUILD_MESSAGES | Intents::GUILD_MESSAGE_REACTIONS;
    let mut shard = Shard::new(ShardId::ONE, token, intents);

    let standby = Arc::new(Standby::new());

    loop {
        let event = match shard.next_event().await {
            Ok(event) => event,
            Err(source) => {
                tracing::warn!(?source, "error receiving event");

                if source.is_fatal() {
                    break;
                }

                continue;
            }
        };

        // Have standby process the event, which will fulfill any futures
        // that are waiting for an event.
        standby.process(&event);

        match event {
            Event::MessageCreate(msg) if msg.content == "!react" => {
                tokio::spawn(react(msg.0, Arc::clone(&standby)));
            },
            _ => {},
        }
    }

    Ok(())
}

// Wait for a reaction from the user who sent the message, and then print it
// once they react.
async fn react(msg: Message, standby: Arc<Standby>) -> anyhow::Result<()> {
    let author_id = msg.author.id;

    let reaction = standby.wait_for_reaction(msg.id, move |event: &ReactionAdd| {
        event.user_id == author_id
    }).await?;

    println!("user reacted with {:?}", reaction.emoji);

    Ok(())
}

For more examples, check out each of the methods on [Standby].

Dependencies

~4–10MB
~168K SLoC