Custom logging about eris-fleet

[danclay]

You should be able to do whatever you want with the errors in your index.js file. It is emitted as log, debug, or error. So you could do

const Admiral = new Fleet(options);

Admiral.on('log', m => {
// Do whatever you want with the log
});
Admiral.on('debug', m => {
// Do whatever you want with the log
});
Admiral.on('error', m => {
// Do whatever you want with the log
});

[ThatTonybo]

Got it. Side question as well ~ how do you set the shard's status? Workers don't seem to receive any ready event.

[danclay]

Each cluster is considered ready when all the shards within that cluster are ready. Your code loads after all shards within a cluster are ready.

[ThatTonybo]

So theoretically, slapping the editStatus code anywhere in the bot.js would work?

[danclay]

Yes, you shouldn't have to worry about the client not being ready in your bot.js file since it only loads the code when the client is ready.

[ThatTonybo]

Sounds good. One last question that just popped up:
Are stats not first known on start up? Tried using the ipc.getStats() function and it returns this:

{"guilds":0,"users":0,"clustersRam":0,"voice":0,"largeGuilds":0,"shardCount":0,"clusters":[]}

[danclay]

Stats are started once all services and clusters have launched. It may be possible to give stats as each cluster comes online, but this will give inaccurate stats so I'm conflicted on making that change. If I give 0 for each value, then your code can know if the stats are not ready since everything is 0. You can listen for stats updates by registering the "stats" event in IPC. Here's an example:

this.ipc.register("stats", (message) => {
   const stats = message.msg;
   // Do stuff with the stats
});

[ThatTonybo]

I'd like it to be an option. Otherwise looks good, I can just wait until the stats are ready.