#Client is in a strange ready/not ready state

1 messages · Page 1 of 1 (latest)

cinder hollow

https://github.com/ThreadedTickets/Bot/tree/migrate-to-bridge-v2

sharding file: https://github.com/ThreadedTickets/Bot/blob/migrate-to-bridge-v2/src/cluster.ts

Using worker processes, all the socket connections are working as intended

index.ts: https://github.com/ThreadedTickets/Bot/blob/migrate-to-bridge-v2/src/index.ts

All 3 ways of logging the token return the correct token

ready event: https://github.com/ThreadedTickets/Bot/blob/migrate-to-bridge-v2/src/events/ready.ts

The console.log in here logs this: READY null false 0 Screws

Error: (I get this error whenever my bot tried to make an api call. )

Unhandled Rejection Expected token to be set for this request, but none was present
Error: Expected token to be set for this request, but none was present

The screenshot is of the bridge server, showing that the bot is reporting ready
I am running the bot with IS_PROD=false so none of the prod functions are being called. the set status file is also not being run as i have not set the env variables
There are 0 errors when the bot actually logs in using client.login() and no logs showing that it gets disconnected

any other info that you might want just ping me and i can add it in