-
Notifications
You must be signed in to change notification settings - Fork 41
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
[ISSUE] Quickmaths and unscramble show the name of the person who sent the ! message, not the winner #258
Comments
This looks like your first issue! |
Heya, yeah I'm aware that about this bug, it's not really major or game breaking so it's not really on high priority list. I'm gonna fix it once I get time, but this year I've been really busy with life and other projects, so there have been barely any updates to the bot, you probably noticed that as well. I was gonna do big revamp of the bot this summer, but got internship and then SkyCrypt rewrite started, and also SkyHelper refactors and yeah ;-;. Life got in a way.. I might be able to fix this next weekend but I don't promise anything.
To be honest, I have no idea what could cause that. It could be any of the API calls, can you provide the console error when that occurs? It could be from event notifier, to some command, to update checker.
tysm <3 |
will do tmrw, it affects a bit of commands like !racoon and stuff, which I assume are supposed to have images? not too sure |
You might've put client token instead of clientId in the config. Also either way it wouldn't have worked cuz Hypixel blocked imgur links, I did find a way to solve that, but still WIP |
Mostly in title, but it's simply the bot not getting the name of who won, but instead the name of who sent it first (even if they aren't who answered it)
(also while am here, anu reason why this is broken)
I would also like to give credit, this bridge bot is quite ltrly one of the best currently available, I would spare a dono if I could pay online (algeria problems smh), that's the first time I considered that, that's how good this is xo!
The text was updated successfully, but these errors were encountered: