Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

select_menus - Fixed spelling of "Deferred" #461

Merged
merged 1 commit into from Mar 9, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions DisCatSharp.Docs/articles/topics/components/select_menus.md
Expand Up @@ -100,15 +100,15 @@ When any select menu is pressed, it will fire the [ComponentInteractionCreated](

In the event args, `Id` will be the id of the select menu you specified. There's also an `Interaction` property, which contains the interaction the event created. It's important to respond to an interaction within 3 seconds, or it will time out. Responding after this period will throw a `NotFoundException`.

With select menus, there are two new response types: `DefferedMessageUpdate` and `UpdateMessage`.
With select menus, there are two new response types: `DeferedMessageUpdate` and `UpdateMessage`.
using `DeferredMessageUpdate` lets you create followup messages via the [followup message builder](xref:DisCatSharp.Entities.DiscordFollowupMessageBuilder).

You have 15 minutes from that point to make followup messages. Responding to that interaction looks like this:

```cs
client.ComponentInteractionCreated += async (s, e) =>
{
await e.Interaction.CreateResponseAsync(InteractionResponseType.DefferedMessageUpdate);
await e.Interaction.CreateResponseAsync(InteractionResponseType.DeferedMessageUpdate);
// Do things.. //
}
```
Expand Down