Ok, Sorry about all the confusion. The below works (tested), but again with no timer. bind pub o|o !ban4 pub:bannokick proc pub:bannokick {nick host hand chan text} { global botnick set target [lindex $text 0] set reason [lrange $text 0 end] set bhost [getchanhost $target $chan] set banmask "*!...
This is a snippet from Eggdrop Toolz v2.01 for Eggdrop v1.3.4 & up by tzun # Start KickBan proc msg_kban {nick host hand chan text} { global botnick set target [lindex $text 0] set reason [lrange $text 0 end] set bhost [getchanhost $target $chan] set banmask "*!*[string trimleft [string ran...
# set banmask "*!*someuserid@*.some.host *somenick*!*@1.2.3.*" set banmask "*!*someuserid@*.some.host *somenick*!*@1.2.3.*" Homie22!Homie@22.04.23.233 To ban the nick Homie22 you'd need to change it to; set banmask "Homie22!*@* Homie22!*@*" To ban the ident Homie you'd ...
set bmask_chans "#channel_1 #channel_2" change #channel_1 and #channel_2 to the channels you want the bot to set bans on #yourchannelname # Ban duration in minutes set bmask_time 15 duration you want the ban to last # Ban reason set bmask_reason "Sample ban reason" the stated rea...
You just need to understand the format for these bans. Basically there are three parts seperated by two modifiers ! and @ irc nickname ! ident @ isp Idents are a setting you configure in your irc client running off your computer, so they can be a very useful thing to ban if you want to target a spec...
Nope I've run it again to make sure, it does not say "end of list" either on the channel nor in the console. As for networks, thats a good point. If you will be releasing this script publicly, you may need to have a bind there that people can change depending on their network, be it efnet ...
It's definately coming along nicely :) A few bugs.... but it's definately working. Here's my output with; !Oplist #Channelname Note that there is no info in the founder field. <@Debates> #debates - Founder: : | SOps: Godric, Shamrock, Zotnix, Ozymandias, EnglishGent, Elduran, Debates, ragle, NiteOwl...
Think I found a bug :) When I tried it, I forgot to put the channel name in, putting JUST !aoplist The result was that it IMMEDIATELY tried to get the aop list for every channel the bot is in. Services ended up placing the bot on ignore. When I did a .restart it came back online and did it again, fo...
Agreed, that does seem like the best way to go about it. There's no need to update the list every time it logs on, just whenever a user is added or removed from the bot I would think.
The link works fine and the scripting looks awesome, but the script does not seem to work yet. Have you been able to make it work on your own bot? I am not getting any error messages at all, it simply does not seem to react to the trigger. Here are my binds; bind notc fS|- "*Info* for*" cs...