Skip to content
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

fix: Cooldowns #78

Merged
merged 1 commit into from
Sep 27, 2020
Merged

Conversation

Gerrit0
Copy link
Contributor

@Gerrit0 Gerrit0 commented Sep 26, 2020

Stop relying on pinned messages to figure out who owns a channel. We have a database, and should use it.

This seems to work properly, I was able to set the timeout to a low number and observe that my cooldown was removed.

Just in case this doesn't work, and to fix users whose cooldowns are currently broken, also adds (again) the !cooldown command. It can probably be removed after a couple weeks of no bugged cooldowns.

Stop relying on pinned messages to figure out who owns a channel. We have a database, and should use it.
@Gerrit0 Gerrit0 mentioned this pull request Sep 26, 2020
@robertt
Copy link
Member

robertt commented Sep 27, 2020

Perfect, thanks!

@robertt robertt merged commit 7d47cdb into typescript-community:master Sep 27, 2020
@Gerrit0 Gerrit0 deleted the maybe-fix-cooldowns branch September 27, 2020 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants