-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
[Bug} All Stcikers Dismissed When Posted #8
Comments
I get this issue when SimpleDiscordCrypt is loaded, since it messes with stuff. I usually just disable SDC for this, which can be done by turning on/off Hardware Acceleration cause that restarts discord without SDC. If that isn't the case for you then I will look into it further |
@riolubruh I tried what you said, for some reason my Hardware Acceleration was on, but even after turning it off, I still get the same ClydeBot message popup. |
I managed to get stickers working with an unconventional workaround. I loaded "FreeStickersv1.2.1by An0" alongside NitroPerks. At first, testing stickers gave the same result, ClydeBot message. What fixed the issue was enabling NitroPerks "FreeStickers Compatibility Mode". For peace of mind, I was testing NitroPerks loaded by itself initially. The reason I wanted to use your plugin is because it was a All-in-one solution. So I unloaded "FreeStickersv1.2.1by An0" & "Freemojiv1.7.3by Qb, An0" before testing NitroPerks. I also tested with "FreeStickersv1.2.1by An0" unloaded and NitroPerks "FreeStickers Compatibility Mode" enabled but all my stickers became greyed out. But with NitroPerks "FreeStickers Compatibility Mode" enabled and then loading "FreeStickersv1.2.1by An0" stickers began to work with NO ClydeBot message. I figured I'd share this with you in case you wanted to scour "FreeStickersv1.2.1by An0" to see what comparison you might draw to find a solution. |
Ohhh lol |
Improved the README to guide people to the FreeStickers plugin. |
When trying to post any sticker the ClydeBot dismiss message appears so the sticker posted isnt actually posted.
The text was updated successfully, but these errors were encountered: