You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With our recent chat trolls with SmokeDetector, we've found problems with !!/stappit. Since Undo has added an auto-restarting feature, !!/stappit doesn't work. Thus, Smokey keeps posting...
I think an easy solution to this would be to create !!/block {time} and !!/unblock commands. !!/block {time} would stop Smokey from posting until this given time (in minutes) is up. It could just be a simple check when posting, i.e. if isBlocked: return else: post. !!/unblock would just make it eligible to post again.
Is this a good solution to the problem? Feedback welcome.
The text was updated successfully, but these errors were encountered:
You should have a 15 minute max block so people don't abuse it. 15 isn't a lot but it is comparable to the timer with the hot tub at hotels: you can easily enable it for a little bit more. If you're having problems with people writing scripts to keep it blocked, you should have some maximum commands usable in a few hours.
Also: add an automatic continue of the ban if the chatroom is extremely active... That might always trigger with Tavern...
One more thing: you should either store the "missed" posts and post them when the ban is over or just have a site where you can view everything, even stuff that's deleted in chat/blocked. That would solve the whole issue of infinite bans.
@Annonomus-Penguin This would be limited to certain people, so abuse isn't a major problem. I'm thinking a cap of a few hours though... maybe 5? I'm not sure. Also, re your missed posts point: this is mainly to prevent Smokey from being abused, so we probably wouldn't want to post the missed posts.
With our recent chat trolls with SmokeDetector, we've found problems with
!!/stappit
. Since Undo has added an auto-restarting feature,!!/stappit
doesn't work. Thus, Smokey keeps posting...I think an easy solution to this would be to create
!!/block {time}
and!!/unblock
commands.!!/block {time}
would stop Smokey from posting until this given time (in minutes) is up. It could just be a simple check when posting, i.e.if isBlocked: return else: post
.!!/unblock
would just make it eligible to post again.Is this a good solution to the problem? Feedback welcome.
The text was updated successfully, but these errors were encountered: