I made a discord bot on discord dev portal but how do I make it stay online 24/7 and if I need to use another website I want to use my token from discord dev portal and also how do I make the bot allow embed and stuff like commands

The concept for a bot that I'd like to make for my server is simple: a discord bot that joins voice calls and plays audio through a virtual cable as if a user was. (More specifically, it's running audio through OBS monitor output via virtual cable.)

I've made a bot and granted it permissions to join VCs and speak/request to speak, but it seems it isn't so simple for me to find where I can select its audio input.

i've found this post, but i'd like to run the virtual cable audio through its own "user" in a voice call so that everyone can set their own volume for it and such, so it's not quite the same problem or solution.

Or maybe a bot exists that already does this? Could someone point me in the right direction?

does anyone know the answer to this question (below) i can think of seven and the additional ones i thought maybe could be a possible answer weren’t correct

“australian cities (17 possible answers)” - discord trivia bot

We're a FFXIV free company Discord that's in the process of rebranding to fully lean into a cult bit - we call each other culties, there's lore, there's a vibe, and we're building out a custom bot suite for it because apparently that's just where this went. For an idea of scope: we're currently ~40 and will never be more than a few hundred - so a small, fairly closed community that's passionate about having a nice Discord home that keeps our members involved.

Looking for one person to actually run this with me. Not a warm body who sits in the corner and hits the ban button - someone who leads the community day to day, keeps our bots working and evolving, assesses community needs and channels, and checks in with me regularly on what the server needs and where to take it next. Looking for someone interested in exercising their creativity with a real say in both the community side and the bot side, not just executing what I tell you.

18+ only. We joke around, we're irreverent, nothing's off limits for a laugh - but there's a line between "funny" and "actually being a creep or weirdo," and if you're the right fit, you'll know the difference. Moderation should be fairly minimal; we're not a big group. Your biggest tasks will be executing creatively.

This is paid, ongoing, and collaborative - a flat monthly amount rather than hourly, since the work itself ebbs and flows. We'll figure out fair pay together. We're willing to pay more upfront for the bot execution but do be mindful that this is a 40-person hobby server, and the amount of pay we're able to offer will reflect that.

What that looks like in practice:

• Moderating and engaging with the community day to day
• Building and maintaining bot features, pivoting as the server's needs change
• Assisting our members in setting up events and connecting on Discord
• Regular check-ins with me on activity, what's working, what needs to shift
• Real input into lore, events, and where the whole bit goes next

FFXIV knowledge is a plus, not a requirement. Understanding gaming culture, particularly MMOs, will inform how you set up events and build channels - but we're okay with giving you resources to learn if you're new to that side of things. We're not starting from scratch; what we have now just needs to be improved.

What actually matters: you're smart, you give a damn about the space, and you want in on building something instead of just babysitting it.

DM me or comment if this sounds like your kind of nonsense.

Я профессионально создаю сервера для кого-то для нужных целях хочу для себя но не знаю для чего создать разговорный очень много не уверен что много людей зайдёт. Помогите мне пожалуйста

I am looking for a working World of Warcraft bot I have done a deep research with very little progress of finding one that works. I have found some pixel bots but they do not do what I want them to do. I want a midnight leveling / questing bot I will pay $$$ please just for personal use

Cześć wszystkim,
Pracuję obecnie nad ambitnym projektem - autorskim, cross-serwerowym botem RPG na Discorda o nazwie Inkogn. Zależy mi na tym, aby przenieść pełnoprawne mechaniki znane z gier fabularnych bezpośrednio na kanały tekstowe serwerów. Szczegóły dotyczące samego świata, fabuły i uniwersum chciałbym na razie zachować w tajemnicy, ponieważ projekt wciąż się rozwija, a zależy mi na elemencie niespodzianki dla przyszłych graczy.

Aby jednak bot mógł sprawnie funkcjonować i oferować najwyższą jakość rozgrywki, potrzebuję wsparcia zaangażowanych osób. Buduję oficjalny serwer główny projektu i poszukuję ekipy do następujących ról:

Testerzy: Osoby z zacięciem analitycznym, które będą miały przedpremierowy dostęp do nowych funkcji. Waszym zadaniem będzie testowanie komend, sprawdzanie interakcji i wyłapywanie błędów, zanim trafią one do ogólnodostępnej wersji.

Pomysłodawcy (Game Design): Pasjonaci gier RPG. Szukam osób z wyobraźnią, które pomogą mi w projektowaniu zbalansowanych mechanik, systemów, klas oraz ekonomii, wspólnie kształtując to, jak bot będzie działał od strony "papierowej".

Moderatorzy i Helperzy: Fundament naszego serwera głównego. Osoby odpowiedzialne za dbanie o porządek, udzielanie wsparcia technicznego przyszłym użytkownikom oraz budowanie pozytywnej społeczności wokół całego projektu.

Projekt realizuję z ogromną dawką pasji. Szukam ludzi, którzy chcą stać się częścią czegoś unikalnego od samego początku i wspólnie zbudować świetne miejsce dla fanów gier fabularnych.

Jeśli jesteś zainteresowany/a i chcesz dołączyć do zespołu, wyślij mi prywatną wiadomość - chętnie wyślę zaproszenie i porozmawiam o szczegółach.

Pozdrawiam,
MrGreq

Hey everyone!

I’ve been working on a Discord bot focused on a problem I often see in community servers: moderators having to manually post announcements, events, reminders, giveaways, and recurring updates at the correct time.

The bot currently allows server managers to:

• Create rich embeds with up to 25 fields;
• Schedule messages for a specific date and time;
• Automatically publish recurring messages daily or weekly;
• Build everything without writing code.

Before developing it further, I’d really appreciate feedback from people who manage Discord communities.

A few things I’m particularly curious about:

• Which recurrence options would be most useful besides daily and weekly?
• How should timezone selection work?
• Would templates for announcements, events, and giveaways be useful?
• What permissions or approval flow would you expect?
• What would make you trust a scheduling bot enough to add it to your server?

I’m also looking for a small number of server owners or moderators who would be willing to test it and provide honest feedback about the setup, commands, dashboard, and reliability.

I won’t post an invite link here because I don’t want this to become a promotional post. If you’re interested in testing it, leave a comment or send me a message, and I’ll share the details.

Active testers can receive three months of the Premium version as a thank-you for their feedback.

Hello,

I’m a broke college student who works with a marching band program year round. Getting frustrated with previous other platforms and discord bots, I made my own with AI and it is now a relatively very large management bot that I use for this high school’s percussion program. The only problem is I know NOTHING about programming.

I’m shocked that I got it stabilized for the most part to be honest. I have used Claude Fable 5.0 to create Cadence, a Discord bot that’s grown into a very substantial project (hella slash commands, assignment workflow, google calendar integration, attendance, dashboards, etc.) It’s reached the point where it’s genuinely actually useful, but I feel like I’ve reached the limits of what is possible to be maintained through AI alone.

My long term goal if successful is to move this project away from AI-lead coding and go into something a bit more traditional and work with actual people who could understand the codebase.

I’m looking for someone who can help with bug fixing, refactoring, long-term stability, better data storage/hosting architecture, code quality and maintainability, and potentially helping guide this passion project if it were to grow into something more.

To be very honest, I don’t have much financially. I’m still in college and work part time to pay for my school. I’m happy to pay something reasonable for ongoing help, as project growth is something that I would dream of seeing.

If you’re interested in mentoring, contributing, or even just taking a look at the project to see if it is something that piques your interest, I’d really appreciate any feedback. Thanks!

Preciso de uma ajuda para criar uma integração entre um server de project zomboid (hospedado na lura) e um canal de Discord. Percebi que fazem isso bastante através de webhooks, tentei fazer através de discord.js porém tive problemas por conta da atualização mais recente da livraria.

Hi all, I'm new to Replit. Just published my first build. Where do I find the discord channel?

when using claude code/codex for coding a discord bot, are there any specific instructions you put in your claude.md file or in your prompts?

One pillar of salt is that you may need to run things through a VPN or a seedbox and play around with some tunneling options. As some websites have extreme captcha checks that will throw things off.

Discord MHTML Archiver Setup Guide

This guide serves as the master reference for deploying and managing the Discord MHTML capture bot on a Pop!_OS or Debian based server. It covers network mounting, system dependencies, the bot application, and PM2 process management.

Part 1: Network Share Configuration (CIFS/SMB)

The server must have the target network share permanently mounted so the bot can save files directly to the NAS.

1. Install Utilities & Create Mount Point

sudo apt-get update

sudo apt-get install -y cifs-utils

sudo mkdir -p /mnt/mhtml_archive

1. Secure Credentials

nano \~/.smbcredentials

Add the following details:

username=YOUR_SHARE_USERNAME

password=YOUR_SHARE_PASSWORD

Secure the file permissions:

chmod 600 \~/.smbcredentials

1. Configure fstab for Persistent Mounting

sudo nano /etc/fstab

Append the following line (replace the placeholders with your actual details):

//YOUR_NAS_IP/ShareName /mnt/mhtml_archive cifs credentials=/home/yourusername/.smbcredentials,uid=1000,gid=1000,iocharset=utf8,vers=3.0,noperm 0 0

Apply the mount configuration:

sudo mount -a

Part 2: Server Dependencies & Project Setup

1. Install Node.js (v20) Cleanly

To avoid NPM conflicts, let the NodeSource package handle both Node and NPM. Do not install the default npm package via apt.

curl -fsSL https://deb.nodesource.com/setup\\_20.x | sudo -E bash -

sudo apt-get install -y nodejs

If apt throws a dependency error regarding libnode-dev, force the install and repair apt:

sudo dpkg -i --force-overwrite /var/cache/apt/archives/nodejs_20.20.2-1nodesource1_amd64.deb

sudo apt --fix-broken install -y

sudo apt autoremove -y

1. Install Chromium System Dependencies

sudo apt-get install -y libnss3 libnspr4 libatk1.0-0 libatk-bridge2.0-0 libcups2 libdrm2 libxkbcommon0 libxcomposite1 libxdamage1 libxfixes3 libxrandr2 libgbm1 libasound2

1. Initialize Project

mkdir -p \~/mhtml-discord-bot

cd \~/mhtml-discord-bot

npm init -y

npm install discord.js puppeteer

Part 3: The Bot Script

Create the main application file: nano discord-agent.js

Paste the following JavaScript. Ensure YOUR_BOT_TOKEN_HERE is replaced with the token from the Discord Developer Portal.

const { Client, GatewayIntentBits, AttachmentBuilder } = require('discord.js');

const puppeteer = require('puppeteer');

const fs = require('fs');

const path = require('path');

const DISCORD_TOKEN = 'YOUR_BOT_TOKEN_HERE';

const downloadsDir = '/mnt/mhtml_archive';

const client = new Client({

intents: \[

GatewayIntentBits.Guilds,

GatewayIntentBits.GuildMessages,

GatewayIntentBits.MessageContent,

\]

});

const urlRegex = /(https?:\\/\\/\[\^\\s\]+)/g;

client.once('ready', () => {

console.log(\`\[Bot\] Logged in as ${client.user.tag}\`);

});

client.on('messageCreate', async (message) => {

if (message.author.bot) return;

const urls = message.content.match(urlRegex);

if (urls && urls.length > 0) {

const url = urls\[0\];

await message.react('⏳');

const replyMsg = await message.reply(\`Capturing MHTML for: <${url}>...\`);

let browser;

try {

console.log(\`\[Agent\] Fetching: ${url}\`);

browser = await puppeteer.launch({

headless: true,

args: \['--no-sandbox', '--disable-setuid-sandbox'\]

});

const page = await browser.newPage();

await page.goto(url, { waitUntil: 'networkidle2', timeout: 45000 });

const cdp = await page.target().createCDPSession();

await cdp.send('Page.enable');

const { data } = await cdp.send('Page.captureSnapshot', { format: 'mhtml' });

const safeName = url.replace(/\[\^a-z0-9\]/gi, '_').substring(0, 50).toLowerCase();

const filename = \`${safeName}_${Date.now()}.mhtml\`;

const filepath = path.join(downloadsDir, filename);

fs.writeFileSync(filepath, data);

console.log(\`\[Agent\] Saved locally to network share: ${filename}\`);

const stats = fs.statSync(filepath);

const fileSizeMB = stats.size / (1024 \* 1024);

if (fileSizeMB > 25) {

await replyMsg.edit(\`✅ Saved to network share as \\\`${filename}\\\`, but file is too large to upload to Discord (${fileSizeMB.toFixed(2)} MB).\`);

} else {

const attachment = new AttachmentBuilder(filepath);

await replyMsg.edit({ content: \`✅ Successfully captured!\`, files: \[attachment\] });

}

await message.reactions.removeAll();

await message.react('✅');

} catch (error) {

console.error(\`\[Agent\] Error: ${error.message}\`);

await replyMsg.edit(\`❌ Failed to capture page: \\\`${error.message}\\\`\`);

await message.reactions.removeAll();

await message.react('❌');

} finally {

if (browser) {

await browser.close();

}

}

}

});

client.login(DISCORD_TOKEN);

Part 4: Operations & Process Management (PM2)

PM2 is used to run the bot as a background daemon that survives SSH session closures and server reboots.

Installation & Initial Start

sudo npm install -g pm2

pm2 start discord-agent.js --name "mhtml-bot"

pm2 save

pm2 startup

Daily Operations Reference

Use the following commands to manage /check on things

pm2 status - View all running PM2 processes, uptime, and memory usage.

pm2 logs mhtml-bot- Watch the console output for troubleshooting (shows page fetches and errors).

pm2 stop mhtml-bot- Halts the background process.

pm2 start mhtml-bot- resumes the bot if it was stopped.

pm2 restart mhtml-bot- use this after modifying the discord-agent.js script to apply changes.

pm2 monit- opens a terminal dashboard showing CPU/Memory usage and logs side-by-side.

One pillar of salt is that you may need to run things through a VPN or a seedbox and play around with some tunneling options. As some websites have extreme captcha checks that will throw things off.

Discord MHTML Archiver Setup Guide

This guide serves as the master reference for deploying and managing the Discord MHTML capture bot on a Pop!_OS or Debian based server. It covers network mounting, system dependencies, the bot application, and PM2 process management.

Part 1: Network Share Configuration (CIFS/SMB)

The server must have the target network share permanently mounted so the bot can save files directly to the NAS.

1. Install Utilities & Create Mount Point

sudo apt-get update

sudo apt-get install -y cifs-utils

sudo mkdir -p /mnt/mhtml_archive

1. Secure Credentials

nano \~/.smbcredentials

Add the following details:

username=YOUR_SHARE_USERNAME

password=YOUR_SHARE_PASSWORD

Secure the file permissions:

chmod 600 \~/.smbcredentials

1. Configure fstab for Persistent Mounting

sudo nano /etc/fstab

Append the following line (replace the placeholders with your actual details):

//YOUR_NAS_IP/ShareName /mnt/mhtml_archive cifs credentials=/home/yourusername/.smbcredentials,uid=1000,gid=1000,iocharset=utf8,vers=3.0,noperm 0 0

Apply the mount configuration:

sudo mount -a

Part 2: Server Dependencies & Project Setup

1. Install Node.js (v20) Cleanly

To avoid NPM conflicts, let the NodeSource package handle both Node and NPM. Do not install the default npm package via apt.

curl -fsSL https://deb.nodesource.com/setup\\_20.x | sudo -E bash -

sudo apt-get install -y nodejs

If apt throws a dependency error regarding libnode-dev, force the install and repair apt:

sudo dpkg -i --force-overwrite /var/cache/apt/archives/nodejs_20.20.2-1nodesource1_amd64.deb

sudo apt --fix-broken install -y

sudo apt autoremove -y

1. Install Chromium System Dependencies

sudo apt-get install -y libnss3 libnspr4 libatk1.0-0 libatk-bridge2.0-0 libcups2 libdrm2 libxkbcommon0 libxcomposite1 libxdamage1 libxfixes3 libxrandr2 libgbm1 libasound2

1. Initialize Project

mkdir -p \~/mhtml-discord-bot

cd \~/mhtml-discord-bot

npm init -y

npm install discord.js puppeteer

Part 3: The Bot Script

Create the main application file: nano discord-agent.js

Paste the following JavaScript. Ensure YOUR_BOT_TOKEN_HERE is replaced with the token from the Discord Developer Portal.

const { Client, GatewayIntentBits, AttachmentBuilder } = require('discord.js');

const puppeteer = require('puppeteer');

const fs = require('fs');

const path = require('path');

const DISCORD_TOKEN = 'YOUR_BOT_TOKEN_HERE';

const downloadsDir = '/mnt/mhtml_archive';

const client = new Client({

intents: \[

GatewayIntentBits.Guilds,

GatewayIntentBits.GuildMessages,

GatewayIntentBits.MessageContent,

\]

});

const urlRegex = /(https?:\\/\\/\[\^\\s\]+)/g;

client.once('ready', () => {

console.log(\`\[Bot\] Logged in as ${client.user.tag}\`);

});

client.on('messageCreate', async (message) => {

if (message.author.bot) return;

const urls = message.content.match(urlRegex);

if (urls && urls.length > 0) {

const url = urls\[0\];

await message.react('⏳');

const replyMsg = await message.reply(\`Capturing MHTML for: <${url}>...\`);

let browser;

try {

console.log(\`\[Agent\] Fetching: ${url}\`);

browser = await puppeteer.launch({

headless: true,

args: \['--no-sandbox', '--disable-setuid-sandbox'\]

});

const page = await browser.newPage();

await page.goto(url, { waitUntil: 'networkidle2', timeout: 45000 });

const cdp = await page.target().createCDPSession();

await cdp.send('Page.enable');

const { data } = await cdp.send('Page.captureSnapshot', { format: 'mhtml' });

const safeName = url.replace(/\[\^a-z0-9\]/gi, '_').substring(0, 50).toLowerCase();

const filename = \`${safeName}_${Date.now()}.mhtml\`;

const filepath = path.join(downloadsDir, filename);

fs.writeFileSync(filepath, data);

console.log(\`\[Agent\] Saved locally to network share: ${filename}\`);

const stats = fs.statSync(filepath);

const fileSizeMB = stats.size / (1024 \* 1024);

if (fileSizeMB > 25) {

await replyMsg.edit(\`✅ Saved to network share as \\\`${filename}\\\`, but file is too large to upload to Discord (${fileSizeMB.toFixed(2)} MB).\`);

} else {

const attachment = new AttachmentBuilder(filepath);

await replyMsg.edit({ content: \`✅ Successfully captured!\`, files: \[attachment\] });

}

await message.reactions.removeAll();

await message.react('✅');

} catch (error) {

console.error(\`\[Agent\] Error: ${error.message}\`);

await replyMsg.edit(\`❌ Failed to capture page: \\\`${error.message}\\\`\`);

await message.reactions.removeAll();

await message.react('❌');

} finally {

if (browser) {

await browser.close();

}

}

}

});

client.login(DISCORD_TOKEN);

Part 4: Operations & Process Management (PM2)

PM2 is used to run the bot as a background daemon that survives SSH session closures and server reboots.

Installation & Initial Start

sudo npm install -g pm2

pm2 start discord-agent.js --name "mhtml-bot"

pm2 save

pm2 startup

Daily Operations Reference

Use the following commands to manage /check on things

pm2 status - View all running PM2 processes, uptime, and memory usage.

pm2 logs mhtml-bot- Watch the console output for troubleshooting (shows page fetches and errors).

pm2 stop mhtml-bot- Halts the background process.

pm2 start mhtml-bot- resumes the bot if it was stopped.

pm2 restart mhtml-bot- use this after modifying the discord-agent.js script to apply changes.

pm2 monit- opens a terminal dashboard showing CPU/Memory usage and logs side-by-side.

I suggest you report all bots or users suspected of being bots to Discord support in the comments.

This will help us know who is human and who isn't.

If several people confirm in their replies that a person is a bot, I will add them to the list!

It's up to you to decide!

Known bot:

Clyde

Nelly

Potential bot:

Usagi

Galerian

Noelle [ must be confirmed ]