Random command "recognition" #48
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
backmeupplz/banofbot#48
Loading…
Reference in a new issue
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?
Banofbot "recognizes" commands in random context or situations. This leading to not intended command execution or deleted messages (when as not-admin in "lock"-mode).
Examples (with /lock, but happening with all Banofbot commands) :
command is "hidden" in a message sent in the group:
".. to explain how bots work. So you could use the /lock-command to toggle wether users are allowed to ..."
in an other command:
"/addblocklist" (or everything like e.g. "/sbjelklockrandjk")
(happend in a group where i got another bot using this command. NOT an issue when not beeing to lazy and fully adressing as /addblocklist@MissRose_bot)
unintended banvote:
(reply to someone whilst discussing the behavior of Banofbot)
" ... yes, that's the intended part. Also working with other commands as (slash) limit , (slash) help oder (slash) help@banofbot."
One more "option" - also "recognizing" things like
"/ramdomtextlockrandomword@banofbot"
Hm, interesting issue. Feel free to submit a pull request fixing it
Fair proposal - but im just an (active) user without knowhow to code a fix.
Thank you for taking the time to report this, and sorry it sat without an answer for so long. I'm cleaning up old issues and closing this one because it has been inactive for a long time. If it still affects you, please open a new issue with the current details and I'll take a look.