Problem
Community servers outgrow a single feature. By the time The CodeVerse Hub crossed a thousand members, staff were juggling half a dozen disconnected bots: one for moderation, one for tickets, one for fun games, one for starboard. Each bot had its own permissions model, its own database, and its own failure modes.
Existing all-in-one bots were either closed-source, paid, or shipped opinionated features the community couldn't extend. The team wanted a self-hosted bot they fully owned one that could grow with the server, be reloaded without downtime, and be hardened against injection attacks.
Goals
Support
Thread-based ticket system with persistent button panels across Bugs, Support, and Partnerships categories.
Engagement
Anti-grief counting game, CodeBuddy quizzes, and Daily Quest rewards that keep members active beyond one-time moderation.
Moderation
Role-based access control, user tracking (chowkidar), and parameterized queries to prevent SQL injection.
Extensibility
Cog-based architecture with hot reload, documented setup, and Dockerized deployment so maintainers can iterate live.
Architecture
┌──────────────────────────────────────────────────────────────────────────┐ │ EIGEN BOT │ ├──────────────────────────────────────────────────────────────────────────┤ │ Discord Gateway Cog Layer Persistence Ops │ │ ┌───────────────┐ ┌───────────────┐ ┌───────────────┐ ┌────────────┐ │ │ │Hybrid │ │Tickets │ │aiosqlite │ │Docker │ │ │ │commands │ │Starboard │ │.db files │ │Compose │ │ │ │?prefix + / │ │Tags · Elect │ │parameterized │ │hot reload │ │ │ │slash │ │Games · Quests │ │SQL + RBAC │ │?reload │ │ │ └───────────────┘ └───────────────┘ └───────────────┘ └────────────┘ │ │ hot reload (?reload) · Docker Compose · RBAC security │ └──────────────────────────────────────────────────────────────────────────┘
Eigen Bot is organized as a modular cog-based application around a single async event loop. Each feature lives in its own cog, exposing hybrid commands that work with both the ? prefix and native / slash commands. State is persisted per-feature in dedicated SQLite databases, accessed exclusively through parameterized queries behind a role-based access-control layer.
Gateway & Commands
discord.py hybrid commands give members a familiar ? prefix while surfacing discoverable / slash commands. Guild-scoped syncing keeps slash updates instant during development.
Cog Layer
Tickets, starboard, tags, elections, staff applications, and games each live in an isolated module that can be hot-reloaded with ?reload no restarts, no downtime during live events.
Persistence
aiosqlite provides async database access across dedicated .db files. All queries are parameterized, and admin actions pass through an RBAC layer before touching data.
Deployment
Fully containerized with Docker and Docker Compose, with environment-driven configuration (DISCORD_TOKEN, OWNER_ID, GUILD_IDS) for reproducible, single-command setup.
Key Features
Support Tickets
Thread-based categories (Bugs, Support, Partnerships) with persistent button panels members open a thread with one click and staff work through it in-place.
Starboard System
Community-voted content is highlighted automatically with dynamic embeds, surfacing the best posts without manual curation.
Tag System
High-speed storage and retrieval of custom text snippets staff paste common answers in one command instead of retyping them.
Elections & Voting
Democratic decision-making with weighted roles, used by the community for maintainer elections and rule polls.
Staff Applications
DM-based application flow with admin review channels, keeping the pipeline private and organized.
Engagement Games
Anti-grief counting game, CodeBuddy MCQ quizzes, and Daily Quest rewards keep the server lively between technical discussions.
Tech Stack
Python 3.11+
Core language modern async patterns keep the bot responsive under load.
discord.py
Gateway client with hybrid commands (prefix + slash) and cog support.
aiosqlite
Async SQLite access for per-feature persistence without blocking the event loop.
Docker / Compose
Reproducible containerized deployment with env-driven configuration.
Results
Eigen Bot consolidated the community's bot sprawl into one owned codebase. Support tickets moved from ad-hoc DMs to organized threads with persistent panels, and moderation tooling (chowkidar tracking, RBAC) gave staff precision without giving them dangerous raw permissions. The bot is the reference implementation for new contributors joining the org's Discord bot cohort.
Challenges & Trade-offs
Challenge
Slash commands take up to an hour to sync globally, which slows live iteration on a bot used in production every day.
Solution
Hybrid commands expose both ? prefix and / slash interfaces from a single implementation, and GUILD_IDS scopes slash syncing to the development guild for near-instant updates.
Challenge
Six features sharing one process risks a single crash or permission bug cascading across all of them.
Solution
Each feature is isolated in its own cog with its own .db file, wrapped in a role-based access control layer. Parameterized queries eliminate the injection class of bugs entirely.
Challenge
Live community events can't wait for a deploy cycle when a command misbehaves.
Solution
The cog architecture ships a ?reload command, so maintainers hot-swap modules without restarting the process or dropping the gateway connection.
Implementation Highlights
Hybrid Commands
One implementation, two interfaces: ?prefix for power users, / slash for discoverability. No duplicated command logic.
Security First
Parameterized SQL everywhere, role-based access control on every admin path, and no raw database string interpolation.
Self-Hosted Ownership
No vendor lock-in, no premium tiers. The community owns the code, the data, and the deployment.
Lessons Learned
Async I/O discipline pays off a single blocking call in a shared cog stalls every command, so every feature must stay non-blocking.
Documentation-as-code (the /docs markdown set) makes a production bot maintainable by a rotating team of contributors.
Self-hosting is a feature: full control over permissions, data, and deployment turned the bot into a teaching artifact for new Discord developers.