| View previous topic :: View next topic |
| Author |
Message |
tassat Voice
Joined: 06 Jun 2008 Posts: 5
|
Posted: Sun Feb 08, 2009 10:08 pm Post subject: where is info stored |
|
|
when people join my server my eggdrop bot gives them a +h or +v depending on what was assigned to them.
what i want to know is where the information about what to do to who is. |
|
| Back to top |
|
 |
TCL_no_TK Owner

Joined: 25 Aug 2006 Posts: 509 Location: England, Yorkshire
|
Posted: Mon Feb 09, 2009 10:59 am Post subject: |
|
|
Eggdrop shouldn't really do this Automatically. If this is done by a script, i would just read the script and look at what it is doing. _________________ TCL the misunderstood |
|
| Back to top |
|
 |
speechles Revered One

Joined: 26 Aug 2006 Posts: 1398 Location: emerald triangle, california (coastal redwoods)
|
Posted: Mon Feb 09, 2009 5:43 pm Post subject: Re: where is info stored |
|
|
| tassat wrote: | when people join my server my eggdrop bot gives them a +h or +v depending on what was assigned to them.
what i want to know is where the information about what to do to who is. | That would be the user record... | default eggdrop.conf wrote: | # Specify here the filename your userfile should be saved as.
set userfile "LamestBot.user" |
By default the file should be named as above, and reside in your eggdrop's root folder. The channel record works the same way. _________________ speechles' eggdrop tcl archive |
|
| Back to top |
|
 |
tassat Voice
Joined: 06 Jun 2008 Posts: 5
|
Posted: Wed Feb 18, 2009 5:52 pm Post subject: |
|
|
[15:41] * Joins: I-Eagle (~I-Eagle@myweb.com)
[15:41] * ChanServ sets mode: +ao I-Eagle I-Eagle
[15:41] * Chasey sets mode: +h I-Eagle
thats what i'm getting this user is not in the user file at all.
it's like the bot is doing it based on the host??
there is no script that i am running that sets users modes.
i have no clue what doing this. |
|
| Back to top |
|
 |
nml375 Revered One
Joined: 04 Aug 2006 Posts: 2857
|
Posted: Wed Feb 18, 2009 8:04 pm Post subject: |
|
|
User identification is indeed done by hosts. Or rather, "hostmasks", on a first-match basis.
As soon as eggdrop finds a mask matching the nick!user@host of the client, the associated handle is considered being the user. Any flags for this handle is then cared for (auto-op, etc), as well as permissions for commands.
You could try to use the .match command to try and figure out which handle is the cause of all this.
Try something like this:
| Code: | .match *!*@myweb.com
.match *!*I-Eagle@* |
_________________ NML_375, idling at #eggdrop@IrcNET |
|
| Back to top |
|
 |
|