Closed DrChic0 closed 3 months ago
has happened in the past when the discord bot software i use fails to read some payload from discord
kinda hard to find which one(s) tho
as a workaround you can remove all unnecessary perms from your bot or put it in a discord server that has much less activity
Alright, I'll give it a try.
im pretty sure its also related to u not using an up-to-date version of zenith. most likely you're still on zenith for 1.20.1 which has been long deprecated. the line numbers in your exception match that version.
you can update to zenith for 1.20.4 or 1.21 using the channel
command. you can still connect with a 1.20.1 client and connect to 1.20.1 servers with the built-in viaversion.
modern versions have updated discord bot code and force bot restarts even if the logout fails there.
This error only happens after the bot has been in the 2b2t queue for a few hours, this bot is running within Ubuntu using a VPN and in a Hyper-v cluster with 3 other VMs that do the exact same as this one and are setup the same way (they don't have this error).
Happens after a few hours of been online
Happens when I try to restart it using bot commands
The only few ways of fixing this is to:
This problem causes the discord bot to not be online on discord, the only to see what its doing is to remote into the machine or view the server through minecraft.