You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 27, 2018. It is now read-only.
I noticed however that after upgrading to 0.18, ready.js in the events folder is not executing on bot being ready.
Expected Behaviour
When the bot loads, ready.js from events is fired. I have a console.log to tell me when it is fired. It also creates an open port to receive metadata from a radio system to put as a channel topic in a guild.
Actual Behaviour
ready.js does not appear to fire. Nothing in the log about it firing, and the server port supposed to start up on ready is not started.
Steps to Reproduce.
create a ready.js script in events.
Make ready.js output something to the console on fire.
Start the bot via. pm2 or via. node.
ready.js does not appear to fire.
The text was updated successfully, but these errors were encountered:
@Lovinity Fixed and will be instated on the next NPM version of Komada, (0.18.1, UtilsHotFix).
Thank you for using the issues tab for reporting this bug.
Version of Komada
0.18 on Centos 7
Are core files modified?
No
Describe the problem
I noticed however that after upgrading to 0.18, ready.js in the events folder is not executing on bot being ready.
Expected Behaviour
When the bot loads, ready.js from events is fired. I have a console.log to tell me when it is fired. It also creates an open port to receive metadata from a radio system to put as a channel topic in a guild.
Actual Behaviour
ready.js does not appear to fire. Nothing in the log about it firing, and the server port supposed to start up on ready is not started.
Steps to Reproduce.
The text was updated successfully, but these errors were encountered: