Forum | Features | Download | Patches | Help | #emech | Links | About | Contact |
Versions | News Archive | Installing | Linking | Configuration | Commands | FAQ |


See download page for distribution packages.

Configuring & Compiling

Same procedure as with versions 2.8.x, simply configure and make.

E3 has a wad of options in the config.h file that arent asked about in the configure script (yet), you might want to edit them to your liking. Everything (which is a lot) is enabled by default.

The Userfile

Since there is no genuser program for E3 yet, you have to make use of a little trick in order to make the first userlist(s) for your bot.

The ^D means press Ctrl-D, but you know that, right?

host:~> cat > trick.conf
set userfile myusers.filename
add handle * *!*ident@* 100 password

This is a "fake" configuration file of sorts. You obviously edit the name of the userfile to the one you need to create and the add command to fit yourself (and remember that E3 does not have the AOP and PROT values in the add command). If you dont want a password, simply dont enter one and you will be added with no password (which is insecure).

"Run" the configuration file;

host:~> ./mech -f trick.conf

The userlist will be created with the content of your add command in place.

Next step get rid of the trick config and make a proper config file (see sample.conf for hints).

Those commands in the config file are the exact same commands as you would use online. Thats one of the nice parts about E3, you dont need to learn commands that only apply in the config file.

This is all the help I can provide right now. Dont come to #emech asking trivial questions, E3 is still in the development stages and we expect you to be a developer if you come into #emech asking questions. We dont help newbies, ever.

The DCC filesend

New for version 2.99.70 is the DCC file transfer capability. It doesnt have many options sofar but basic transfers now work.

To use this feature you need to put the files you wish to transfer in a "public" subdirectory. If you for example run the EnergyMech from the directory "/home/luser/emech", you need to place the files you wish to make available in a directory called "/home/luser/emech/public".

On the IRC side, a user can simply type ".send <filename>" for the EnergyMech to send the file to them via DCC. Depending on how you set the command level for the 'send' command, it can be made available to the public. Change the command level to 0 (zero) to make it available to any user. The default command level for the 'send' command is 10 (ten) which would require users to be in the userlist in order to use the command.

The IRC Proxy

New for version 2.99.59 is the IRC proxy. It should work fine but it hasnt been tested much at all yet.

To enable it, you have to add one line to the mech.conf file;

set bncport <portnum>

portnum is the port that you want it to listen for connections on. Once its listening (you can check this in debug mode), you connect with your IRC client to the port and follow the on-screen prompts...

You will be prompted for a handle and a password which needs to be in the userlist. The user record also needs the special +BNC flag to be allowed access to the IRC proxy.

To set this flag for a user record, use the command;

user <handle> +bnc

The final step is to enter which server to connect to. You can also specify a port and a virtual host if there is any available.

The line could look something like; 6667

Both the port and virtual host is optional. If you dont specify a port, it will connect on port 6667. If no virtual host is specified, it will connect from the default interface of the shell box, which is usually what you go with.

You should probably ask your shell administrator for permission before running an IRC proxy. Shell admins typically charge for 2 background processes, one process for a bot and one process for an IRC proxy. The E3 combines these two elements into the same process and some admins could probably be a bit ticked off (most admins are cheap, they feel like you're cheating them out of their money when you squeeze more features into a single background process...).

Copyright © 2000-2005 Proton,  All rights reserved.  Last edited November 16th, 2004.