Lesson 12 — Sharding (Advanced)

Goal: Understand what shards are and why the handler uses index.js.

Video

Paste your lesson video embed here later.

Baby-step explanation

Step 1 — What is a shard?

A shard is basically another copy of your bot that runs at the same time, but each copy only handles some servers instead of all of them.

Step 2 — Why shards exist

Discord limits how much one bot process can handle. If a bot is in many servers, it can become slow or crash. Sharding fixes this by spreading the workload across multiple bot processes.

Step 3 — Why you start index.js

index.js is the shard manager — it creates and manages shards. app.js is the actual bot code that each shard runs.

node index.js → creates shards
shards → run app.js
app.js → runs the bot

Step 4 — Student rule

Do not change sharding values unless Helix tells you to.

Changing shard settings incorrectly can cause commands to stop working, servers to not respond, or the bot to fail to start.

How Sharding Works

index.js (Shard Manager) ↓ ┌─────────────┐ │ Shard 1 │ → Servers 1–500 └─────────────┘ ┌─────────────┐ │ Shard 2 │ → Servers 501–1000 └─────────────┘ ↓ app.js runs on each shard

Summary

A shard is another copy of your bot.
Shards exist to prevent lag and crashes.
index.js starts and manages shards.
app.js is the bot code each shard runs.
Do not change shard settings unless told to.

← Lesson 11 Next → Lesson 13