'undefined' / no name custom commands | Ticket Tool Support | Page 1

woven wave Mar 16, 2024, 4:06 PM

#

We created a custom command in our server to send a message when a ticket has been inactive for 30 minutes.
This command had no name (since it wasn't intended to be set off manually).
When someone said "undefined" it caused the command to trigger.

--

Reproduction steps:

create a command and leave the trigger box blank (https://fb.crcle.xyz/i/2024/03/brave_0hMyDwh8nH.png)
say "undefined" in your server and the bot will reply (https://fb.crcle.xyz/i/2024/03/DiscordCanary_mEkk00X51P.png)

#

not particularly a bug since i guess the command trigger is indeed undefined and the bot is just doing what its told but not a behaviour the average user expects

primal ruin Mar 16, 2024, 4:11 PM

#

Was able to reproduce. Bumping to @round pebble

#

In the meantime, you can set the trigger to anything (as weird as possible, or with special characters) and enable ADMIN ONLY - That will highly reduce the chances of someone accidentally triggering it

round pebble Mar 16, 2024, 4:15 PM

#

primal ruin Was able to reproduce. Bumping to <@279639060996292609>

Interesting.. if no command trigger is supplied it reverts to undefined.. that's not intended..

rugged dune Mar 18, 2024, 12:49 AM

#

Yeah that'll be the library providing the default presumably - best to just ignore commands if name is undefined 😄

#'undefined' / no name custom commands