No error and bot not come online | discord.js - imagine an app | Page 1

tired yoke Jan 12, 2022, 1:57 PM

#

use client.on

next comet Jan 12, 2022, 1:57 PM

#

Ok

next comet Jan 12, 2022, 1:58 PM

#

tired yoke use `client.on`

Still not working

tired yoke Jan 12, 2022, 1:58 PM

#

show again the whole code

next comet Jan 12, 2022, 1:58 PM

#

That is whole code

tired yoke Jan 12, 2022, 1:58 PM

#

as I said before, use client.on

next comet Jan 12, 2022, 1:59 PM

#

const { Client, Intents } = require('discord.js');
const token = process.env['TOKEN'];

const client = new Client({ intents: [Intents.FLAGS.GUILDS] });

client.on('ready', () => {
client.user.setPresence({ activities: [{
  name: 'Oto in' + client.guilds.size + 'with' + client.users.size,
  type: 'PLAYING',
}], status: 'idle' });
console.log('Ready!');
});

client.login(token);

#

See

#

@tired yoke

tired yoke Jan 12, 2022, 2:00 PM

#

does ready event gets fired at all? put a breakpoint at client.user.setPresence, or a console.log above it

next comet Jan 12, 2022, 2:00 PM

#

Ok

tired yoke Jan 12, 2022, 2:03 PM

#

this error should not be triggered by the code changes suggested by me. if you changed the code again, please show it

next comet Jan 12, 2022, 2:03 PM

#

Again that old error

tired yoke Jan 12, 2022, 2:03 PM

#

do a console.log(process.env['TOKEN'])

next comet Jan 12, 2022, 2:04 PM

#

const { Client, Intents } = require('discord.js');
const config = process.env;

const client = new Client({ intents: [Intents.FLAGS.GUILDS] });

client.on('ready', () => {
  
client.user.setPresence({ activities: [{
  name: 'Oto in' + client.guilds.size + 'with' + client.users.size,
  type: 'PLAYING',
}], status: 'idle' });
  
console.log('Ready!');
});

client.login(config.TOKEN);

tired yoke Jan 12, 2022, 2:05 PM

#

follow at least one of my steps:

does ready event gets fired at all? put a breakpoint at client.user.setPresence, or a console.log above it

do a console.log(config.TOKEN)

next comet Jan 12, 2022, 2:05 PM

#

tired yoke do a `console.log(process.env['TOKEN'])`

Done not logging anything

tired yoke Jan 12, 2022, 2:06 PM

#

then that's the problem. you're not logging in using a valid token

next comet Jan 12, 2022, 2:06 PM

#

no token is correct

tired yoke Jan 12, 2022, 2:06 PM

#

likely you're not setting the env variable TOKEN

next comet Jan 12, 2022, 2:07 PM

#

Let me show you full code

#

const { Client, Intents } = require('discord.js');
const config = process.env;

const client = new Client({ intents: [Intents.FLAGS.GUILDS] });

client.on('ready', () => {
console.log('Ready!');
client.user.setPresence({ activities: [{
  name: 'Oto in' + client.guilds.size + 'with' + client.users.size,
  type: 'PLAYING',
}], status: 'idle' });
});
 console.log(process.env['TOKEN'])

client.login(config.TOKEN);

const express = require('express');
const app = express();
const port = 3000;
app.use(express.static(__dirname));
app.listen(port);

tired yoke Jan 12, 2022, 2:08 PM

#

if the line with console.log(process.env['TOKEN']) doesn't show anything, then your env variable TOKEN is empty

#

since it is empty, it is considered invalid

next comet Jan 12, 2022, 2:09 PM

#

Token is logged in console

#

Is any error in intents

tired yoke Jan 12, 2022, 2:09 PM

#

next comet Done not logging anything

then why you said it does not log anything?

next comet Jan 12, 2022, 2:09 PM

#

That's time it not logged

#

It looged after 5 sec

#

Is it possible that error is in intents

tired yoke Jan 12, 2022, 2:10 PM

#

you are giving vague information, making the helping process harder

next comet Jan 12, 2022, 2:10 PM

#

Sorry

tired yoke Jan 12, 2022, 2:10 PM

#

next comet It looged after 5 sec

what about now? does that specific line logs the token?

tired yoke Jan 12, 2022, 2:11 PM

#

next comet Is it possible that error is in intents

no, intents have nothing to do with logging in

next comet Jan 12, 2022, 2:11 PM

#

One line is logging token

#

Only ex: Owjjsjsuwisoso

#

Like this

next comet Jan 12, 2022, 2:12 PM

#

tired yoke no, intents have nothing to do with logging in

Then I am using Correct Activity name what

tired yoke Jan 12, 2022, 2:12 PM

#

next comet Only ex: Owjjsjsuwisoso

i don't understand what that means.. Owjjsjsuwisoso is the token?

next comet Jan 12, 2022, 2:12 PM

#

No

#

I am not telling you token it is example

tired yoke Jan 12, 2022, 2:13 PM

#

ah, ok. you have to know that the format of the token is incorrect, if it really looks similar to that

#

do you still get the invalid token error?

next comet Jan 12, 2022, 2:13 PM

#

No it not looks like that

#

No

next comet Jan 12, 2022, 2:13 PM

#

tired yoke do you still get the invalid token error?

No

#

No error coming

tired yoke Jan 12, 2022, 2:14 PM

#

and bot is not online? (it can take some secs for the bot to come online)

next comet Jan 12, 2022, 2:14 PM

#

tired yoke and bot is not online? (it can take some secs for the bot to come online)

Yes bot is not online

tired yoke Jan 12, 2022, 2:14 PM

#

i guess not even console.log('Ready!'); shows anything

next comet Jan 12, 2022, 2:15 PM

#

Yes it is also not showing

tired yoke Jan 12, 2022, 2:16 PM

#

temporarily delete all express stuff (5 lines), and run the code again

next comet Jan 12, 2022, 2:17 PM

#

Ok

#

const { Client, Intents } = require('discord.js');
const config = process.env;

const client = new Client({ intents: [Intents.FLAGS.GUILDS] });

client.on('ready', () => {
console.log('Ready!');
client.user.setPresence({ activities: [{
  name: 'Oto in' + client.guilds.size + 'with' + client.users.size,
  type: 'PLAYING',
}], status: 'idle' });
});

client.login(config.TOKEN);

///const express = require('express');
///const app = express();
///const port = 3000;
///app.use(express.static(__dirname));
///app.listen(port);

#

Done

#

Still not working

#

@tired yoke

#No error and bot not come online