How meomundep/discord-autobot works
Project Type and Purpose
• This is a Node.js-based Discord automation bot (CLI tool) that orchestrates multiple Discord accounts in parallel to perform actions (auto-messaging, joining/leaving servers, deleting messages, AI-powered replies) through the Discord API, optionally via proxies. It uses JSON/YAML files for configuration and inputs, and loops continuously with configurable delays.
File Structure Analysis
• Top Level:
• meomundep_discord.js – main entry point (Orchestrator/CLI)
• package.json – Node.js dependencies and scripts
• README.md, DISCORD_INFO.MD, IMAGE/ – documentation assets
• run.bat / run.sh – platform-specific startup scripts
• Input Directories:
• discord_data/ – runtime artifacts (servers.json, tokens.txt)
• user_data/ – user config and message templates (configs.json, messages.yaml, proxies.txt)
• No separate “frontend” or “backend” — it’s a single CLI app with modular components (config loader, account manager, task executor, logger).
Key README Insights
• Core workflow:
a. Load configs (configs.json) and input files (tokens, channel IDs, invite codes, proxies, messages).
b. For each account (up to maxAccountsAtOnce, with inter-account delay):
• Initialize Discord client with token & proxy
• Execute enabled tasks in sequence (send messages, join/leave servers, delete messages, react/reply with optional AI)
• Log all events with timestamps
c. On completion or timeout (timeToRestartAllAccounts), restart the loop.
• Supports AI providers (Groq, OpenRouter, Gemini) via optional API keys.
a. Main Components (group into modules/containers):
1. CLI Orchestrator (meomundep_discord.js + run scripts)
2. Configuration & Input Loader (reads configs.json, tokens.txt, proxies.txt, messages.yaml, channel/server lists)
3. Account Manager (spawns and tracks multiple “Account Workers” up to maxAccountsAtOnce)
4. Account Worker (one per Discord token):
• Discord.js Client
• Proxy Layer (HTTP/S or SOCKS5)
• Task Executor (MessageSender, ServerJoiner, ServerLeaver, MessageDeleter, ReactionHandler, AIReplyHandler)
5. AI Provider Services (Groq, OpenRouter, Gemini – external)
6. Logging Module (timestamped logs, language formatting)
7. File System (input files + discord_data for persistence)
8. External Systems:
• Discord REST & Gateway APIs
b. Relationships & Data Flows:
• CLI Orchestrator → Configuration Loader → Account Manager
• Account Manager → spawns multiple Account Workers
• Each Account Worker → reads its token → applies proxy → connects to Discord Gateway
• Account Worker → invokes Task Executor → makes REST calls to Discord API (send/join/leave/delete)
• If AI replies enabled → Task Executor ↔ AI Provider Services
• All modules → Logging Module → writes to console/files
c. Architectural Patterns & Principles:
• Event-Driven / Actor Model: one Actor (Worker) per account responds to timers/events
• Scheduler/Throttler: enforces delayBetweenAccounts, delayEachChannel, delayEachChat, timeToRestartAllAccounts
• Single Responsibility: each module handles a clear concern (config, account lifecycle, tasks, logging)
• Externalization of Config & Data: makes behavior pluggable without code changes
d. Technologies & Frameworks:
• Node.js v22.11.0, npm
• discord.js (Discord API library)
• YAML parser (for messages.yaml)
• HTTP(S)/SOCKS5 proxy libraries
• Optionally AI SDKs or HTTP clients for Groq/OpenRouter/Gemini