4 replies

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

S-IaF

Sapphire - Imagine a Framework•7mo ago•

4 replies

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

Jump to solution

Commands don't trigger with newline starts

Similar Threads

Commands don't trigger with newline starts

Similar Threads

Similar Threads

Similar Threads