Fix FakeNitro patch for FakeStickers #2958
Closed
Conversation
This file contains 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
Fix FakeNitro patch for rendering FakeStickers This patch might be a little sensitive but it doesn't currently conflict with any other code in the module and I don't think it will
fres621
changed the title
|
Done by 4e89352, thanks regardless! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix FakeNitro patch for rendering FakeStickers
This patch might be a little sensitive but it doesn't currently conflict with any other code in the module and I don't think it will
An alternative less sensitive patch would be a lookbehind for the function's name "renderAttachments"
To test this patch enable these 3 options and send a FakeNitro's FakeSticker
If the patch applied correctly it should look like a regular FakeSticker in the message