staed / fubuki Goto Github PK

Once added to multiple servers, the bot frequently, but not always, runs into ETIMEDOUT and UnhandledPromiseRejection errors.

The specific error logs are:
(node:xxxx) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Forbidden
(node:xxxx) 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.

and

Request Failed: RequestError: Error: connect ETIMEDOUT [IP_ADDRESS:PORT]

Sometimes, but not always, this error is accompanied by resource starvation. Sending an SIGINT signal to the process to interrupt will fix the blockage.

As cmds is an array of the message send separated by spaces, the username with spaces will be split across multiple array elements. A possible fix for this is to not use cmds to derive the username but instead to use the author property in the message object (from discord.js) passed in to get the username.

The @mentions of discord have a special format of <@xxxxxx> where xxxxxx is the user id. A possible solution to this is to use regex to detect <@xxxxx>, perhaps of /<@\d+>/. Once detected, trim off the preceding <@ and following >. Now that a ID is isolated, you can retrieve a TextChannel object from the given message object. Call the method members() on the TextChannel object which will return a Collection (an extended Map) in the form of <id, member object>. Iterate to match and use the member object to derive the username.

Some possible internet radio to use are R/a/dio, Eden, Listen.moe, and JPopsuki. The playback should be done using the simple command [!listen] and have a way to cycle through the radio list.

Playback from radios could potentially be combined with playback from the Bot's own song stash via queuing.