Académique Documents
Professionnel Documents
Culture Documents
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Contents
~~~~~~~~
Section 1: Initial Setup
=======================================================================
====
If you start your bot without running the genuser script first you will
get
output similar to the following:
This is just the last few lines of output but you can see it even tells
you
what you didn't do (create the userlist) and how to fix the problem
(running
genuser).
./genuser emech.users
The script is very simple to use and comes with complete instructions
onscreen. Just make sure you follow the prompts for Handle and
Hostmask.
Look at the examples shown in genuser if you are not too sure.
If it fails then make polite enquiries about it and you might get
answered.
In the next section you will find out how to add the general users.
Read it
carefully.
=======================================================================
====
NOTE: The bot will let you add users to channels that the bot isn't in
or
channels that don't even exist.
There are two ways you could add yourself to your bot. You can message
the
add command to it or you can type it in the channel. Both methods
provide
the desired result - the user is added.
nick/
userhost - You can put the bot users nick here or
you can specify a userhost mask (e.g.
*!*user@*.host.com). The bot will let
you add using a stupid userhost mask so
be carefull and think before you add.
No matter which method you choose to add a user to your bot the outcome
will
be the same. You will get either an error message or a confimation
that the
user has been added.
Here are some examples of error messages and the commands that produce
them.
Example 1:
There are probably other ways to produce errors from using the add
command.
If you stick to using the add command by following the breakdown above
then
you can't go too far wrong (if you do consider yourself special and
beyond
help).
When you actually add the user correctly you will get something similar
to
the following example.
Example 2:
-AddBot(azmodan@phrozen.gen.nz)- azmodan has been added as
*!*azmodan@*.gen.nz on *
-AddBot(azmodan@phrozen.gen.nz)- Access level: 100 Auto-op: No
Protect level: 0 Password: changeme
If you got this then congratulations you have now added your first
general
user and can have a cookie (NOTE: Cookies have been discontinued).
At this point you might want to issue a save command e.g. /msg botnick
-save.
Use your own bot nick and your own command character.
The user level is important when adding general users. You should only
give
them the level required to get their job done. If you don't want user
joebloggs to have the ability to issue the die command then don't give
him/her level 100 access. Consult the Default Command Levels in
Appendix ii
when you are making up your mind what level to add a user at.
To add a user to more than one channel you need to add them with a
different
handel for each channel.
If you stick to the breakdown above you can't go very wrong when adding
users.
In the next section you will learn how to remove users.
=======================================================================
====
Before deleting a user you need to know the handle that you added them
with.
If you don't know it or want to double check and make sure then you can
use
the userlist command e.g. /msg botnick -userlist. Check in the list
that
comes up for the user you want to delete and note the handle.
You have decided to delete the user with the handle of rogue. You can
do
this one way by using the del command.
Example 3:
Command: /msg addbot -del trustme
Response: -AddBot(azmodan@phrozen.gen.nz)- User trustme has been
purged
This is a successfull delete. The user record is now gone. Check with
/msg
botnick -userlist if you want to double check.
If you had specified an unknown handle then the bot will tell you that
you
have made a mistake.
Example 4:
Command: /msg addbot -del rogue2
Response: -AddBot(azmodan@phrozen.gen.nz)- Unknown handle
Error: The handle rogue2 did not exist so could not be
deleted.
If this happens to you then check the handle in the userlist again and
get
it right this time! Repeat the process for each user that you want to
remove.
=======================================================================
====
If you do a /whois nick on your user you will get the information that
you
need to decide on the hostmask.
Example 5:
Whois: Rogue (barky@irc.phrozen.gen.nz)
Hostmask: *!*barky@*.phrozen.gen.nz
Notes: This mask will match on barky@skippy.phrozen.gen.nz or
barky@irc.phrozen.gen.nz. The '*' is a wildcard that
stands for anything.
Example 6:
Command: /msg addbot -host add trustme
*!*barky@*.phrozen.gen.nz
Response: -AddBot(azmodan@phrozen.gen.nz)- Added mask
*!*barky@*.phrozen.gen.nz to user trustme
Notes: This is a good hostmask that leaves little room for
being abused by other users.
You can add as many hostmask to a user as you need. These hostmasks
allow
users access to the bot from any different shell accounts or ISP
accounts
that they may have.
Of course from time to time you may wish to remove hostmasks from
users.
This is explained in the final section.
=======================================================================
====
Example 7:
Command: /msg addbot -host del trustme
*!*barky@*.phrozen.gen.nz
Response: -AddBot(azmodan@phrozen.gen.nz)- Deleted mask
*!*barky@*.phrozen.gen.nz from user trustme
Notes: All their other hostmasks remain. Only the one in the
delete command is actually removed.
Thats all there is to hostmask deleting and also the end of the Dummies
Guide To Adding Users. I hope you have found this document helpfull and
that have many hours of fun adding and removing various things from your
users.
***********************************************************************
****
Appendicies
~~~~~~~~~~~
Appendix i: Protection Levels
0 No protection.
1 Reop/unban, do nothing to offender.
2 Reop/unban, deop offender.
3 Reop/unban, kick offender.
4 Reop/unban, kickban offender.
-----------------------------------------------------------------------
----
These are the levels of all the commands a bot will accept. Use this
list to determine what you give your bot users access to.
Level 70: cycle, esay, join, ks, kslist, part, rks, setpass
Level 100: core, debug, die, reset, shutdown, spawn, uset ( msconfig )
-----------------------------------------------------------------------
Login form
.uLogBlock
{margin:0;padding
:2px;clear:both;}.u
LogDescr,.uLogRe
m
{float:left;}.uLogF
ield,.uLogSbm
{float:right;}
Login:
Parola:
remember
Am uitat parola ·
Register
News calendar
«
D
ec
e
m
be
r
20
08
»
S M T WT
Fr Sa
u o u e h
1 2 3 4 5 6
7 8 9 10 11 12 13
1415 1617 18 19 20
2122 2324 25 26 27
2829 3031
----