The EnergyMech is a fully functional IRC bot, written entirely in the C programming
language. It has common features such as userlists, shitlists, channel protection, DCC partyline,
botnet and lots more.
The EnergyMech started out as a hack of the combot but is today quite different and more sophisticated.
One of the main ideas of the EnergyMech is that it should be easy both to setup and use. The popular
eggdrop requires that TCL is installed on a system for it to compile sucessfully, the EnergyMech has no
such requirements. A person that is familiar with UNIX would have no trouble installing an EnergyMech
and getting it up and running.
Compiles and runs on most any standard UNIX!
The EnergyMech was developed primarily for Linux and Solaris, however it functions perfectly OK on most other types of unices
with a few exceptions based on compile-time options. Successful compilations has been reported for AIX, BSD/OS, FreeBSD, HP-UX,
IRIX, Linux, NetBSD, OpenBSD, OSF/1 (DEC UNIX), SunOS 4.x and Solaris (SunOS 5.x).
Installs quickly, easy to configure and easy to run!
With a bit of experience, an EnergyMech normally doesn't take more than a few minutes to download, compile, configure and run.
With precompiled distributions it's quite possible to get a mech up and running within a couple of minutes!
Run more than one bot in a process and link them with others!
The EnergyMech can be configured to link with other EnergyMechs, creating botnets with partyline, remote execution of commands
and autoopping of bots to keep channels safer! Bots in the same process are virtually linked at all times.
Advantages of multi-head bots.
Very low CPU and memory usage!
The EnergyMech has been designed to use only small amounts of memory and process time. This will enable you to run more bots
without using up large amounts of resources.
IRC proxy services in the same process as the bot!
Yes indeed, there is no need to run any extra process in order to get an irc bouncer for your favourite virtual host!
||Eggdrop 1.6 |
|Multi-head (Many bots in the same process) ||Yes||Yes||No|
|Partyline (DCC, Telnet)||Yes||Yes||Yes|
|Dynamically Loadable Modules||No||No||Yes|
|Scripting (Perl)||No||(Yes) ||No|
|Scripting (Python)||No||(Yes) ||No|
|Advanced notify & nick tracking||No||Yes||No|
|File transfer (DCC)||No||Yes||Yes|
|Dependencies||EnergyMech 2.8||EnergyMech 3.0||Eggdrop 1.6|
Typical memory usage
Minimum install size
|Diskspace needed to compile||2.3MB||3.2MB||8.7MB|
 At the time this comparison was made, versions used was: EnergyMech 2.9.4, EnergyMech 2.99.77 and Eggdrop 1.6.17.
 (Yes) features are not yet functional in the v2.99 releases, but will hopefully be fully functional by the time v3.0 is released.
 Memory usage is counted in actual physical memory which can vary greatly from system to system, the test was made on the same system tho so numbers should be comparable.
|AIX, BSD/OS, HP-UX, IRIX, NetBSD, OpenBSD, OSF/1 (DEC UNIX), SunOS 4.x||2.8 compiles OK, 2.99 untested|
|FreeBSD, Linux, Solaris||2.8 and 2.99 compiles OK|
|Win32||2.8 and 3.0 compiles OK with Cygwin|
Copyright © 2000-2005 Proton, All rights reserved.
Last edited August 18th, 2005.
HTML 4.01 CSS