-
Notifications
You must be signed in to change notification settings - Fork 33
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
why does the bot keep resetting itself? #3
Comments
did you ever find a solution? |
No, I just wrote an autohotkey script that would input each command to
reconfigure the bot
But even that has to be done every few hours
if you figure out anythjng, that would be much appreciated
…On Thu, Dec 16, 2021, 16:02 abhayasood1793 ***@***.***> wrote:
did you ever find a solution?
—
Reply to this email directly, view it on GitHub
<#3 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWEYHVQTCTKKVGACG2UZRXTURJHYBANCNFSM5GM4PMQQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Maybe it’s a problem with your database not persisting. Watch |
That would make sense, the database not persisting. |
In that case, I don't really know, but it seems to be a problem with the people who host the bot. As far as I can tell from the source code, you don't need to host a separate database. |
Yeah I'm not sure either, but thanks for the python 3.7 tip |
Having this issue too, not self-hosting. 🤔 |
After I setup the bot, go through
.enableonjoin
.domainadd [the domain I want to use].org
for some reason it doesn't seem to work if I put the @ in the domain.rolechange Verified
And for a short period of time, maybe a few hours, it works.
But after a few hours, the bot resets itself for .enableonjoin and .domainadd, although it does keep the proper Verified role (or maybe it resets to the default)
Why does it do this?
Is there any way to keep the configuration persistent?
The text was updated successfully, but these errors were encountered: