TitanBot README

The project's README from github.com/codebymitch/TitanBot. As one markdown file: README.md.

TitanBot - Ultimate Discord Bot

TitanBot is a powerful, feature-rich Discord bot designed to enhance your server experience with comprehensive moderation tools, engaging economy systems, utility features, and much more. Built with modern Discord.js v14 and PostgreSQL for optimal performance and data persistence.

Support Server Discord.js PostgreSQL

Table of Contents

Features Overview

TitanBot offers a complete suite of tools for Discord server management and community engagement:

Moderation & Administration

  • Mass Actions - Bulk ban/kick capabilities
  • User Notes - Keep detailed moderation records
  • Case Management - View and track all mod actions

Economy System

  • Shop & Inventory - Buy and manage items
  • Gambling - Risk it for rewards
  • Pay System - Transfer money between users

Fun & Entertainment

  • Random Facts - Learn something new
  • Wanted Poster - Create fun wanted images
  • Text Reversal - Reverse any text

Advanced Ticket System

  • Claim & Priority - Staff ticket management
  • Ticket Limits - Prevent spam
  • Transcript System - Save ticket history

Server Stats

  • Member Counter - Live member count channels
  • Voice Counters - Track voice stats
  • Dynamic Updates - Real-time channel updates

Reaction Roles

  • Role Assignment - Self-assignable roles
  • Emoji Selection - Reaction-based system
  • Multi-role Support - Multiple role options

Leveling & XP System

  • XP Tracking - Automatic message-based XP
  • Level Roles - Auto-assign roles by level
  • Custom Configuration - Personalize leveling

Giveaways & Events

  • Multiple Winners - Support multi-winner giveaways
  • Auto Picking - Automatic winner selection
  • Reroll System - Pick new winners if needed

Birthday System

  • Birthday Tracking - Never miss a birthday
  • Auto Announcements - Celebrate automatically
  • Timezone Support - Accurate worldwide tracking

Utility Tools

  • Report System - Report issues to staff
  • Todo Lists - Personal task management
  • First Message - Jump to channel's first message

Welcome System

  • Welcome Messages - Greet new members
  • Auto Roles - Assign roles on join
  • Custom Embeds - Personalized messages

Music

  • 24/7 Mode - Play music 24/7
  • Interative Button System - Manage music through buttons
  • Supports EVERY platform - Supports spotify, deezer, youtube, apple music

Video Tutorial

For a detailed step-by-step setup guide, watch our comprehensive video tutorial: TitanBot Setup Tutorial

TitanBot is fully containerized for easy deployment.

  1. Clone the repository:

    git clone https://github.com/codebymitch/TitanBot.git
cd TitanBot

  2. Configure environment variables:

    cp .env.example .env

    Set at minimum DISCORD_TOKEN, CLIENT_ID, and GUILD_ID. Docker Compose also reads POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_DB from .env (defaults: titanbot / password / titanbot).

  3. Build and start the containers:

    docker compose up -d --build

  4. Check status:

    docker compose ps
curl http://localhost:3000/health

This starts the bot and PostgreSQL. The compose file sets POSTGRES_SSL=false and AUTO_MIGRATE=true for the bundled database. Music uses public Lavalink v4 nodes from lavalink/nodes.json by default.

Music

Music uses Lavalink v4 via Riffy, similar to Musicify.

  1. By default, the bot loads multiple public v4 SSL nodes from lavalink/nodes.json (sourced from lavalink.darrennathanael.com). Edit that file to add or remove nodes.
  2. To self-host Lavalink instead, run docker compose --profile local-lavalink up -d and set single-node env vars in .env:
    LAVALINK_HOST=lavalink
LAVALINK_PORT=2333
LAVALINK_PASSWORD=youshallnotpass
LAVALINK_SECURE=false
    Remove or rename lavalink/nodes.json so the bot falls back to those env vars.
  3. Override nodes inline with LAVALINK_NODES (JSON array) or point at another file with LAVALINK_NODES_FILE.
  4. Use /play <song> from a voice channel, or /join to connect without playing. Prefix shortcuts: join, np, leave, pause, resume, skip, stop, volume <0-100>, or music <subcommand>. Use /nowplaying and /queue for status; /music for loop, shuffle, seek, and other controls.

Using GitHub Container Registry

The bot is automatically published to GitHub Container Registry on every push to main.

docker pull ghcr.io/codebymitch/titanbot:main

Manual Installation Steps

Prerequisites

  1. Clone the Repository

    git clone https://github.com/codebymitch/TitanBot.git
cd TitanBot

  2. Install Dependencies

    npm install

  3. Configure Environment Variables

    cp .env.example .env

    Edit .env with your configuration (only the following variables require configuration, leave remaining variables as default):

    # Discord Bot Configuration
DISCORD_TOKEN=your_discord_bot_token_here
CLIENT_ID=your_discord_client_id_here
GUILD_ID=your_discord_guild_id_here

# PostgreSQL Configuration (Primary Database)
POSTGRES_URL=postgresql://postgres:yourpassword@localhost:5432/titanbot
POSTGRES_HOST=localhost
POSTGRES_PORT=5432
POSTGRES_DB=titanbot
POSTGRES_USER=postgres
POSTGRES_PASSWORD=yourpassword

    Production note:

    • NODE_ENV=production
    • LOG_LEVEL=warn for a clean production console (critical issues + startup status)
    • LOG_LEVEL=info if you want more detailed operational logs
    • If your chosen PORT is already used, TitanBot automatically tries the next port(s)

    Environment options reference:

    • NODE_ENV: development, production, test (any non-production value is treated as non-production)
    • LOG_LEVEL: error, warn, info, http, verbose, debug, silly
    • Accepted aliases for LOG_LEVEL in this bot: warns, warning, warnings → warn

    Recommended production .env (easy mode + default mode):

    NODE_ENV=production
LOG_LEVEL=warn
WEB_HOST=0.0.0.0
PORT=3000
PORT_RETRY_ATTEMPTS=5

    This gives clear startup/online status messages while keeping logs simple for non-technical operators. If port 3000 is busy, the bot tries the next available ports automatically (up to PORT_RETRY_ATTEMPTS).

Multiple servers

Slash commands are registered globally on startup (via CLIENT_ID), so the bot works in every server it is invited to. GUILD_ID stays in the tutorial .env for setup steps but is not used for command registration.

Notes:

  1. Setup PostgreSQL Database (Optional but recommended)

    # Create database and user
createdb titanbot
createuser titanbot
psql -c "ALTER USER titanbot PASSWORD 'yourpassword';"
psql -c "GRANT ALL PRIVILEGES ON DATABASE titanbot TO titanbot;"

  2. Verify Database Setup

    npm run migrate:check

  3. Start the Bot

    npm start

Note on database migrations: Schema tables and legacy key migrations run automatically on startup, somanaged hosts like **Railway** need no manual migration step — just deploy/restart. To disable auto-migration setAUTO_MIGRATE=false. You can still run a manual key migration locally with node scripts/migrate-keys.js --dry-run(preview) ornode scripts/migrate-keys.js`.

Required Bot Intents

TitanBot requires the following Discord intents:

Required Permissions

License

TitanBot is released under the MIT License. See LICENSE for details.

Thank You

Thank you for choosing TitanBot for your Discord server! We're constantly working to improve and add new features based on community feedback.

Last updated: May 2026

TitanBot (codebymitch/TitanBot)

community
Searching Database…

9K ·GitHub
TitanBot
What is this?An all-in-one Discord bot covering moderation, economy, tickets, music, leveling, giveaways, reaction roles, welcome messages and birthday tracking — built on discord.js v14 with PostgreSQL for persistence.
So it's not an app I download — where does this actually run?You host it yourself: deploy with Docker (recommended) or Node.js using your own Discord bot application. Images are auto-published to GitHub Container Registry on every push to main.
How do I get it running?Clone the repo, set DISCORDTOKEN, CLIENTID and GUILDID in .env, then docker compose up -d — that starts the bot plus a bundled PostgreSQL database. A video tutorial walks non-coders through the whole setup.
What do I need to have ready before installing?A Discord bot application with the required intents, plus PostgreSQL (recommended — memory storage works as a fallback). Manual installs also need Node.js 20.10.0 or higher; Docker users can skip that.
Anything I should know before the first launch?Global slash commands can take up to about an hour to appear after the first deploy. Music also relies on Lavalink v4 nodes — public ones are preconfigured, or you can self-host a node.
Does the music feature need me to run my own audio server?No — music runs through Lavalink v4 via Riffy, with public SSL nodes preloaded from lavalink/nodes.json. To self-host a node instead, run docker compose --profile local-lavalink up -d. It supports Spotify, Deezer, YouTube and Apple Music, with /play, button controls and prefix shortcuts like skip, queue and volume.
Can one deployment serve several Discord servers?Yes. Slash commands are registered globally via CLIENTID, so the bot works in every server it is invited to (OAuth2 scopes: bot and applications.commands). Each server gets isolated data — config, economy, tickets, leveling and warnings are all scoped per guild.
What can moderators actually do with it?Bulk ban/kick actions, per-user moderation notes, tracked case history and a staff report system. To act it needs permissions such as Kick Members, Ban Members, Manage Roles, Manage Messages and Manage Channels.
Beyond moderation, what is there for members?An economy with a shop, inventory, gambling and money transfers, message-based XP with auto-assigned level roles, giveaways with multiple winners, auto picking and rerolls, birthday tracking with timezone-aware announcements, welcome messages with auto roles, and a ticket system with claims, priorities and transcripts.
What are similar projects?Crucix, nanobot, YesPlayMusic, discord.js, SimpMusic, dokploy, YYeTsBot, discord.py
Which topics is it in?all-in-one, discord-bot, slash-commands, spotify, bot, community, discord, youtube, music, postgresql, docker-compose, free
Creator
codebymitch
Size
3.1 MB
Stars
9K
Updated
CommitAug 20Releasev3.0.0Jul 13
Age
8mo
Commits · 90 Days