ok with some testing, I moved the alias Check_idle to the top of the code and took out the -l ...but now it just seems to have a problem if i set the idle limit above 2 mins. I get this:
* /timer: timer 1 not active
* /timer: timer 1 not active
* /timer: timer 1 not active
* /timer: timer 1 not active
* /timer: timer 1 not active
* /timer: timer 1 not active
* /timer: timer 1 not active
* /timer: timer 1 not active
Ok not all of my op's and hop's use mIRC so they didnt have a /omsg or /msg @%&#chan...Plus its fun to have a bot that they can make talk like a /bs say command. so this is designed for a mIRC bot in your #. This will also close all pm's after it looks for the commands, So if you like to keep the PM window open or get them from people wanting to chat then take out the last line of code "Closemsg..
I modified yours some, But gave you credit for the real work.
http://www.hawkee.com/snippet/5376/
I dont choose the admin's the owner does, I just control the bot. And with about 30+ bans a day, you would lose track of what bans can be cleared and what ones cant. we get about 5000 joins per # everyday....its nice to have a way to make sure the real bad ones dont come back.
And no it dont kick clones, my clone kicker does that =) But once the host is banned the clones cant talk in the # anymore anyway.
Ok I saw someone had a "Point System" on here, well I didnt like it (sorry). It didnt have any type of promotions. So this code Is setup for a irc that has Op and Hop. at 3 points the person gets a voice. At 10 points (if given by a OP not a Hop) the person gets Hop. If they get demoted below that score they lose the promotion.....Most people dont need this type of thing but our # runs 24/7 with at..