Question 1

Could not locate the bindings file: fix better-sqlite3

Accepted Answer

Quick fix: update better-sqlite3 (and libraries that depend on it, like quick.db) to the latest version, delete node_modules and package-lock.json, and restart the application. Full steps below.

What this error means

When your application uses better-sqlite3 (directly, or through a library that depends on it like quick.db), it may fail on startup with an error like this:

Error: Could not locate the bindings file. Tried:
 → /application/node_modules/better-sqlite3/build/better_sqlite3.node
 ...

In short: better-sqlite3 couldn't load its native binary (the "bindings"), which almost always means the installed version is too old for the Node.js version running your app.

Why it happens

Older versions of better-sqlite3 don't support the Node.js LTS v24.x line. When the platform runs your application on a newer Node.js, the outdated package can't find a compatible compiled binary and throws this error.

How to fix it

1. Check the latest version of the libraries.

Look up the current versions on npm: better-sqlite3 and, if you use it, quick.db.

2. Update your package.json.

"better-sqlite3": "^12.5.0",
"quick.db": "^9.1.7" // or any other library that depends on better-sqlite3

Or from the terminal: npm install better-sqlite3@latest.

3. Force a clean install.

Delete node_modules, package-lock.json, and the `.

Question 2

LoginFailure: Improper token (401) — TOKEN_INVALID: how to fix

Accepted Answer

What this error means

Your Discord bot can't authenticate because its token is missing, wrong, or no longer valid (the Discord API responds with HTTP 401 Unauthorized). Typical messages:

# discord.js
Error [TOKEN_INVALID]: An invalid token was provided.

# discord.py
discord.errors.LoginFailure: Improper token has been passed.

Why it happens

The token was regenerated in the Developer Portal (the old one immediately stops working).
The token was reset or revoked for security.
It's misconfigured — extra spaces or quotes, or the code is reading the wrong variable.

How to fix it

1. Regenerate the token. In the Discord Developer Portal, open your application → Bot → Reset Token, and copy the new value.

2. Update the token where it's stored. Replace it in your .env file or config.json (and in your Square Cloud environment variables, if you use them). Never commit the token to GitHub.

3. Keep the library up to date. npm install discord.js@latest or pip install -U discord.py.

4. Restart the application.

Setting up a bot for the first time? See How to create a Discord bot from scratch and How to host a Discord bot.

Question 3

How to create a Discord bot from scratch

Accepted Answer

What a bot is and how it works

A Discord bot is an application that connects to the Discord API and acts as an automated user: it responds to commands, moderates the server, plays music, sends alerts, and much more. To create one, you need two things: register the application in the Discord Developer Portal and write the code that brings it to life.

1. Create the application in the Discord Developer Portal

Go to the Discord Developer Portal and log in.
Click New Application, give it a name, and confirm.
In the side menu, go to Bot.
Click Reset Token to generate your bot's token.

2. Get and protect your token

The token is your bot's password — whoever has the token controls the bot. So:

Never share it or push the token to GitHub.
Store it in an environment variable (e.g., DISCORD_TOKEN), never directly in the code.
If it leaks, generate a new one immediately under Reset Token.

3. Configure the Intents

Still under the Bot tab, enable the Privileged Gateway Intents your bot needs — especially the Message Content Intent if it will read messages. Without it, the bot won't receive message content (see Why isn't my bot reading messages? Understanding Privileged Intents).

4. Invite the bot to your server

Go to OAuth2 > URL Generator.
Under Scopes, check bot (and `applic

Question 4

Discord API rate limits (429 error): how to avoid them

Accepted Answer

How to Handle Rate Limits in the Discord API: The Ultimate Guide

If you develop Discord bots, sooner or later your application will receive an HTTP status code 429 (Too Many Requests). Discord enforces strict traffic rules to protect its infrastructure against abuse and Denial of Service (DoS) attacks.

For your bot to operate with maximum stability, you need to understand the internal mechanics of these limits and safeguard your code using a queue and cache system.

1. Anatomy of Discord Rate Limits

Discord divides its restrictions into well-defined layers. Limits are tracked based on your bot's token and the IP address from which the requests originate.

The Global Rate Limit

By default, Discord applies a global limit of 50 requests per second per bot token. If your bot attempts to trigger 51 requests in a single second (e.g., even if directed at entirely different endpoints), the API will temporarily block all subsequent calls.

Per-Route Limits and Buckets

In addition to the global limit, each API route has its own "bucket" of credits, usually tied to a primary identifier (such as a server or channel ID).

Common routes: Sending messages in a specific channel has a different limit than editing a user's nickname.
The critical Channel Creation/Editing route: Modifying or creating channels on a server is one of the most heavily monitored operations by Discord to prevent raid attacks. For instance, modifying a channel's name or topic is stri

Question 5

Sharding on Discord: how to scale your bot (2,500+)

Accepted Answer

Sharding: How to Scale Your Discord Bot on Square Cloud

When a Discord bot grows and reaches the 2,500 server mark, Discord requires it to use a technique called Sharding. Even before reaching this milestone, sharding can be a smart strategy to manage resources and prevent a failure in one server from bringing down the bot's connection across all others.

1. What Is Sharding?

Sharding is the process of splitting your bot's workload into multiple instances or "pieces" (shards). Instead of a single WebSocket connection handling all events from all servers, each shard takes care of a specific subset of servers.

Think of sharding as opening multiple cash registers at a supermarket instead of having just one cashier handling a mile-long line. This avoids processing bottlenecks and improves the bot's responsiveness.

2. Why Use Sharding on Square Cloud?

Hosting a sharded bot on Square Cloud offers strategic advantages:

Error Isolation: If one shard encounters a critical error and crashes, the other shards continue operating normally.
Memory Management: Node.js and Python have memory limits per process. Splitting the bot into shards allows you to make better use of your plan's total RAM.
Discord Limits: Discord enforces a strict limit of 2,500 servers per shard. Without sharding, your bot will stop receiving events once it hits this limit. Learn more here.

3. Technic

Question 6

discord.js or discord.py: which one to choose

Accepted Answer

Why the choice matters (and why it doesn't matter that much)

discord.js and discord.py are the two most-used libraries to build Discord bots. Both are mature, free, and capable of doing practically anything. The main difference is the language: discord.js uses JavaScript/Node.js and discord.py uses Python. The good news is you get a great bot with either one — and both run on Square Cloud.

discord.js (JavaScript / Node.js)

Pros:

Huge Node.js (npm) ecosystem, with packages for everything.
Great performance for large, asynchronous bots.
Enormous documentation and community.
Ideal if you already work with web or JavaScript.

Cons:

The asynchronous nature (async/await, Promises) can confuse beginners.
Changes between major versions require code adjustments.

discord.py (Python)

Pros:

Clean, easy-to-read syntax — excellent for those starting to program.
Widely used in automation and data projects.
Good documentation and an active community.

Cons:

The bot package ecosystem is a bit smaller than Node's.
For very high scale, it requires more attention to performance.

Quick comparison

Language: discord.js uses JavaScript; discord.py uses Python.
Learning curve: discord.py tends to be gentler for beginners; discord.js is natural for those who already know JS.
Performance at scale: both scale well, with a slight edge to discord.js for very large bots.
Community: both huge, with discord.js ahead in n

Frequently Read Articles

Browse All Categories