| View previous topic :: View next topic |
| Author |
Message |
gtfo Voice
Joined: 30 Jun 2009 Posts: 3
|
Posted: Tue Jun 30, 2009 2:07 pm Post subject: i am lost |
|
|
i have a bot that keeps automatically opping everyone that comes in a room although i have checked and dbl checked the config. it is set as follows when i do chaninfo for that room:
Protect modes (chanmode): +tn
Idle Kick after (idle-kick): DON'T!
stopnethack: DON'T!
aop-delay: 5:30
revenge-mode: 0
ban-time: 0
exempt-time: 60
invite-time: 60
Other modes:
-inactive +statuslog -secret -shared
-greet -seen -cycle +dontkickops
-protectops -protectfriends -revenge -revengebot
-bitch -autoop -autovoice -nodesynch
-enforcebans -dynamicbans -userbans -autohalfop
-protecthalfops
-dynamicexempts +userexempts -dynamicinvites -userinvites
User defined channel flags:
-portcheck
flood settings: chan ctcp join kick deop nick
number: 21 3 3 5 5 5
time : 60 60 60 10 10 60
correct me if i'm wrong, but doesn't -autoop means not to op ppl auto?
not only does he op everyone that comes in the room, but he ops ppl who arent even in his db as users. ppl hes never even seen before. i have been trying to figure this out for a week now and i give up. please help |
|
| Back to top |
|
 |
Sir_Fz Revered One

Joined: 27 Apr 2003 Posts: 3793 Location: Lebanon
|
Posted: Tue Jun 30, 2009 2:20 pm Post subject: |
|
|
What you need to know is that +autoop means the bot will op anyone with +o user-flag on the bot. I doubt that everyone's added on your bot as +o (this you need to check), and you also need to check if the channel is dynamically set as +autoop (regardless of what has been set in the config file). To check your channel settings use '.chaninfo #channel' and '.chanset' to modify them. Another thing that you need to consider is the possibility that you've loaded some script which is causing this behavior. _________________ Follow me on GitHub
- Opposing
Public Tcl scripts |
|
| Back to top |
|
 |
speechles Revered One

Joined: 26 Aug 2006 Posts: 1398 Location: emerald triangle, california (coastal redwoods)
|
Posted: Tue Jun 30, 2009 7:08 pm Post subject: Re: i am lost |
|
|
| gtfo wrote: | correct me if i'm wrong, but doesn't -autoop means not to op ppl auto?
not only does he op everyone that comes in the room, but he ops ppl who arent even in his db as users. ppl hes never even seen before. i have been trying to figure this out for a week now and i give up. please help |
The other alternative to this is you've given any user an +a for that channel. That user would be detected strictly by the nick!ident@host.mask (host) you've entered for them. Then without a need for a password (this is how +a differs from +o) they are "automatically" opped on join forever after. You need to .match +a|+a #your-chan-here and better define the host for any user that shows up, or better yet ditch that method and just use +o and make those users use the /msg bot op pass-here way. Networks with cloaked hosts (+x) obfuscate too much of the hostmask causing collisions (incorrect host matches) to occur out of coincidence (opping the wrong person accidentally) rather than by design (a user purposely spoofs your host to attain ops on join). Using +a is a good way to lose control of your channel. Using +o even with these collisions these people must still know the password for the user they are matched incorrectly against in order to become opped. _________________ speechles' eggdrop tcl archive |
|
| Back to top |
|
 |
gtfo Voice
Joined: 30 Jun 2009 Posts: 3
|
Posted: Mon Jul 06, 2009 6:19 pm Post subject: |
|
|
ok thanks guys.
after using the .match command i found the problem.
you guys are going to laugh, but here it is.
the owner of the room kept changing hostmasks and she had a +a flag
(y i gave channel owner +a i dunno, but...), but the bot wouldnt respond because she kept changing, so i had added *!*@*.*.*.* to cover her. well, obviously this was telling the bot to +a everyone. I simply removed the +a flag from her (she has +m and +o for the room witch should be ok) and the bot stopped opping everyone.
not a newb at computers, just a newb using eggies, so dont laugh too hard
thanks again |
|
| Back to top |
|
 |
Sir_Fz Revered One

Joined: 27 Apr 2003 Posts: 3793 Location: Lebanon
|
Posted: Mon Jul 06, 2009 7:12 pm Post subject: |
|
|
but everyone still has +m and +o. I recommend you find an alternative solution. _________________ Follow me on GitHub
- Opposing
Public Tcl scripts |
|
| Back to top |
|
 |
gtfo Voice
Joined: 30 Jun 2009 Posts: 3
|
Posted: Mon Jul 06, 2009 10:51 pm Post subject: |
|
|
yeah, well i have the channel owners set as masters in their channels and then i have ops set, or let them set their own for the channel.
there is only myself and one other person set as owners and so far that hasnt presented any problems. I set it up for ppl to use i just didnt know why he was opping everyone in that particular room until now. Clearly this is something where one needs to develop a good understanding of the flags and that is what I am doing. What would be a wise set up that you might suggest? I dont even really use the bot that much and just load whatever scripts ppl request and do whatever maintaining they cant. |
|
| Back to top |
|
 |
nml375 Revered One
Joined: 04 Aug 2006 Posts: 2857
|
Posted: Tue Jul 07, 2009 3:57 pm Post subject: |
|
|
I'd suggest you first remove the *!*@*... hostmask. Next add a few hostmasks matching the owner's different hosts, and tell her to try and not change hosts so much. If she really needs op/master privileges from another host, she could still use the IDENT/ADDHOST msg commands to add new hostmasks. _________________ NML_375, idling at #eggdrop@IrcNET |
|
| Back to top |
|
 |
|