DEV Community: Julius

I built a Discord bot because I was tired of running five bots that didn't talk to each other

Julius — Mon, 20 Jul 2026 16:20:24 +0000

Every server I ran had the same problem. MEE6 for levels. Dyno for automod. Ticket Tool for support. Carl-bot for reaction roles. A music bot that got banned every six months. Five bots, five dashboards, five permission sets, five points of failure.

When one of them broke, I'd spend an hour figuring out which one. When a mod asked "why did this user get warned?", I'd have to check three different logs. When I wanted to know if my server was healthy, the answer was "I have no idea."

So I built Cipher.

What I wanted

A bot that handles the boring, high-stakes work of running a community:

Staff management. Who's on the team, who's active, who's on leave, who messed up.
File security. Quarantine and scan attachments before anyone clicks them.
AI ticket triage. Tell me if a ticket is angry, urgent, and what it's about — before I read it.
Verification. Stop raids before they start.
Community health. One number that tells me if my server is dying.

Not a music bot. Not a meme bot. Not a "100 commands you'll never use" bot. An operations bot.

What I learned building it

discord.js v14 is good but verbose. Intents, partials, slash command registration, permissions — there's a lot of boilerplate. I ended up with a cog system (like Red) to keep things modular.

AI integration is easier than people think. Most providers (Gemini, OpenRouter, Groq, Cerebras) have similar REST APIs. A simple abstraction layer lets you swap providers without rewriting code. The hard part is prompt engineering for sentiment and priority — models are optimistic by default.

File scanning is unglamorous but critical. Nobody thinks about it until someone drops a RAT in their #general. Local heuristics (magic bytes, entropy, extension mismatch) catch 80% of threats. VirusTotal and MalwareBazaar catch the rest. The boring part is the UX: delete the message, post a notice, DM the user, log it, apply an action. All of that matters more than the scan itself.

Community health is hard to define. Everyone wants a "health score" until you ask them what healthy means. I ended up with four sub-scores (growth, activity, retention, engagement) because no single number captures everything. The score is useful as a trend, not as an absolute.

Open source is the only honest model for Discord bots. You're asking people to give your code access to every message in their server. If that code isn't public, you're asking for blind trust. I'd rather earn it.

What's next

Cipher is live, free, and self-hostable. I'm adding more AI features (summarization, recommendation engine) and improving the dashboard. The goal isn't to compete with MEE6 — it's to be the bot you switch to when MEE6 isn't enough.

If you run a Discord community and you're tired of duct-taping five bots together: try Cipher. It's free, open source, and built by someone who's been there.

Side projects are just problems you got tired of solving manually.

Open-source Discord bots worth using in 2026

Julius — Mon, 20 Jul 2026 16:19:21 +0000

Most Discord bot lists are full of abandoned projects, premium upsells, and bots that harvest your server data. Here are the open-source ones actually worth running in 2026.

Why open source matters for Discord bots

When you add a bot to your server, you're giving it access to every message, every member, every attachment, and every voice channel. That's a lot of trust.

Closed-source bots can:

Change their terms overnight
Start selling your data
Get acquired and shut down
Push updates you never approved

Open-source bots can't hide anything. The code is public. You can self-host. You can audit. You can fork and modify.

The list

Cipher

Yeah, I'm starting with my own. Cipher is a community operations bot — staff management, AI ticket triage, file security scanning, verification, community health scoring, and AutoMod. No music piracy, no meme commands, no premium tiers.

GitHub: cipher-bot-v2
Self-hostable: Yes
License: Open source
Best for: Serious communities that need operations, not entertainment

Red Discord Bot

A modular, multi-purpose bot with a huge plugin ecosystem. Cog system means you install only what you need. Mature, well-maintained, and battle-tested.

GitHub: Cog-Creators/Red-DiscordBot
Self-hostable: Yes
License: GPL-3.0
Best for: Power users who want full control and don't mind setup

Modmail

A Discord modmail bot that lets members DM the bot to contact staff. Clean, simple, does one thing well.

GitHub: modmail-dev/modmail
Self-hostable: Yes
License: MIT
Best for: Servers that need a DM-to-staff pipeline

Ticketsbot

Open-source ticket system with transcripts, logging, and claim system. Focused and reliable.

GitHub: Eartharoid/Ticketsbot
Self-hostable: Yes
License: GPL-3.0
Best for: Support-focused servers

Autocode-based bots

Not a single bot, but a platform. Autocode lets you build Discord bots with JavaScript in a browser editor. Good for quick automations without a full server.

Website: autocode.com
Best for: Simple automations and prototypes

How to choose

Ask yourself:

Do I need to self-host? If yes, eliminate anything closed-source.
What's my #1 problem? Staff management → Cipher. Modmail → Modmail. Tickets → Ticketsbot. General-purpose → Red.
Do I trust the maintainer? Check commit history, issue response time, and whether it's actively maintained.
Is the license compatible with my use case? GPL-3.0 means modifications must stay open. MIT is more permissive.

The honest truth

Most servers don't need 10 bots. They need one or two that do their job well. If you're running MEE6 + Dyno + Ticket Tool + Carl-bot + Groovy, you're managing a zoo. Consolidate.

Try Cipher — one open-source bot for staff, security, tickets, and analytics.

Open source isn't just about price. It's about trust.

Discord community health — how to actually measure if your server is dying

Julius — Mon, 20 Jul 2026 16:11:42 +0000

Your Discord server has 5,000 members. That sounds great until you realize 4,200 haven't posted in three months, 600 are bots, and the remaining 200 are the same five people talking in #general every day.

Member count is a vanity metric. Here's how to actually measure community health.

The four metrics that matter

1. Growth (are new people joining?)

Not total members. Net new members per week minus leaves and bans. If you're gaining 50 members but losing 40, your growth is 10. That's the real number.

Track it weekly. A healthy community grows slowly and consistently. A spike followed by a cliff means something went wrong — a drama event, a bad announcement, a raid.

2. Activity (are people actually participating?)

Messages per day, active chatters per week, voice channel hours. The key metric is active chatters — people who posted at least once in the last 7 days.

If you have 5,000 members and 30 active chatters, your engagement rate is 0.6%. That's not a community. That's an audience watching five people talk.

3. Retention (are people staying?)

Of the people who joined 30 days ago, how many are still active? This is your 30-day retention rate. Healthy Discord communities see 15-30% retention. Below 10% means people join, look around, and leave.

Retention is the hardest metric to improve and the most important one. Growth without retention is a leaky bucket.

4. Engagement (are people interacting with each other?)

Not just posting — replying. Are conversations happening, or is it a monologue? Track replies per message and reactions per message. A server where people post but never reply is a billboard, not a community.

How to calculate a health score

Cipher uses a 0-100 score built from four sub-scores (0-25 each):

Growth score: net new members vs. historical average
Activity score: active chatters as % of total members
Retention score: 30-day retention rate
Engagement score: replies + reactions per message

A score of 70+ means your community is healthy. 40-69 means it's coasting. Below 40 means it's dying and you need to intervene.

What to do when the score drops

Growth dropping: Check your invite links. Are they still active? Is someone promoting the server? Are you listed on Disboard, top.gg, or Discord Me?

Activity dropping: Run an event. A game night, a Q&A, a giveaway. Something that gets people in voice or typing. Temporary spikes are fine — they remind people the server exists.

Retention dropping: Look at your onboarding. Do new members get welcomed? Do they understand what the server is for? A confusing first experience kills retention.

Engagement dropping: Ask questions in #general. Start discussions. Tag people who haven't posted in a while. Communities die when nobody asks anything.

The dashboard trap

Don't build a 47-metric dashboard. You'll look at it once and never again. Four numbers, checked weekly, acted on immediately. That's it.

Try Cipher's community health score — one number, four sub-scores, actionable tips. Free and open source.

If you're not measuring it, you're not managing it.

How to stop Discord raids before they start — a verification gateway guide

Julius — Mon, 20 Jul 2026 16:09:36 +0000

A raid is the moment your server stops being a community and starts being a crime scene. Twenty bots join in 10 seconds, post slurs in every channel, and your mods are still asleep.

Verification gateways stop this before it happens.

What a verification gateway does

Every new member lands in a single channel. They see one button or one reaction prompt. Until they click it, they can't see the rest of the server, can't post anywhere else, and can't mention anyone.

That's it. One click between your server and chaos.

Why Discord's built-in verification isn't enough

Discord has a native verification level setting (Settings → Safety Setup → Verification Level). It requires email or phone verification before a user can post. Useful, but:

It doesn't stop humans with verified accounts
It doesn't slow down coordinated raids
It doesn't let you customize the flow
It doesn't log who verified and when

A bot-based gateway gives you control.

The three gateway patterns

1. Reaction gateway. A message in #verify says "React with ✅ to gain access." User reacts, bot assigns the Member role, user sees the server. Simple, fast, stops most bots.

2. Button gateway. Same idea, but with a Discord button. Cleaner UX, works on mobile, and you can track clicks. Cipher uses this by default.

3. Question gateway. User has to answer a simple question ("What server is this for?" or "Read the rules and type the keyword"). Filters out drive-by spam and forces people to actually read something.

What to do after verification

Auto-assign a role. Don't leave them with @everyone only. Give them Member so you can revoke it later if needed.
Log it. Who verified, when, from what invite. If someone causes trouble later, you have a trail.
Welcome them. A DM or channel message after verification increases retention. People who feel welcomed stay longer.
Slow-mode the verify channel. 10 seconds is enough. Stops spam without annoying real users.

The raid scenario

Without a gateway: 20 bots join, all post in #general simultaneously, your server is a mess for 20 minutes until a mod wakes up.

With a gateway: 20 bots join, all land in #verify, none of them click the button, your server is untouched. You wake up, see 20 unverified accounts, ban them all in two clicks.

Common mistakes

Making verification too hard. CAPTCHAs, 10-step forms, essay questions. People leave. One click or one short answer is enough.
No logging. If you don't track who verified, you can't audit later.
Forgetting to remove the role when banning. Banned users keep their roles in some setups. Clean up properly.
No slow-mode. A raided verify channel is useless if 200 messages bury the button.

Where Cipher fits

Cipher has a built-in verification gateway — reaction or button based, auto-role assignment, logging, and configurable welcome messages. Set it up once and forget about it.

Try Cipher for free — verification, file security, AutoMod, and community health in one bot.

The best raid response is the one that never happens.

Discord staff management — a practical guide for growing servers

Julius — Mon, 20 Jul 2026 13:24:05 +0000

At 50 members, your server is a group chat with extra steps. At 5,000 members, it's an organization. And organizations need management.

Most Discord servers fail not because of trolls or drama, but because their mod team falls apart. People burn out, go inactive, argue over who banned who, and eventually leave. The solution is a staff system.

What a staff system actually tracks

Roster. Who is on the team, what role they have, when they joined, how to contact them. Sounds basic, but most servers don't have this written down anywhere.

Activity. How many mod actions did each person take this week? How many tickets did they handle? How much time in voice? Without data, you can't tell who is carrying the team and who is coasting.

Leave of absence. Real life happens. Your best mod has exams, a new job, a health issue. A formal LOA system means you know who is unavailable instead of just assuming they quit.

Infractions. Mods mess up too. They ban the wrong person, overstep, go rogue. A staff infraction log means you can address it privately instead of letting it fester into public drama.

The tools most servers use instead

A #staff-chat channel
A pinned message with role assignments
Memory

This works until it doesn't. Scattered information, no accountability, and a ton of context that disappears when someone leaves.

A better setup

Use a bot that records staff activity automatically:

Mod commands (/warn, /kick, /ban)
Ticket handling
Messages in mod channels
Voice time in staff channels

Then review weekly. Not to micromanage, but to notice when someone is overwhelmed or missing.

Also: remove Administrator from everyone except the owner. Give scoped permissions. A mod who can delete the server is a mod you don't actually trust yet.

The 5-minute weekly review

Every Sunday, ask yourself:

Who was active this week?
Who is on LOA?
Any infractions to address?
Are tickets being handled on time?
Does anyone need help?

Five questions. More useful than any dashboard.

Where Cipher fits

Cipher has a built-in staff system: roster, LOA, daily activity tracking, and infractions. Activity is auto-captured from mod actions, ticket handling, and voice time. You get the data without chasing people down.

Try Cipher for free — built for communities that outgrew the group-chat phase.

Good mod teams don't happen by accident. They happen by design.

How to set up AI ticket triage in Discord without paying for Zendesk

Julius — Mon, 20 Jul 2026 13:11:44 +0000

Discord ticket bots are dumb. Someone opens a ticket, it lands in a channel, and your mods have to read the whole thing to figure out if it's urgent. By the time they do, the user has already left the server.

There is a better way. AI ticket triage isn't magic — it's just fast classification.

What ticket triage actually means

For every incoming ticket, you want to know three things immediately:

How angry is the user? (sentiment)
How urgent is this? (priority)
What is this actually about? (category)

A human takes 2-3 minutes to figure this out. A model takes 2-3 seconds.

Why Discord needs this

Discord support is different from email support. Tickets are public to your staff, often emotional, and usually tied to a real-time community event. A payment issue in a server with a live product launch is not the same as a general question. Context matters.

AI triage lets you:

Route urgent/angry tickets to senior mods immediately
Label tickets as payment, ban appeal, bug, harassment without reading them
Suggest a first reply draft your team can edit and send
Spot patterns — e.g. 12 tickets in one category means something is broken

How to set it up in Cipher

Cipher analyzes the first message of a ticket and stores:

sentiment: positive, neutral, negative, or urgent
priority: low, medium, high, critical
category: payment, report, appeal, bug, general, etc.
ai_summary: a 1-2 sentence summary
suggested_reply: an editable draft response

The AI runs on your configured providers (Gemini, OpenRouter, Groq, Cerebras). You bring your own keys, so no extra subscription.

The workflow

User opens a ticket
Cipher classifies it in the background
Mods see the ticket with labels already applied
Senior mods grab critical tickets first
Junior mods use the suggested reply as a starting point

Result: faster responses, less mod burnout, fewer missed crises.

The catch

AI triage is not a replacement for human judgment. It's a filter. The model can misread tone, miss context, or be too polite. Always let a human review the suggested reply before sending.

But compared to a raw ticket stream? It's night and day.

Try Cipher's AI ticket triage — free, open source, and it runs on your own AI keys.

No Zendesk required.

Why MEE6 isn't enough for serious Discord communities

Julius — Mon, 20 Jul 2026 13:11:38 +0000

MEE6 is fine for a gaming server of 50 friends. It's not fine for a community that actually matters.

I've run communities from a few hundred members to tens of thousands. At some point, every admin hits the same wall: MEE6 does a lot, but it doesn't do the things that keep a real community alive.

What's missing

Staff management. MEE6 has levels and roles, but it has no concept of a mod team. No roster, no leave-of-absence tracking, no way to see which mods are active and which ones are coasting. When you scale past 10 mods, you need a system.

File security. MEE6 won't quarantine a .exe someone dropped in chat. It won't scan attachments, won't check hashes against VirusTotal, won't DM your members that they almost downloaded malware. It just lets it sit there.

Real tickets. MEE6 has a ticket plugin, but it doesn't triage. It doesn't tell you "this ticket is urgent and angry" before a human opens it. It doesn't suggest a reply draft based on the conversation.

Community health. MEE6 shows you levels and command usage. It doesn't tell you whether your server is growing healthily or bleeding members. It doesn't warn you three weeks before your community goes stale.

What a serious operations bot looks like

A server ops bot should be invisible infrastructure. It should:

Catch dangerous files before anyone clicks them
Route tickets to the right person with the right priority
Track which staff are active and which are missing
Tell you if your community is healthy or dying
Not spam you with premium upsells

That's what I built Cipher for. It's open source, free, and handles staff, security, tickets, verification, and analytics in one bot.

When to switch

You have more than 5 staff members
You ever had a malware file sit in chat for an hour
You run support tickets and wait hours for the right mod to see it
You don't know your monthly retention rate
You're paying for three bots that don't talk to each other

If that sounds like you, the all-in-one entertainment bot phase is over. You need an operations bot.

Try Cipher for free — staff system, file security, AI ticket triage, and community health in one open-source Discord bot.

Written by someone who has cleaned up too many 2am Discord crises.

5 Discord security mistakes every server admin makes

Julius — Mon, 20 Jul 2026 12:51:23 +0000

Most Discord servers get compromised because of the same five mistakes. Not zero-days, not sophisticated attacks — just basic hygiene that nobody told admins about.

I've been running Discord communities for years and built an open-source bot called Cipher that handles most of these automatically. Here's what I learned.

1. Trusting every attachment

Discord doesn't scan files. If someone uploads invoice.pdf.exe in your #general channel, it stays there until a mod notices — by which point 200 people may have downloaded it.

Fix: Use a bot that quarantines suspicious attachments automatically. Cipher scans every file with a dangerous extension (.exe, .bat, .scr, .jar, archives) before it reaches your members. Local heuristics plus optional VirusTotal and MalwareBazaar lookups.

2. No verification gateway

Anyone can join, anyone can post. Bots, alts, and ban evaders walk straight in.

Fix: Reaction or button verification. New members have to click a button or react to a message before they can see the rest of the server. Slows down raids, filters drive-by spam.

3. Giving mods admin permissions

Every mod with Administrator is a liability. One rogue mod, one compromised account, and your server is gone.

Fix: Use a proper staff system with scoped permissions. Cipher has a staff roster with leave-of-absence, daily activity tracking, and infractions — so you can promote people without handing them the keys to the kingdom.

4. No idea what's happening in your server

You don't know your retention rate. You don't know which channels are dead. You don't know if your mods are actually doing anything. You're flying blind.

Fix: A community health score. Cipher calculates a 0-100 score from real activity data: growth, engagement, retention, mod activity. You get actionable tips, not vanity metrics.

5. Five bots doing one job each

MEE6 for moderation. Dyno for automod. Ticket Tool for tickets. Carl-bot for reaction roles. Groovy for music. Five bots, five permission sets, five points of failure.

Fix: Consolidate. Cipher handles moderation, tickets, verification, file security, and analytics in one bot. Open source, free, self-hostable.

What to do now

Audit your server for these five issues today
Remove Administrator from any mod who doesn't need it
Set up file scanning and verification
Start tracking your community health

If you want a bot that handles all of this without five separate subscriptions: Cipher is free and open source. Add it to your server in one click.

This article is part of a series on running Discord communities that actually work. Follow for more.