The first time I set up an Eggdrop bot was in 1999, on a Pentium 133 running Slackware. It took me an entire weekend to get the Tcl scripts working right, and the bot crashed every few hours because I'd misconfigured the memory limits. But when it worked — when it sat in my channel, greeting users, managing bans, keeping the peace while I slept — it felt like magic. That feeling, I think, is why IRC bots became such a massive part of the culture.
Why Bots Existed in the First Place
On networks without services (NickServ, ChanServ), bots were essential infrastructure. If you ran a channel on EFnet in the 1990s, you needed a bot — full stop. Without one, your channel was vulnerable to takeover the moment all human operators went offline.
Here's the problem: IRC channels are ephemeral by default. When the last person leaves a channel, it ceases to exist. When it's recreated, whoever joins first gets operator status. On networks without ChanServ, this meant that a netsplit — which might cause half your channel's users to "leave" temporarily — could result in an attacker on the other side of the split gaining ops and taking over.
Bots solved this by being permanent residents. A well-configured bot stayed in the channel 24/7, held operator status, and could automatically re-op the legitimate channel operators when they returned after a split. It was the bouncer at the door, and the locksmith, and the security guard, all rolled into one.
But bots quickly grew beyond simple channel protection. People realized that a program permanently connected to IRC could do almost anything — relay information, run games, serve files, moderate content, provide search functionality, bridge to other networks, and a hundred other things nobody had anticipated.
Early Days: War Bots and Channel Protection
The earliest IRC bots were simple scripts, often written in C or Perl, that connected to a server and performed basic tasks. Some of the first bots were "war bots" — designed specifically for channel takeovers. They'd exploit netsplits to gain operator status, mass-kick or mass-ban the legitimate users, and hand the channel to whoever controlled the bot.
The counter to war bots was protection bots. These sat in channels and implemented defensive measures: monitoring for mass mode changes, detecting clone attacks (multiple connections from the same host), and automatically responding to takeover attempts. It was an arms race — takeover bots got smarter, protection bots got smarter, and the whole thing escalated through the mid-1990s.
Some notable early bots:
- GM (Global Message) bots: Among the earliest, used for relaying messages across channels and networks.
- NoteServ bots: Provided offline messaging before it was a network service — you could leave a note for someone, and the bot would deliver it when they next appeared.
- Trivia bots: One of the first "fun" bot types. They'd ask quiz questions and keep score. Channels like #trivia on various networks were hugely popular.
- XDCC bots: File-sharing bots that served files via DCC. These became a major part of the warez scene in the late 1990s.
Most of these early bots were custom-written, single-purpose programs. There was no framework, no plugin system — every bot was built from scratch, and the code was often passed around between friends or shared on websites. The quality ranged from elegant to terrifying.
Eggdrop: The Bot That Defined a Genre
Eggdrop changed everything. First released in 1993 by Robey Pointer, Eggdrop was the first widely-used modular IRC bot framework. Written in C with a Tcl scripting interface, it gave bot operators a stable, well-documented platform that they could extend without touching the core code.
What made Eggdrop special:
- Stability: Eggdrop could run for months without crashing. For the era, this was remarkable. Many custom bots had memory leaks that required regular restarts.
- Tcl scripting: You could write scripts in Tcl that hooked into bot events — channel joins, messages, mode changes. This lowered the barrier to customization enormously. You didn't need to be a C programmer to add features.
- Botnet support: Multiple Eggdrop bots could link together in a botnet (not to be confused with malicious botnets), sharing user databases and coordinating channel management across multiple channels or networks.
- User authentication: Eggdrop had its own user database with hostmask-based authentication and access levels. You could grant different levels of trust to different users.
- DCC support: Direct client-to-client connections for file transfer and a "party line" chat that only bot users could access.
The Tcl scripting ecosystem around Eggdrop was massive. Scripts were shared on sites like egghelp.org, and some of them were remarkably sophisticated — complete channel management systems, game engines, web interfaces for bot administration, and integrations with external services. At its peak, the Eggdrop script community was one of the most active open-source ecosystems around.
I've run Eggdrop bots on and off for over twenty years. The configuration file format hasn't changed much in that time — you can still take a config from 2001 and, with minor adjustments, run it on a current version. That kind of stability is rare in software.
Supybot and the Plugin Revolution
Supybot appeared in the early 2000s, written in Python by Jeremiah Fincher (jemfinch). If Eggdrop was the bot of the 1990s, Supybot was the bot of the 2000s. It brought a more modern architecture and a stricter plugin model.
Supybot's key innovations:
- Python: By 2003, Python was becoming the language of choice for many open-source developers. Supybot leveraged Python's readability and extensive standard library to create a bot that was easier to develop for than Eggdrop's C/Tcl combination.
- Plugin isolation: Each plugin ran in its own namespace with a well-defined API. Buggy plugins couldn't crash the whole bot (usually), and installing new plugins was as simple as dropping a directory into the plugins folder.
- Multi-network: Supybot could connect to multiple IRC networks simultaneously from a single process, which was more efficient than running separate Eggdrop instances.
- Built-in database: User records, channel data, and plugin state were stored in flat files with a consistent format, making backup and migration straightforward.
The plugin ecosystem was impressive. Supybot shipped with dozens of built-in plugins — RSS feeds, Google search, weather, dice rolling, seen tracking, karma, and more. Third-party plugins extended it further into territory like bug tracker integration, code repository monitoring, and natural language processing.
Limnoria: Supybot Lives On
When Supybot's original developer moved on, the project stagnated. Enter Limnoria — a fork maintained by Valentin Lorentz (ProgVal) and others, which became the de facto successor. Limnoria added Python 3 support, IRCv3 capabilities, SASL authentication, and numerous security improvements.
Limnoria remains one of the most actively maintained IRC bot frameworks in 2026. It's the bot I'd recommend to anyone starting today who wants a full-featured, well-documented platform with a mature plugin ecosystem. The learning curve is steeper than some alternatives, but the result is a bot that's genuinely reliable in production.
Modern IRC Bots and Frameworks
The current landscape of IRC bots is diverse:
- Sopel: Another Python bot framework, formerly known as Willie, then Jenni. It's lighter than Limnoria and focuses on ease of use. Good for simple utility bots where you don't need the full Supybot plugin architecture.
- Cinch: A Ruby-based IRC bot framework with a clean DSL. It never gained the user base of Python-based bots but is well-designed and pleasant to work with if you're a Rubyist.
- Irssi scripts: Not exactly bots, but Irssi's Perl scripting interface allows client-side automation that serves many of the same purposes as a traditional bot. Many IRC regulars have extensive Irssi script collections built up over years.
- Custom bots in Go/Rust: Modern systems programmers often prefer to write their own bots in Go or Rust, using libraries like girc (Go) or irc (Rust). These tend to be single-purpose bots rather than full frameworks.
There's also been a trend toward IRC bots that bridge to other platforms — Matrix, Discord, Slack. These relay bots keep IRC channels connected to modern chat platforms, which is increasingly important as communities spread across multiple services.
The Dark Side: Botnets and Abuse
No history of IRC bots is complete without acknowledging the darker side. IRC was the original command-and-control infrastructure for botnets — networks of compromised computers controlled remotely by an attacker. The infected machines would connect to a specific IRC channel and wait for commands.
This wasn't a coincidence. IRC's real-time, many-to-one communication model was perfect for botnet control. An attacker could issue a command in a channel, and thousands of compromised machines would receive it simultaneously. The protocol was simple enough to implement in a few hundred lines of code, making it easy to embed in malware.
The association between IRC and botnets did real damage to IRC's reputation. Network administrators spent enormous amounts of time fighting botnet traffic. Some networks implemented aggressive connection limits and proxy scanning specifically to combat botnet connections. The arms race between botnet operators and IRC network administrators was brutal and ongoing throughout the 2000s.
Modern botnets have largely moved away from IRC to HTTP-based command and control, which is harder to detect and block. But the legacy remains — IRC's association with botnets is still one of the first things non-technical people mention when you bring up the protocol.
Frequently Asked Questions
Is Eggdrop still maintained?
Yes. Eggdrop is actively maintained on GitHub, with version 1.9.x being the current release series. It supports modern features including IRCv3, TLS, and IPv6. The community is smaller than in the 1990s and 2000s, but the bot is stable and well-documented.
What's the best IRC bot framework in 2026?
For a full-featured bot with a large plugin ecosystem, Limnoria (the Supybot fork) is the strongest choice. For simpler needs, Sopel is easier to set up. Eggdrop remains excellent if you're comfortable with Tcl. For custom single-purpose bots, writing your own in Python, Go, or Rust using an IRC library is often the most efficient approach.
Were IRC bots the first chatbots?
Not exactly. ELIZA (1966) and other conversational programs predate IRC. But IRC bots were the first widely-deployed automated programs in a multi-user chat environment, and they pioneered many concepts — command parsing, plugin architectures, user authentication — that modern chatbot platforms use today.
Can IRC bots connect to modern chat platforms?
Yes. Bridge bots like Matterbridge and Heisenbridge relay messages between IRC and platforms like Matrix, Discord, and Slack. This allows IRC communities to stay connected with users on modern platforms without abandoning the IRC infrastructure they've built.
FAQ
What was the first IRC bot?
GM (Game Manager), written by Greg Lindahl in 1989, is generally considered the first IRC bot. It ran a Hunt the Wumpus game on channel #twilight_zone.
What is Eggdrop?
Eggdrop is the oldest actively maintained IRC bot, first released in 1993 by Robey Pointer. It's written in C with Tcl scripting and remains widely used for channel management.
Are IRC bots still relevant?
Yes. Bots handle channel protection, logging, integration with external services (Git, CI/CD), and moderation. Modern bots often use Python (sopel, limnoria) or Go, but Eggdrop is still deployed.