Commands don't trigger with newline starts

If a message is sent with a newline immediately after the command's name it won't be triggered. For example:
!say
{
"content": "content",
}
!say
{
"content": "content",
}
Wouldn't trigger the say command. However:
!say(empty space)
{
"content": "content",
}
!say(empty space)
{
"content": "content",
}
Does trigger the command. Is there any workaround for this? Thanks!
Solution:
No... I don't think this is gonna work. It goes pretty much against how we parse messages and commands. Might I recommend using Slash commands instead and showing the user a TextInput modal component which allows for multiline string input that way?...
Jump to solution
2 Replies
Solution
Favna
Favna3mo ago
No... I don't think this is gonna work. It goes pretty much against how we parse messages and commands. Might I recommend using Slash commands instead and showing the user a TextInput modal component which allows for multiline string input that way?
//
//OP3mo ago
Ah, sadge. I got a slash command version already working, I add both options to every command, thanks for the suggestion though!

Did you find this page helpful?