Closed myde2001 closed 2 years ago
Pictures aren't loading or linking to anything for me
Sorry, fixed
Where was your name on the wishes by string ?
Where was your name on the wishes by string ?
My name is the third one, but it also happened in the past when I got a character much higher that the min_kak I specified and it was wished by another player, it appears that the wish string is messing the bot.
Is there snipe protection in your server ?
Sent from my iPhone
On Apr 18, 2022, at 10:24 PM, myde2001 @.***> wrote:
Where was your name on the wishes by string ?
My name is the third one, but it also happened in the past when I got a character much higher that the min_kak I specified and it was wished by another player, it appears that the wish string is messing the bot.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
Another reason is that it seems like button are enabled so ensure both discum library and my repo is updated as button support was added recently
Is there snipe protection in your server ?
This are the sniping settings of the MudaeBot in the server:
· Rolls sniping: 0 ($togglesnipe) · Kakera sniping: 0 ($togglekakerasnipe)
Another reason is that it seems like button are enabled so ensure both discum library and my repo is updated as button support was added recently
I have discum 1.4.0, I downloaded the last version of the script right now, but I had the previous one at this last one.
Also I modified the code in this line "sniping = settings.get("sniping_enabled",False)" to prevent claiming rolls from other people.
Also the character of 900ka I got and the bot didn't claim was rolled by me, and the last week happened too with another character of 988ka, in that time I haven't had change the line in the code
For me it seems that the string of "Wished by @username" breaks the bot or something like that.
it searches for your user id not the "wished by" string if you think it only applies to the wish setting then print out content when finds a wished character
you could also test sniping to true and seeing if that the reason things are disabled
you could also test sniping to true and seeing if that the reason things are disabled
I had it in true the first time it happened and it didn’t claim it
it searches for your user id not the "wished by" string if you think it only applies to the wish setting then print out content when finds a wished character
So strange this behavior then
it searches for your user id not the "wished by" string if you think it only applies to the wish setting then print out content when finds a wished character
So strange this behavior then
Hi @myde2001, I have found a strange behaviour, I pointed it out in issue #158. I think that more than pointing out that it does not make a claim, it is pointing out that something changed in the identifiers of the connection to the channel and server. What I did to make it work for me was to put the slash_ids as channel_ids, that way the bot is making the connection and therefore the claim.
"channel_ids":[ channel_ids, slash_ids ], "slash_ids":[ slash_ids ], "slash_guild_ids":[ slash_ids ],
Environment Package Version
Brotli 1.0.9 certifi 2021.10.8 charset-normalizer 2.0.12 colorama 0.4.4 discum 1.4.0 filetype 1.0.10 idna 3.3 pip 22.0.4 requests 2.27.1 requests-toolbelt 0.9.1 setuptools 58.1.0 six 1.16.0 ua-parser 0.10.0 urllib3 1.26.9 websocket-client 0.59.0
But I'm not using the slash ids
if you are using buttons then it might be a discum dependecy issue
Closing since haven't recieved a response. TLDR: Possible issue with discum dependency due to buttons ?? or possible settings issue
It happened two weeks ago when I got a character, and it happened now, I noticed and I claimed it myself
https://i.imgur.com/bQyBVKX.png
https://i.imgur.com/nXVzZzN.png