Advertisement
Guest User

Untitled

a guest
Sep 17th, 2019
321
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.79 KB | None | 0 0
  1. I am ready!
  2. timers.js:479
  3. throw new ERR_INVALID_CALLBACK();
  4. ^
  5.  
  6. TypeError [ERR_INVALID_CALLBACK]: Callback must be a function
  7. at setInterval (timers.js:479:11)
  8. at Client.client.on (C:\Users\Tim\Downloads\mcstatusbot-master\mcbot.js:114:3)
  9. at Client.emit (events.js:203:15)
  10. at WebSocketConnection.triggerReady (C:\Users\Tim\Downloads\mcstatusbot-master\node_modules\discord.js\src\client\websocket\WebSocketConnection.js:125:17)
  11. at WebSocketConnection.checkIfReady (C:\Users\Tim\Downloads\mcstatusbot-master\node_modules\discord.js\src\client\websocket\WebSocketConnection.js:141:61)
  12. at GuildCreateHandler.handle (C:\Users\Tim\Downloads\mcstatusbot-master\node_modules\discord.js\src\client\websocket\packets\handlers\GuildCreate.js:13:31)
  13. at WebSocketPacketManager.handle (C:\Users\Tim\Downloads\mcstatusbot-master\node_modules\discord.js\src\client\websocket\packets\WebSocketPacketManager.js:103:65)
  14. at WebSocketConnection.onPacket (C:\Users\Tim\Downloads\mcstatusbot-master\node_modules\discord.js\src\client\websocket\WebSocketConnection.js:333:35)
  15. at WebSocketConnection.onMessage (C:\Users\Tim\Downloads\mcstatusbot-master\node_modules\discord.js\src\client\websocket\WebSocketConnection.js:296:17)
  16. at WebSocket.onMessage (C:\Users\Tim\Downloads\mcstatusbot-master\node_modules\ws\lib\event-target.js:120:16)
  17. npm ERR! code ELIFECYCLE
  18. npm ERR! errno 1
  19. npm ERR! minecraft-server-bot@1.2.1 start: `node mcbot.js`
  20. npm ERR! Exit status 1
  21. npm ERR!
  22. npm ERR! Failed at the minecraft-server-bot@1.2.1 start script.
  23. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  24.  
  25. npm ERR! A complete log of this run can be found in:
  26. npm ERR! C:\Users\Tim\AppData\Roaming\npm-cache\_logs\2019-09-18T03_45_15_823Z-debug.log
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement