We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The recent merge #472 messed up the ability for /audit to retrieve the actual users who used the actions against the target.
/audit
See the following example:
The bug comes from exchanging the previously correct
jda.retrieveUserById(action.authorId())
by the wrong
jda.getUserById(action.authorId());
Latter only checks the JDA cache instead of asking Discord. The cache is rarely reliable (only for the list of guilds).
Changing this back is fairly simple, but requires to make the code properly async using RestAction.
RestAction
The text was updated successfully, but these errors were encountered:
FYI @Taz03
(also, please dont forget to test on the test server before deploying, thanks)
Sorry, something went wrong.
Zabuzard
Successfully merging a pull request may close this issue.
The recent merge #472 messed up the ability for
/audit
to retrieve the actual users who used the actions against the target.See the following example:
Reason
The bug comes from exchanging the previously correct
by the wrong
Latter only checks the JDA cache instead of asking Discord. The cache is rarely reliable (only for the list of guilds).
Changing this back is fairly simple, but requires to make the code properly async using
RestAction
.The text was updated successfully, but these errors were encountered: