heartbeats arent responding.

[elder tree]

• What's your exact discord.js npm list discord.js and node node -v version?
• Post the full error stack trace, not just the top part!
• Show your code!
• Explain what exactly your issue is.
• Not a discord.js issue? Check out #useful-servers.

| `-- [email protected] deduped
+-- [email protected]
| `-- [email protected] deduped
| `-- [email protected] deduped
`-- [email protected]

Node v16.17

• Node v16
My code has no issues, because it was working and then of a few minutes just turns off
Well, i have a problem on my bot, my bot doesnt become online, and when i see my console the heartbeats just stops.

[white plover]

Please add the following code to your code base outside of any other event listeners and provide the full log output relevant to your issue.

client
    .on("debug", console.log)
    .on("warn", console.log)

• Note: if you initialize your Client as bot or other identifiers you need to use these instead of client
• If the output is too long to post consider using a bin instead: gist | hasteb.in | sourceb.in | hastebin

[elder tree]

i just put that

thats the because i see heartbeats

pls help

[loud hedge]

and provide the full log output relevant to your issue.

[elder tree]

well, no error is in my output

just the heartbeats are stopping

i mean there is no more heartbeat log

[loud hedge]

Either show them or we can’t help you. Your choice

[elder tree]

Okay

[elder tree]

This log is showing like 30 minutes

and the bot goes offline

[loud hedge]

Show the end of that output, not the start. The relevant part is what happens when it stops…

[elder tree]

thats all...

Nothing more...

[loud hedge]

Then what’s below that? A command prompt? Anything? Because judging from that screenshot node is still running

[elder tree]

Yeah, node its still running

the heartbeats are not running

i will send the full screenshoot

Look at the time

No more heartbeats

[loud hedge]

Scroll down please…

[elder tree]

okay

[elder tree]

Nothing

[loud hedge]

Do you by any chance remove the debug listener in your ready event?

[elder tree]

what is that

[loud hedge]

The thing that makes your bot print those heartbeats in the first place… client.on('debug', …)

[elder tree]

i didnt

[loud hedge]

Could you show your ready event code please?

[elder tree]

Okay

[elder tree]

client.on('ready', () => {
  client
  .on("debug", console.log)
  .on("warn", console.log)
    console.log(`[ ✔️ ] Estoy en ${client.guilds.cache.size} servidores!`)
    console.log('[ :heavy_check_mark: ] Al parecer no hay errores, Todo listo e iniciado correctamente.')
    console.log('[ GatoOS#5836 ]')

 





 
  
   
    
    
     client.user.setStatus('idle');
     client.user.setActivity('gs!help • OS'); 
})```

index.js

[loud hedge]

Wait, why do you add the listeners inside of the ready event? And how did it print the heartbeats before it was ready then?

You have another .on('debug' somewhere

[elder tree]

Yes

I have in the last line

Obviusly before token

[loud hedge]

Don’t make me drag each single bit of information out of you… paste your whole file into a bin, only remove sensible information (like your token) and send the link…

[elder tree]

Okay

[elder tree]

Cuadro i'm also spanish if you need to and ill translate, the error becomes from shards?

[elder tree]

what else can it be coming from? lol