pkalab / DiscordBot

MIT License
0 stars 0 forks source link

Running the bot failed #4

Open njmurarka opened 3 years ago

njmurarka commented 3 years ago

node bot2.js (node:48709) UnhandledPromiseRejectionWarning: Error [TOKEN_INVALID]: An invalid token was provided. at WebSocketManager.connect (/Users/loquitus/src/gitcoin/bots/pkalab/DiscordBot/node_modules/discord.js/src/client/websocket/WebSocketManager.js:133:26) at Client.login (/Users/loquitus/src/gitcoin/bots/pkalab/DiscordBot/node_modules/discord.js/src/client/Client.js:223:21) (Use node --trace-warnings ... to show where the warning was created) (node:48709) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:48709) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

pkalab commented 3 years ago

Hi @njmurarka! In .env file in TOKEN variable should be Token string from Discord. You can find it in Discord - Developer Portal - Bot Application that you created - Bot section on the left - Click Reveal Token

njmurarka commented 3 years ago

Yes. That's what I did.

The "node bot2.js" worked when I did this in Ubuntu instead of MacOS.

The bot user on Discord is also showing a green dot.

But I can't get the bot to do anything. "/" does not show your bot in the list.

I tried to install your bot on two different Discord servers and in both cases, the Bot is not responding to any / commands and is not even showing up as a bot.

njmurarka commented 3 years ago

Please clarify. Need to review and close this bounty pretty soon.

pkalab commented 3 years ago

Hi @njmurarka there was an issue with package.json. Try to run it again. I will update tests and documents