-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AutoMod MentionSpam Rule Error #9287
Comments
Cannot reproduce. Provided code sample works perfectly fine. Tested both disabling and enabling on 14.8.0 and d1ebe4a. After checking the code, I cannot see where this would fail: discord.js/packages/discord.js/src/structures/AutoModerationRule.js Lines 243 to 245 in d1ebe4a
discord.js/packages/discord.js/src/structures/AutoModerationRule.js Lines 143 to 145 in d1ebe4a
discord.js/packages/discord.js/src/managers/AutoModerationRuleManager.js Lines 169 to 199 in d1ebe4a
The data in your error is all correct. Therefore, I can only theorise that your provided code sample is not what you are actually doing, and you have reassigned the id in some way you have not shown. |
The code sample is exactly what I'm using and it worked just fine for all other rule types. |
Definitely not a client-side issue if the API is returning it! If that's the case, then Discord thinks you do not have one, which is odd... What is the output of |
Looks normal to me. Still running into the error. Here's
|
Honestly not sure at this point. If both the client and API can't do such an action, then it's not related to discord.js. Sounds more like a Discord issue. I'd probably try deleting the rule and recreating it and see if that works. |
Which package is this bug report for?
discord.js
Issue description
When attempting to modify the
MentionSpam
trigger type ofAutoModerationRule
(Block Mention Spam automod rule), methods are returning a 404 API error. All other trigger types for automod rules work without error.Code sample
Package version
14.8.0
Node.js version
18.13.0
Operating system
No response
Priority this issue should have
Medium (should be fixed soon)
Which partials do you have configured?
Not applicable (subpackage bug)
Which gateway intents are you subscribing to?
Not applicable (subpackage bug)
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered: