#Modal Command Help
1 messages · Page 1 of 1 (latest)
- Interactivity is an official extension
- You can't respond to an modal with deferred message update as this type is for message components only afaik
DSharpPlus.Entities.DiscordInteractionResponseType.DeferredChannelMessageWithSource
Summary
Acknowledges an interaction to edit to a response later. The user sees a "thinking" state.
Declaration
public const DiscordInteractionResponseType DeferredChannelMessageWithSource = DiscordInteractionResponseType.DeferredChannelMessageWithSource;
or
DSharpPlus.Entities.DiscordInteractionResponseType.ChannelMessageWithSource
Summary
Responds to the interaction with a message.
Declaration
public const DiscordInteractionResponseType ChannelMessageWithSource = DiscordInteractionResponseType.ChannelMessageWithSource;
also i recommend to not mix and match in this case
if you use interactivity just use the interaction you get in the result
so you dont need the event handler in this case
nope
your interactivity result contains the interaction which you also get in the event handler
interactivity is for writing complex command flows in one place
yeah
the result you get contains the event args which you have to use
similar to your event handler
https://github.com/Plerx2493/Mads/blob/master/ModularAssistentForDiscordServer/Commands/Slash/moveEmoji.cs
heres an example of a more complex command flow using interactivity, this might help to understand it
No problem
That's also kinda on us, our docs for interactivity are a bit out of date
did you respond to the interaction in the interactivity result (response in your code above)?
you have to acknolwedge the interaction which is in the interactivity result
modalSubmission contains a new interaction which was created when the modal was submitted. That interaction has to be answered