Open
Conversation
There was an off-by-one error in many of them: "$1" instead of "$0". That caused them to require two arguments when they need only one. "$args" now also requires no arguments, which makes a lot of the aliases more useful.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JavaCord is not maintained anymore and seems to be causing us some trouble.
With these changes, messages from Discord should show the correct display name of the sender, but mentions should consistently not be resolved (so all of them look like
<@user id>; this is how it is intended to work right now, but apparently JavaCord does something weird with them). We should work on a better parser later that can resolve mentions.