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.
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
where is info stored
-
speechles
- Revered One
- Posts: 1398
- Joined: Sat Aug 26, 2006 10:19 pm
- Location: emerald triangle, california (coastal redwoods)
Re: where is info stored
That would be the user record...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.
By default the file should be named as above, and reside in your eggdrop's root folder. The channel record works the same way.default eggdrop.conf wrote:# Specify here the filename your userfile should be saved as.
set userfile "LamestBot.user"
[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.
[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.
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:
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: Select all
.match *!*@myweb.com
.match *!*I-Eagle@*NML_375