Discord-Hybrid-Sharding

The first package which combines Sharding Manager & Internal Sharding to save a lot of resources! Aka: "Mixing both: if you need x shards for n process"

Why?

The Sharding Manager is very heavy and it uses more than 300mb on a light usage for every shard, during internal sharding just uses 20% of it. Internal Sharding reaches their limit on more than 14000 Guilds and it becomes slow when your bot gets bigger. Your only solution is to convert to the Sharding Manager. Thatsway this new Package will solve all your problems, because it spawns Shards, which has Internal Shards. You can save up to 60% on resources

How does it Work?

There are Clusters/Master Shards, which are like normal shards on the sharding manager and the clusters spawns in addition internal shards. So you do not have to spawn so much normal Shards (master shards ), which you can replace with internal shards. "for process n , n internal shards"

Example: A 4k Discord Bot Normaly we would spawn 4 shards with the Sharding Manager, but we start here with 2 Clusters/MasterShards, which spawns 2 internal shards ==> We save 2 shards in comparision to the Sharding Manager.

See below for the Docs

If you need help feel free to join our discord server. We will provied you all help ☺

Download

You can download it from npm:

npm i discord-hybrid-sharding

Setting Up

First we include the module into the project (into your shard/cluster file). Filename: Cluster.js

const Cluster = require("discord-hybrid-sharding");
let {token} = require("./config.json");
const manager = new Cluster.Manager(`${__dirname}/bot.js`,{
                                       totalShards: 7 ,
                                      ///See below for more options
                                       totalClusters: 2, 
                                       mode: "worker" ,  //you can also choose process
                                       token: token
                                    })
manager.on('clusterCreate', cluster => console.log(`Launched Cluster ${cluster.id}`));
manager.spawn(undefined, undefined, -1)

Sometimes the Cluster.Manager can choose a less amount of total Clusters, when it finds out, that a new cluster is not needed (in very rare cases...)

After that, you have to insert the code below in your bot.js file FileName: Bot.js //You can name your file after you wish

const Cluster = require("discord-hybrid-sharding");
const client = new Discord.Client({
     shards: Cluster.data.SHARD_LIST,        //  A Array of Shard list, which will get spawned
    shardCount: Cluster.data.TOTAL_SHARDS, // The Number of Total Shards
});
client.cluster = new Cluster.Client(client); //Init the CLient & So we can also access broadcastEval...
client.login("Your_Token");

Evaling over Clusters

Following examples assume that your Discord.Client is called client.

    let guildcount = (await client.cluster.broadcastEval(`this.guilds.cache.size`)).reduce((acc, guildCount) => Number(acc + guildCount), 0);
  message.channel.send(`I am in ${guildcount} guilds`)
.........

Cluster.Manager

The Manager.spawn option are the same like Sharding Manager

Cluster Events

Cluster Client Properties

You have all properties like broadcasteval..., just replace client.shard with client.cluster Other Properties:

Have fun and feel free to contribute/suggest or contact me on my discord server or per dm on Meister#9667

Bugs, Glitches and Issues

If you encounter any problems feel free to open an issue in our github repository or join the discord server.

Credits

Credits goes to the discord.js libary since some structures are copied and to this helpful server