Echo System

A complete Discord bot for moderation, security, automation, and community management.

Echo System is a feature-rich Discord bot built to help communities run smoothly and securely. It combines moderation tools, anti-nuke protection, welcome systems, ticketing, giveaways, level tracking, and custom emoji support into one polished package.

Echo System

Echo System is a self-hosted, prefix-command Discord bot built with TypeScript, Discord.js, MongoDB, and Canvas. It provides configurable moderation and event logs, five-type ticket panels, giveaways, temporary voice rooms, EchoSR wallets, leveling, and activity leaderboards.

This project is independently developed and is not affiliated with or endorsed by Discord or ProBot.

Contents

• Features
• Requirements
• Getting started
• Configuration
• Discord setup
• Commands
• Development
• Data and limitations

Features

• Moderation tools, warnings, and configurable security protections
• Per-category event logs, including moderation, members, messages, invites, giveaways, and tickets
• Ticket panels with five configurable types, support roles, welcome messages, images, and transcripts
• Giveaways with enter/leave buttons and event logging
• Temporary voice rooms with owner controls
• EchoSR wallets, message leveling, Canvas cards, and Egypt-time activity leaderboards
• Server-specific prefixes, command aliases, and custom Echo emoji support

Requirements

• Node.js 20 or newer and npm
• A MongoDB server or MongoDB Atlas database
• A Discord application with a bot user and token

Getting started

1. Clone or download this repository, then open a terminal in the project folder (echoss).

2. Install dependencies:

   Shell

   npm install
   

3. Create a .env file in the project root and fill in the values described under Configuration.

4. Configure the Discord application and invite the bot as described under Discord setup.

5. Build and start the bot:

   Shell

   npm run build
   npm start
   

For development with automatic restarts, use npm run dev. This bot uses prefix commands; slash-command registration is not required.

The Bot is also hostable on any host by using this startup command

npm install && npm run build && npm start

Configuration

The bot loads environment variables from .env at startup.

Example .env:

DISCORD_TOKEN=your_bot_token
MONGODB_URI=mongodb://127.0.0.1:27017
MONGODB_DATABASE=echo_system
BOT_OWNER_IDS=your_discord_user_id
DEFAULT_PREFIX=+

For Atlas, set MONGODB_URI to your Atlas connection string. The database user needs the built-in readWrite role on the database named by MONGODB_DATABASE. The bot attempts to create indexes at startup; if index creation is denied, it continues with a warning, but missing indexes can reduce performance or uniqueness protection.

Never commit or share .env or your bot token. If a token is exposed, reset it in the Developer Portal immediately.

Discord setup

1. Create an application in the Discord Developer Portal, add a bot user, and copy its token into .env.
2. In Bot → Privileged Gateway Intents, enable Message Content Intent and Server Members Intent. Invite events use the Guild Invites gateway intent in the bot code and do not require a separate privileged-intent toggle.
3. Under OAuth2 → URL Generator, select the bot scope and invite the bot to your server.
4. Grant only the permissions for the features you intend to use. Common permissions include View Channels, Send Messages, Embed Links, and Read Message History. Depending on enabled modules, the bot may also need Manage Messages, Manage Channels, Manage Server (invite-create logging), Move Members, Manage Roles, Moderate Members, Kick Members, Ban Members, or View Audit Log.
5. Place the bot's role above roles it needs to manage. Discord's role hierarchy still applies to moderation, role, and channel actions.

Some permissions are feature-specific: temporary voice needs Manage Channels and Move Members; transcript export needs ticket-history access and Attach Files in the transcript destination; anti-nuke audit checks need View Audit Log.

Prefix and help

The fallback prefix is $. Set DEFAULT_PREFIX for servers without a saved prefix, or use +setprefix ! to change a server's prefix (replace + with that server's current prefix). +help opens the interactive command categories. Choose Nadeko for a directory of the commands currently implemented across all modules, including moderation, utilities, tickets, and economy. The bot uses the prefix saved for each server.

In the examples below, replace + with your server's current prefix. A command that takes #channel accepts a channel mention; commands that take @member accept a user mention.

Command guide

General and Canvas

Canvas is also used for rank and activity leaderboard cards.

Moderation and administration

Each log category can be routed to a different channel. For example, use +setlogs moderation #mod-logs and +setlogs giveaways #giveaway-logs. Events are sent as timestamped embeds with the server name and icon. +setlogs <category> off disables that category; categories without a configured channel use the bot console unless the legacy shared log channel is still configured. +logs shows each category's current destination.

New invite links are logged in the invites category with their creator, channel, maximum uses, and expiry. The bot needs Manage Server permission in the guild for these events.

Tickets, greetings, and giveaways

Giveaway creation, entries, exits, and results are sent to the configured event-log channel as embeds.

Ticket panels are posted separately for each of the five types, so each panel can have its own text, button label, Discord parent category, support role, opening message, and image. Use +ticketpanel 1 through +ticketpanel 5 to repost one panel, or +ticketpanel to repost them all. Support staff can claim and unclaim tickets from the ticket controls; ticket openings, claims, unclaims, and closures go to the tickets log category. On close, up to the latest 1,000 messages and attachment links are exported as a .txt transcript (capped at 1 MB) to the transcripts log category. Configure the destinations with +setlogs tickets #ticket-logs and +setlogs transcripts #transcript-logs. The bot needs permission to view ticket history and attach files in the transcript destination.

EchoSR and leveling

EchoSR is an internal wallet currency. +convert displays the reference rate 1 EchoSR = 40,000 ProBot credits; it does not send or verify real ProBot credits.

XP is awarded for eligible messages with a one-minute per-user cooldown.

Activity leaderboards

Daily and weekly windows use Africa/Cairo: daily stats begin at Cairo midnight; weekly stats begin Monday at Cairo midnight. Voice activity accumulates only while the bot is online. Combined scores equal text-message count plus voice minutes.

Temporary voice

Use +tempvoice setup #join-to-create [category] to configure the trigger, +tempvoice status to inspect it, and +tempvoice off to disable it. Members joining the trigger are moved into a room named for them; the room is deleted when empty. Each room gets a control embed in its voice-channel chat with controls to lock/unlock, hide/show, rename, set a user limit, claim an abandoned room, transfer ownership, allow/block a user, and disconnect a member. Ownership transfers automatically to a remaining room member if the owner leaves. Room owners and members with Manage Channels can use the controls. The bot needs Manage Channels, Move Members, Send Messages, Embed Links, and Read Message History.

Owners and shortcuts

Seed initial owners with comma-separated Discord user IDs in BOT_OWNER_IDS. Owners can add another owner using +addowner @user. Owner shortcuts are server-specific:

+alias tdaytext topdaytext
+aliases
+unalias tdaytext

Shortcuts can target registered commands and cannot replace built-in names.

Security

Whitelist a user or role with +whitelist add @user-or-role; inspect with +whitelist list; remove with +whitelist remove @user-or-role.

Anti-raid and anti-nuke are disabled by default. Example configuration:

+antiraid on 8 10 alert
+antinuke on 3 20 alert

Anti-raid can use timeout instead of alert; anti-nuke can use strip to remove selected privileged roles after its threshold. Anti-nuke requires View Audit Log; strip also requires Manage Roles. These protections monitor configured event thresholds and cannot restore deleted channels or roles.

Echo custom emojis

Run npm run emojis:build, then upload the generated PNGs from assets/emojis to each server. Keep names such as echo_core, echo_coin, and echo_tickets; the bot finds uploaded emojis by name. Without them, the bot uses text labels.

Development

npm run dev
npm run build
npm test

Run npm run emojis:build to generate the Echo emoji PNG pack in assets/emojis; see Echo custom emojis for how to use it in a server.

Data and limitations

Premium is a placeholder until a payment provider is configured. ProBot credits are not transferred by this bot; +convert only displays a reference value. The Nadeko help entry is a directory of Echo System's implemented commands; it does not indicate full Nadeko feature parity or use Nadeko's original code.

M5 EnzoCord