Create debugging variant of /rquote #65

New issue

Closed

opened 2025-10-20 12:38:00 -04:00 by sirdog3355 · 1 comment

sirdog3355 commented

2025-10-20 12:38:00 -04:00

(Migrated from github.com)

Right now, in order for me to ascertain how /rquote will handle a particular message, I have to make a Frankenstein's monster copy of it on the Discord server I use as a development environment, and then just run /rquote repeatedly until it picks it.

A much, much better idea is to have a /rquote-test command that lets me specify the message by it's ID. This command can then output everything as normal, but I can also have it give me all kinds of debugging information in a separate embed.

This command will need to be locked down since it will be completely outing the person who said the quote and who quoted it, something Fleff is not okay with given /rquote can run in channels that are accessible to people who can't see #out-of-context.

Couple of ways to handle this:

Lock it down to a channel only moderators can traditionally see.
Lock it down by role and simply have the output be ephemeral.
Lock it down by role and require individual to confirm the action (if possible)

Right now, in order for me to ascertain how `/rquote` will handle a particular message, I have to make a Frankenstein's monster copy of it on the Discord server I use as a development environment, and then just run `/rquote` repeatedly until it picks it. A much, much better idea is to have a `/rquote-test` command that lets me specify the message by it's ID. This command can then output everything as normal, but I can also have it give me all kinds of debugging information in a separate embed. This command will need to be locked down since it will be completely outing the person who said the quote and who quoted it, something Fleff is not okay with given `/rquote` can run in channels that are accessible to people who _can't_ see `#out-of-context`. Couple of ways to handle this: - Lock it down to a channel only moderators can traditionally see. - Lock it down by role and simply have the output be ephemeral. - Lock it down by role and require individual to confirm the action (if possible)

sirdog3355 commented

2025-10-21 21:12:54 -04:00

(Migrated from github.com)

Resolved by #66