yuudachi
yuudachi copied to clipboard
Naval-Base
Discord moderation bot
Original is 2 embeds, forward is then message content + embed (author could be omitted, if the action can only be done by the same user, should follow the format...
It could be computed with an expiration timestamp and message timestamp, but very uncomfortable. Seeing the duration of a timeout when looking up history can be useful in judging escalation...
> My pt-BR when? 🥲 ## How? - i18next now supports a new namespace (fancy name for file) called `commands.json`, which is accessible through the `commands:` prefix under any valid...
Reports can get spammy in case of an raid or other massive event - Automatically: when an anti-raid-nuke is running - Manual: a command like `/reports toggle` - [x] #1139
## Bug? When two moderators action the same user the bot does not check anything after the confirmation screen causing duplicate cases (see examples below) ## Proposed solution: Add a...
## Possible causes: The bot failing to link the post_id to the report, making the `upsertReportLog` function to create a new channel to resolve the report on. > https://github.com/Naval-Base/yuudachi/blob/main/packages/yuudachi/src/functions/logging/upsertReportLog.ts#L49-L56 
Paginate the history command to allow mods to view `Reports` and `Cases` in the same command/context
Message references are becoming a native DIscord feature, depending on how much this covers our use cases, we should consider removing the repost feature and employing the (allegedly) immutable nature...
Currently threshold 3, but threat actors stopped spamming this specific scam While automod catches most, outliers exist: see Report 759
This is especially relevant for references (example: action applied by A, after the fact a reference report is opened that is tacked to the action by B)