forked from adam/discord-bot-shtik
cooldowns #38
Labels
No Label
Feature (admin)
Feature (chat)
Platform
Problem
blocked
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: greyn/vassago#38
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
if vassago has had the same command with the same input triggered
x
times overy
seconds (tunex
andy
, obv) in a given channel, go into cooldown.should be a secondary defense against triggering off self, and/or having 2 instances that accidentally trigger each other (e.g., me: "chatgpt" -> shtikbot: "chatgpt is weak" -> magnificent charamote: "chatgpt is weak" -> shtikbot: "chatgpt is weak", etc)
changing the fuck out of this.
new plan!
everything is on a cooldown. telling a joke? adds barely any heat. generating a QR code? adds a significant amount.
...ok cool, why? as a ripcord to prevent infinite loops? in case you add something heavy, like quote-unquote AI? just don't let anyone else touch them, boom done.
although I guess this would be a good proactive prevention against unforseen loops.
safety ripcord: per-channel cooldownto cooldowns