discord-bot | The magic behind xenia-bot on Discord | Bot library

You can use

This means that your bot is missing permissions to (presumably) send messages on that server. You can prevent it from crashing by adding a .catch statement after sending the message like this:

I have found the problem, the function was returning a promise, so I just had to do LM.Message.delete().

Perhaps, try changing

The voiceStateUpdate is emitted whenever a member changes their voice state. In some cases, e.g. when someone leaves a voice channel, newVoiceState.channel will be null and if you try to read a property of this, it will throw a TypeError.

You'll need to compare the voiceStates before and after the update to figure out what triggered the voiceStateUpdate event. I've just added some code below with a few examples. The following code logs if someone joined/left/switched channels, or if there are other changes like muted/unmuted themselves, started sharing their screen, etc.:

You have to send a PATCH request to /guilds/{guild.id}/members/{user.id} and edit set the communication_disabled_until field to an ISO8601 timestamp which holds the date when the timeout will be disabled.

If you want to remove the timeout, simply set communication_disabled_until to Null

discord-api reference

EDIT Just saw the question's last line about the server being reported as offline when using a number rather than an object. That actually confirms my suspicion below, as you're no longer getting an error from the SDK itself (ie, it seems to be "working," in that it's at least making the network call). I would double-check your address and port number, and ensure the server is accessible from replit.

--- Original response below ---

Difficult to say for sure without knowing the mineutil API you're using, but it looks like you may be sending more than you need to the mineutil.status() function (And if you're using this library, I'm fairly certain you are).

I'm guessing that the following line:

return mineutil.status(SERVER_ADDRESS, { port: SERVER_PORT })

which is sending an object `{port: SERVER_PORT}' as its second parameter, should just be sending the number itself. For example:

Your YDL_OPTIONS is malformed: Instead of providing a dict you're providing a set because you've placed the colons inside of strings.

Instead of {'format : bestaudio', 'noplaylist : True'} you want the -- subtly different, but crucially totally other data structure -- YDL_OPTIONS = {"format": "bestaudio", "noplaylist": True}.

From the discord-api-types README:

You can only import this module by specifying the API version you want to target. Append /v* to the import path, where the * represents the API version.

Thus, your require statement should look something like this: