ShardingManager Woes
So my main project is still growing and I'm by no means at a point where sharding is required, but I'm also not one to put off something that I know will be a headache later on.
With that in mind I have implemented a sharding setup in my application now following the official guide. My application works and starts and given the lower guild count, only one shard gets spawned (shard 0). I've done this following many comments from people advising there is no harm in having it setup now to save me work later on.
My issue comes from the fact that no matter what I do, the
This means I'm unable to use any of the shard utilities like
I've asked for general help regarding this in #djs-help-v14 but I'm hoping with it's own thread here, someone might have more insight on what I could be doing wrong.
Disclosure: I'm using DJS Dev at the moment, but I've been having this same behaviour with 14.7.1 and also now 14.8.0 as well.
DJS: discord.js@14.8.1-dev.1678752596-41077c9.0
Node: 19.3.0
With that in mind I have implemented a sharding setup in my application now following the official guide. My application works and starts and given the lower guild count, only one shard gets spawned (shard 0). I've done this following many comments from people advising there is no harm in having it setup now to save me work later on.
My issue comes from the fact that no matter what I do, the
shard property on client is always null even though I know the client was started within a shard.This means I'm unable to use any of the shard utilities like
broadcastEval and fetchClientValues for instance.I've asked for general help regarding this in #djs-help-v14 but I'm hoping with it's own thread here, someone might have more insight on what I could be doing wrong.
Disclosure: I'm using DJS Dev at the moment, but I've been having this same behaviour with 14.7.1 and also now 14.8.0 as well.
DJS: discord.js@14.8.1-dev.1678752596-41077c9.0
Node: 19.3.0
