ChanServ Auto Need Script problem very detailed inside

[killer-instinct]

ChanServ Auto Need Script2.28.b by awyeah isnt working
it appears to load fine

[22:16] [LOADED] ChanServ Auto Need Script v2.28.b by awyeah (awyeah@usa.net)
[22:16] *NEED OP* is ACTIVE on: #pwnt
[22:16] *NEED UNBAN* is ACTIVE on: #pwnt
[22:16] *NEED INVITE* is ACTIVE on: #pwnt
[22:16] *NEED LIMIT* is ACTIVE on: #pwnt
[22:16] *NEED KEY* is ACTIVE on: #pwnt
[22:16] [LOADED] ChanServ Auto Reop Script v5.61.b by awyeah (awyeah@usa.net)
[22:16] *ENABLED* Auto Reop for Bubba on: All channels

but when i test by deopping the bot (with a unknow user to him) i does this

NEED OP [#PWNT]: Need to regain ops back on #pwnt.
NEED OP [#PWNT]: *REOPPING* myself on #pwnt with Chanserv.
NEED OP [#PWNT]: Need to regain ops back on #pwnt.
NEED OP [#PWNT]: *REOPPING* myself on #pwnt with Chanserv.
NEED OP [#PWNT]: Need to regain ops back on #pwnt.
NEED OP [#PWNT]: *REOPPING* myself on #pwnt with Chanserv.
NEED OP [#PWNT]: Need to regain ops back on #pwnt.
NEED OP [#PWNT]: *REOPPING* myself on #pwnt with Chanserv.


but it never reops itself

here is how i have it setup

##################################################
### Start editing variables from here onwards! ###
##################################################

#---------------------------------------#
# SETUP NETWORK CHANSERV VARIABLE #
#---------------------------------------#

#Set your ChanServ service nick here. (This is a case-senstivie setting)
#USAGE: Set the nick of your networks channel service here. For example 'ChanServ'.
#(If your network uses ChanServ and is not DALnet, set this to only 'ChanServ' then)
#(If your network is DALnet, then you do not need to edit this as I have set this to default for DALnet)
set needchanserv "Chanserv"


#------------------------------#
# SETUP NEED-OP VARIABLES #
#------------------------------#

### IMPORTANT - PLEASE READ ###
#This is the most important variable in the entire script.

#Please enable this variable if you want your eggdrop bot to always have ops on channels you define for it
#or on all channels the bot is on. The bots internal timer will request ChanServ to reop it after a delay
#of every 20-30 secs if it gets deoped.

#If supposingly the bot is deleted from the ChanServ access list of a channel mentioned in the working
#channel list, this script will still try to regain ops from ChanServ. It might flood ChanServ and irc
#operators might kill the bot for services flooding.

#Please enable this setting on channels only which you eggdrop bot has channel ops (ChanServ access) on.
#If it has access on all channels it is on, then only enable the all channels feature, otherwise not.
#If suppose your eggdrop is deleted from any of the ChanServ access lists, then please also remove it
#immediately from this scripts user defined channels and rehash it, so it doesn't flood services or
#request ops from ChanServ on channels where it doesn't have access, as ChanServ will deny it.

#Set the type of channels on which you would like the 'NEED-OP' script to work on.
#USAGE: [1/2] (1=USER DEFINED CHANNELS, 2=ALL CHANNELS) (You can enable only one, not both!)
#Use '1' for 'user defined channels'. (Will make the need-op command work on channels only mentioned by the user)
#Use '2' for 'all the channels' the bot is on. (Will make the need-op command work on all channels the bot is on)
set needoptype "1"

#Set this only if you have enabled the previous setting to '1' (user defined channels). Set here the working
#user defined channels you want the 'need-op' command to work on, if not then leave this setting empty/blank.
#USAGE: set needopchans "#channel1 #channel2 #channel3 #mychannel #yourchannel"
set needopchans "#pwnt"


#---------------------------------#
# SETUP NEED-UNBAN VARIABLES #
#---------------------------------#

#Set the type of channels on which you would like the 'NEED-UNBAN' script to work on.
#USAGE: [1/2] (1=USER DEFINED CHANNELS, 2=ALL CHANNELS) (You can enable only one, not both!)
#Use '1' for 'user defined channels'. (Will make the need-unban command work on channels only mentioned by the user)
#Use '2' for 'all the channels' the bot is on. (Will make the need-unban command work on all channels the bot is on)
set needunbantype "1"

#Set this only if you have enabled the previous setting to '1' (user defined channels). Set here the working
#user defined channels you want the 'need-unban' command to work on, if not then leave this setting empty/blank.
#USAGE: set needunbanchans "#channel1 #channel2 #channel3 #mychannel #yourchannel"
set needunbanchans "#pwnt"


#----------------------------------#
# SETUP NEED-INVITE VARIABLES #
#----------------------------------#

#Set the type of channels on which you would like the 'NEED-INVITE' script to work on.
#USAGE: [1/2] (1=USER DEFINED CHANNELS, 2=ALL CHANNELS) (You can enable only one, not both!)
#Use '1' for 'user defined channels'. (Will make the need-invite command work on channels only mentioned by the user)
#Use '2' for 'all the channels' the bot is on. (Will make the need-invite command work on all channels the bot is on)
set needinvitetype "1"

#Set this only if you have enabled the previous setting to '1' (user defined channels). Set here the working
#user defined channels you want the 'need-invite' command to work on, if not then leave this setting empty/blank.
#USAGE: set needinvitechans "#channel1 #channel2 #channel3 #mychannel #yourchannel"
set needinvitechans "#pwnt"

#Set this if you when the bot rejoins back through the need-invite command, should it should remove the
#invite-only mode (+i) set on the channel to -i.
#USAGE: [0/1] (1=OFF, 2=ON) - (1=DOES NOT REMOVE THE INVITE-ONLY MODE, 2=REMOVES THE INVITE-ONLY MODE)
#If set to '0' the bot will take no action against the +i mode set when it rejoins back. (This setting is disabled)
#If set to '1' the bot will remove the +i set by making it -i, when it rejoins back.
set invitetype "1"


#---------------------------------#
# SETUP NEED-LIMIT VARIABLES #
#---------------------------------#

#Set the type of channels on which you would like the 'NEED-LIMIT' script to work on.
#USAGE: [1/2] (1=USER DEFINED CHANNELS, 2=ALL CHANNELS) (You can enable only one, not both!)
#Use '1' for 'user defined channels'. (Will make the need-limit command work on channels only mentioned by the user)
#Use '2' for 'all the channels' the bot is on. (Will make the need-limit command work on all channels the bot is on)
set needlimittype "1"

#Set this only if you have enabled the previous setting to '1' (user defined channels). Set here the working
#user defined channels you want the 'need-limit' command to work on, if not then leave this setting empty/blank.
#USAGE: set needlimitchans "#channel1 #channel2 #channel3 #mychannel #yourchannel"
set needlimitchans "#pwnt"

#Set this if you want the bot when it rejoins back through the need-limit command, should it should remove the
#channel-limit mode (+l) or increase the channel limit to a user defined value.
#USAGE: [0/1/2] (1=OFF, 2=REMOVES THE LIMIT, 3=INCREASES THE LIMIT TO A USER DEFINED VALUE)
#If set to '0' the bot will take no action against the +l mode set when it rejoins back. (This setting is disabled)
#If set to '1' the bot will remove the +l set by making it -l, when it rejoins back.
#If set to '2' the bot will increase the current limit +l value set to a user defined value.
set limittype "1"

#Set this if you have chosen the previous option to '2' (to increase the channel limit). Set this to the limit
#you would like the bot to set after it rejoins the channel.
#USAGE: Use a numerical value which is greater 5-to-10 users from your original channel peak value.
set limitincrease "50"


#-------------------------------#
# SETUP NEED-KEY VARIABLES #
#-------------------------------#

#Set the type of channels on which you would like the 'NEED-KEY' script to work on.
#USAGE: [1/2] (1=USER DEFINED CHANNELS, 2=ALL CHANNELS) (You can enable only one, not both!)
#Use '1' for 'user defined channels'. (Will make the need-key command work on channels only mentioned by the user)
#Use '2' for 'all the channels' the bot is on. (Will make the need-key command work on all channels the bot is on)
set needkeytype "1"

#Set this only if you have enabled the previous setting to '1' (user defined channels). Set here the working
#user defined channels you want the 'need-key' command to work on, if not then leave this setting empty/blank.
#USAGE: set needkeychans "#channel1 #channel2 #channel3 #mychannel #yourchannel"
set needkeychans "#pwnt"

#Set this if you want the bot when it rejoins back through the need-key command, should it should remove the
#channel-key mode (+k) or set the channel key to a random or user-defined one.
#USAGE: [0/1/2] (1=OFF, 2=REMOVES THE KEY, 3=REPLACES THE CHANNEL KEY TO A RANDOM/USER-DEFINED ONE)
#If set to '0' the bot will take no action against the +k mode set when it rejoins back. (This setting is disabled)
#If set to '1' the bot will remove the +k set by making it -k, when it rejoins back.
#If set to '2' the bot will replace the current channel key (+k) to a random or user-defined value.
set keytype "1"

#Set this if you have chosen to replace the channel-key to a user-defined key. Set this to the new channel key
#which you would like. (If you want to use random keys, selected from a list of keys set this to "" as empty/blank)
#USAGE: Only use alphabets and numbers, no special characters.
set newkey ""

### This setting will only work if you have set the previous variable setting as "" empty/blank ###
#Set this if you have chosen to replace the channel-key to a random key, chosen from a list of speicifed keys.
#USAGE: Only use alphabets and numbers, no special characters. Set the channel keys in seperated lines each
#between quotation marks, making the whole list enclosed in braces, as shown.
set newkeys {
"yeahbaby"
"fearme"
"ohmygod"
"bornintheusa"
"iameleet"
}


#--------------------------------------#
# SETUP NEED FUNCTION DELAY TIMER #
#--------------------------------------#

#Set this if you have enabled to remove any -i, -l, -k modes or replace them. This setting will cause a
#delay after the eggdrop joins back in the channel so it will be able to perform the mode operations as
#requested. Set a delay in seconds after which the bot rejoins back it should perform these operations.
#USAGE: Use a range of '3 to 10' seconds.
set needdelay "5"


###############################################################################
### Don't edit anything else from this point onwards, even if you know tcl! ###
###############################################################################

[awyeah]

Don't use the auto reop script and need-op at the same time they will tend to cause problems. Switch of the need-op by setting it to #blabla a random named channel. Use these:

set needoptype "1"
set needopchans "#blabla"

Grr ...I forgot to add a switch to select certain features so all don't have to be always on, anyway what are future releases for, heh?!

[killer-instinct]

tottaly disabled the need script

[22:36] [LOADED] ChanServ Auto Reop Script v5.61.b by awyeah (awyeah@usa.net)
[22:36] *ENABLED* Auto Reop for |6gb|Bubba on: #pwnt


still get the same problem , no reopping

ps this is the auto reop script i am using

# $Id: autoreop.tcl, eggdrop-1.6.x 2004/5 awyeah@usa.net Exp $

# Begin - Deop Protection, ChanServ Auto Reop Script v5.61.b (autoreop.tcl)
# Script Version: 5.61.b
# Built Date: November 2003, Last Updated: 25th June 2004
# Copyright © 1999-2004 awyeah (awyeah@usa.net)
# TCL script was designed to use with eggdrop v1.5.x or higher

#########################################################################
# ChanServ Auto Reop Script v5.61.b #
# #
# #
# Author: awyeah 25th June 2004 #
# Email: awyeah@usa.net Build version 5.61.b #
# Copyright © 2004 awyeah All Rights Reserved http://www.awyeah.org/ #
#########################################################################
# #
# ####### #
# PURPOSE #
# ####### #
# #
# This script serves the purpose to auto-reop an eggdrop bot when it #
# is deoped by someone on a channel. (there are some condtions) #
# #
# Basically this script is written for networks, which run a channel #
# maintainence service called 'ChanServ', like DALnet. Hence this #
# script can be only used on networks having ChanServ. #
# #
# I've made this script because sometimes people deop my eggdrop bot on #
# channels, like suppose when they perform a mass deop in a channel, or #
# maybe the bot disconnects from the server like in a netsplit and does #
# not regain channel op status, or something of the kind. #
# #
#########################################################################
# #
# ########### #
# DESCRIPTION #
# ########### #
# #
# This script reops the bot on all channels, if it is deoped by #
# any user on any channel it is on. It can be requested to work on #
# specific, user defined channels and will not request auto reop from #
# chanserv on the channels not mentioned in its working channel list. #
# #
# This is a very effective script to keep your bot oped on all #
# channels or specific channels it has access on. However, if the bot #
# is deleted from the ChanServ access list then obviously as you might #
# suspect it will not be able to regain op status on that channel. #
# #
# This script has other functions and features other than simply to #
# reop the eggdrop bot when it is deoped. It has different punishment #
# levels, many exemptions features, functions such as logging the #
# people who deop the bot and etc. #
# #
#########################################################################
# #
# ######## #
# FEATURES #
# ######## #
# #
# 1. This script has *3* settings of channels to work on. #
# - It can work on user defined channels. #
# - It can work on all matching channels the bot is deoped on. #
# - It can work on all the channels the bot is monitoring. #
# #
# 2. This script will make the bot request chanserv network service for #
# regaining ops back on channels, when it is deoped. #
# #
# 3. This script has user defined exempt flag settings, so users in #
# bot file such as owners and masters would be exempted from this #
# script and would be able to deop the bot. It also has exemption #
# settings for seperate nicks, idents, user hosts, ip addresses etc. #
# #
# 4. This script has different punishment options for the user who #
# deoped the bot, such as deoping, kicking and banning the user etc. #
# #
# 5. There is a notification feature to the user who deoped the bot. #
# Notifications can be sent in the form of private messages and #
# private notices depending upon the owners choice. #
# #
# 6. Bot owners can log the data of the people who deop the bot through #
# the course of the day and store the info a text file which created #
# in the main eggdrop dir, which would include which channel the bot #
# was deoped on, the users host, address and his nick. #
# #
#########################################################################
# #
# ##### #
# USAGE #
# ##### #
# #
# - Please unzip zipped file autoreop.zip file and place the tcl file #
# autoreop.tcl file in your eggdrops */scripts* folder along with #
# your other tcl scripts. #
# #
# - Please add a link at the bottom of your eggdrop's .CONF file to #
# the path of your autoreop.tcl, it would be something like this: #
# #
# source scripts/autoreop.tcl #
# #
# - Save your bot's configuration file #
# #
# - *RESTART* your eggdrop bot and start enjoing the script! #
# #
#########################################################################
# #
# ####### #
# CONTACT #
# ####### #
# #
# - If you have any suggestions, comments, questions or if you want to #
# report bugs, please feel free to email me at: #
# #
# awyeah@usa.net / awyeah@awyeah.org #
# #
# #
# - You can contact me on MSN Messenger, on my ID: awyeah@awyeah.org #
# #
# #
# - You can also catch me on IRC (The DALnet Network) #
# #
# /server irc.dal.net:6667, Nick: awyeah #
# #
#########################################################################
# #
# ######## #
# VERSIONS #
# ######## #
# #
# #
# v5.61.b - Added a new type of channel activation option. The bot #
# (25/06/04) will only request for ops on channels it is deoped on by #
# this new function. #
# - Added new exemption options for exempting specific nicks, #
# user idents, ip addresses and user hosts. #
# - There were two similar ban types in the banmask selector #
# fixed those and replaced the similar one by a new one. #
# - Fixed some errors in the punishment procedure. #
# - Optimized most of the settings to give a faster output. #
# #
# v4.82.b - Added a switch for users to select channels for the script #
# (16/06/04) to work on. Users can activate the script on their own #
# defined channels or activate the script on all the #
# channels the bot is monitoring. #
# - Added punishment options for the user who deoped the bot. #
# The punishment range can be from minimum to maximum #
# depending upon the type of punishment selected. #
# - Modified the user notification options to select between #
# private messages or private notices. #
# - Added a choice to send user defined notifications #
# - Added a deop user log function. Users who deop the bot #
# will be logged into a text file in the bots main *eggdrop* #
# directory along with their userhost, channel and info. #
# - Added a small feature to choose whether the bot should try #
# to reop itself when it is deoped on a channel by ChanServ. #
# #
# v3.56.b - Removed the all channels support for the script. #
# (25/05/04) Added support for users to define their own channels. #
# Users can now activate the script on specific channels #
# the bot is opped on. The bot would only request ops from #
# ChanServ on those channels which are mentioned in its #
# channel list. #
# - Also added a notice command if the owner wishes the bot #
# to notice the nick who deoped the bot, with a msg #
# telling the user who deoped the bot not to deop it. #
# #
# v3.20.b - Initial release of script #
# (08/03/04) #
# #
# #
# Latest released verions of this script which are updated and modified #
# from time to time can be found on: #
# #
# http://www.egghelp.org/ - http://www.tclscript.com/ #
# #
#########################################################################
# #
# ####### #
# CREDITS #
# ####### #
# #
# - Thanks to all my friends who gave me the idea of creating this #
# script as it has proven to be very useful. #
# #
# I hope you really appreciate the work I've done! #
# #
# #
# ./awyeah #
# #
#########################################################################

##################################################
### Start editing variables from here onwards! ###
##################################################

#----------------------------------------#
# SETUP CHANNEL ACTIVATION OPTIONS #
#----------------------------------------#

#Set the type of channels (defined, all) you would like to enable for the bot.
#USAGE: [1/2/3] (1=USER DEFINED CHANS, 2=MATCHING CHANS 3=ALL CHANS) (You can enable only one, not both!)
#Use '1' for 'user defined channels'. (Will make the bot request for ops only on channels defined for it)
#Use '2' for 'all matching channels'. (Will make the bot request for ops on any channel it is deoped on)
#Use '3' for 'all the channels' the bot is on. (Will make the bot request for ops on all channels it is on)
set deoptype "1"

#Set this to the user defined channels if you have enabled deop protection for user defined
#channels, if not then leave this empty/blank. (Set the channels on which this script would work on)
#USAGE: set deopchans "#channel1 #channel2 #channel3 #mychannel #yourchannel"
set deopchans "#pwnt"


#--------------------------------------#
# SETUP NETWORK CHANSERV OPTIONS #
#--------------------------------------#

#Set your ChanServ service nick here. This is not a case-senstivie setting.
#USAGE: Set the nick of your networks channel service, for example 'ChanServ'.
#(If your network uses ChanServ and is not DALnet, set this to only 'ChanServ' then)
#(If your network is DALnet, then you do not need to edit this as, I have set this default for DALnet)
set chanservices "Chanserv"

### Recommended to keep this setting to '0' (OFF) if possible ###
#Set this is you want your bot to reop itself when it is deoped on a channel by ChanServ.
#Mostly sometimes people use chanserv to deop other people on channels, because they might have
#been just removed off the channel access lists. (I would recommend to *KEEP THIS SETTING OFF*)
#USAGE: [0/1] (0=WILL NOT REOP IF DEOPED BY CHANSERV, 1=WILL REOP IF DEOPED BY CHANSERV)
#If set to '0' the bot will *NOT* reop itself if it is deoped by chanserv
#If set to '1' the bot will reop itself if it is deoped by chanserv (can cause services/mode floods)
set noreop "0"


#---------------------------------#
# SETUP USER EXEMPT OPTIONS #
#---------------------------------#

### IMPORTANT NOTE ###
#For all of the exemption settings below please *DO NOT* use wildcards
#such as: (*, !, *!*, *@*, *!*@*, @*.host.com, *@127.0.0.* etc as they maybe risky)
#(If you do not have any ident, userhost, or ip to enter then please leave the field "")

### This is a compulsory setting ###
#Set the 'user flags' for bot owners, masters, ops and etc which will be exempted from this script and
#would be able to deop the bot, which after that the bot will not reop itself again using this script.
#(Try not to leave this field empty, atleast fill it with "n" to exempt the bot owner if possible)
#Example: n=owner, m=master, o=op, v=voice, f=friend, b=bot etc
#USAGE: "m", "n", "o", or "mnf", "bfv" etc
set deopexemptflags "mn|mn"

#Set this to the list of 'exempted nicks', which you would like the bot to ignore when checking for
#users who deoped the bot. (If you do not have any 'nick' to exempt then, leave this as "")
#USAGE: "nick1, bot3, user5, robot7"
set deopexemptnicks ""

#Set this to the list of exempted 'user idents' which you would like the bot to ignore when checking for
#users who deoped the bot. (If you do not have any 'user ident' to exempt then, leave this as "")
#(Whois example: awyeah is cooldude@loves.you.com ===> cooldude)
#USAGE: "cooldude, myident, user, script, sweet"
set deopexemptidents ""

#Set this to the list of 'exempted domains' (user ip addresses) which you would like the bot to ignore when
#when checking for users who deoped the bot. (If you do not have any 'ip addresses' to exempt then, leave this as "")
#(Whois example: awyeah is cooldude@adsl-154-462.cable.myisp.com ===> cable.myisp.com)
#USAGE: "cable.myisp.com, name.myuniversity.edu, mindspring.com, cpe.net.cable.rogers.com"
set deopexempthosts ""

#Set this to the list of 'user hosts' (user@host) which you would like the bot to ignore when checking for
#users who deoped the bot. (If you do not have any 'user@host' to exempt then, please leave this as "")
#USAGE: "rules@127.0.0.1, i@am.eleet.com, yeah@baby.yeah.net"
set deopexemptuserhosts ""


#-------------------------------------#
# SETUP USER PUNISHMENT OPTIONS #
#-------------------------------------#

#Set this if you want the bot to 'punish' the person who deoped your bot.
#USAGE: [0/1/2/3/4/5] (0=OFF, 1=DEOP, 2=KICK, 3=KICK/BAN, 4=STICKY KICK/BAN, 5=GLOBAL KICK/BAN)
#Use '0' if *DO NOT* want the bot to punish the user. (No punishment)
#Use '1' if you want the bot to 'deop' that user in the channel. (Minimal punishment)
#Use '2' if you want the bot to 'kick' that user from the channel. (Moderate punishment)
#Use '3' if you want the bot to 'kick and ban' that user from the channel. (Extreme punishment)
#Use '4' if you want the bot to 'kick ban' that user using a sticky ban from the bots ban list. (Maximum punishment)
#Use '5' if you want the bot to 'kick ban' (blacklist) that user using the bots global ban list. (Not recommended)
set deoppunish "0"

#Set this to the kick message if you have enabled to punish the user and would want to kick or
#or kick and ban the user from the channel. (This would be the kick message used to kick out the user)
set punishmsg ""

#Set this to the ban time if you have selected to punish the user by kicking and banning the user.
#Please set the ban time in minutes over here. (in minutes)
set punishunban "10"


#-----------------------------#
# SETUP TYPE OF BANMASK #
#-----------------------------#

#Set this to the banmask type if you have selected to punish the user by the kick and ban method.
#Types of banmasks
# 1 - *!*@some.host.com
# 2 - *!*@*.host.com
# 3 - *!*ident@some.domain.com
# 4 - *!*ident@*.host.com
# 5 - *!*ident*@*.host.com
# 6 - *!*ident*@some.host.com
# 7 - nick*!*@*.host.com
# 8 - *nick*!*@*.host.com
# 9 - nick*!*@some.host.com
# 10 - *nick*!*@some.host.com
# 11 - nick!ident@some.host.com
# 12 - nick!ident@*.host.com
# 13 - *nick*!*ident@some.host.com
# 14 - nick*!*ident*@some.host.com
# 15 - *nick*!*ident*@some.host.com
# 16 - nick!*ident*@some.host.com
# 17 - nick*!*ident@*.host.com
# 18 - nick*!*ident*@*.host.com
# 19 - *nick*!*ident@*.host.com
# 20 - *nick*!*ident*@*.host.com
set deopbanmask "1"


#---------------------------------------#
# SETUP USER NOTIFICATION OPTIONS #
#---------------------------------------#

#Set this if you want the bot to give a notification warning to the user who deoped it, saying back not to
#deop it in the future. (If that user may have deoped your bot, probobaly because of any bugs or errors detected
#in the bot, then that person should contact you 'the owner' of the bot)
#USAGE: [0/1] (0=OFF, 1=ON)
set deopnotify "1"

#Set your nick here, the owner of the bot. (This is used to notify the person who deoped your bot that, you
#are the owner of this bot and that person should contact you if he has encountered any problem with the bot)
#(Please do not leave this setting empty as it is compulsory. I recommend you fill this setting)
set botownernick "edited"

#Set this to the type of notification warning you would like the bot to notify the user with.
#USAGE: [1/2] (1=PRIVATE MESSAGE, 2=PRIVATE NOTICE)
#Use '1' if you want the bot to notify the user with a PRIVATE MESSAGE (/msg).
#Use '2' if you want the bot to notify the user with a PRIVATE NOTICE (/notice).
#(This will only work if you have enabled the user notification option)
set notifytype "2"

#Set the notice here which you wish the bot to send to the user who deoped it. (This will only work if you have
#enabled the deop notification switch and have not set this setting as blank/empty)
set noticeuser "Please *do not* deop me. For further assistance please contact *$botownernick* regarding any problems."


#-------------------------------#
# SETUP DEOP USER LOGGING #
#-------------------------------#

#Set this if you want to enable recording (nick, host, info and chan) for the people who deop
#the bot. (This will help you to check who deops your bot while you are offline)
#USAGE: [0/1] (0=OFF, 1=ON)
set deoplog "0"

#Set this to the file name which will be used to record and store the users nick, info and data in.
#(This file will be created in your main */eggdrop* dir, which has your other .conf, .user and .chan files)
set deopfile "deoplog.dat"


###############################################################################
### Don't edit anything else from this point onwards, even if you know tcl! ###
###############################################################################

[awyeah]

Eeeks you don't need to paste everything over here, I have it.

I don't know what type of error you are getting because this script has had many downloads as I recently checked now and I haven't gotten a bug report regarding this type of malfunction.

What other scripts are you running? Do you have alot loaded?
Does: /msg chanserv op #channel mynick work?
or do you have todo something like: /msg chanserv@services.mynetwork.net op #channel mynick

[awyeah]

Eeeks you don't need to paste everything over here, I have it.

I don't know what type of error you are getting because this script has had many downloads as I recently checked now and I haven't gotten a bug report regarding this type of malfunction.

What other scripts are you running? Do you have alot loaded?
Does: /msg chanserv op #channel mynick work?
or do you have todo something like: /msg chanserv@services.mynetwork.net op #channel mynick

Also are you getting any tcl error in a the format like:
[Tcl:error my_proc]

If so, show me the results of (type this in DCC)
.tcl set errorInfo

[killer-instinct]

no tcl errors at all

and the syntax for enterthegame is
/msg chanserv opme #channel

[awyeah]

Then replace all the lines:

Code: Select all

putserv "PRIVMSG $chanservices :OP $chan $botnick"

with:

Code: Select all

putserv "PRIVMSG $chanservices :OPME $chan"

and the all the lines:

Code: Select all

putserv "PRIVMSG $chanservices :OP $channel $botnick"

with:

Code: Select all

putserv "PRIVMSG $chanservices :OPME $channel"

Basically, if you notice we are just replacing 'OP' with 'OPME' and eliminating the variable $botnick.

[killer-instinct]

still wont seem to work

[awyeah]

See if this works, then the script should as well:

Code: Select all

Usage: !opbot
#Use this on the channel to op the bot on.

Code: Select all

bind pub n !opbot op:bot

proc op:bot {nick uhost hand chan text} {
  putquick "PRIVMSG ChanServ :OPME $chan" -next
  return 0
}

[killer-instinct]

where are you saying to put this code , in the reop script , or a whole new tcl?


i put it in the autorep tcl and got this


Tcl error in file 'eggdrop.conf':
invalid command name "Usage:"
while executing
"Usage: !opbot"
(file "scripts/autoreop.tcl" line 6)
invoked from within
"source scripts/autoreop.tcl"
(file "eggdrop.conf" line 1348)
* CONFIG FILE NOT LOADED (NOT FOUND, OR ERROR)

[awyeah]

This is just a code to check if the bot is opped by chanserv. Put it anywhere in an empty line in any tcl file and load it in. Then seeing the usage, use the command and tell me if it works or not.

[killer-instinct]

ok , no it did not op him. but he does have auto ops

[15:56] * |6gb|Bubba (~|6gb|Bubb@GunBusters.on.EnterTheGame.Com) has joined #pwnt
[15:56] * ChanServ sets mode: +o |6gb|Bubba

[killer-instinct]

been a while , bump

[awyeah]

Really have no idea why it isn't working with you. I've got alot of feedback from people saying it works fine and they want new options added.

Try something simple as:

Code: Select all

bind mode - "-o" test:autoreop

proc test:autoreop {nick uhost hand chan mode target} {
  if {([string equal "-o" $mode]) && ([isbotnick $target]) && (![isbotnick $nick])} {
   putquick "PRIVMSG ChanServ :OPME $chan" -next
   return 0
   }
}

#Also check in DCC with the bot, what response it gets from ChanServ when this script executes so you can know. Try using putlogs as well.

[killer-instinct]

THis one is not working either. i am posotive the bot is on auto ops. From the dcc menu nothing comes un when he is deoped that the last one you said to try. when i am in the dcc with him i can .msg Chanserv opme #pwnt and it will op him , if this helps , also when he joins the channel chanserv ops him


Edit ok the code for the op bot command is now working , when i type !opbot , chanserv ops him.

Using the modifyed version of your script that you told me to change for my network

when i have a user deop him this is what happens in the dcc chat

[00:51] <{GB}Bubba`> [00:49] #pwnt: mode change '-o {GB}Bubba`' by {GB}K-I!~foo@GunBusters.on.EnterTheGame.Com
[00:51] <{GB}Bubba`> [00:49] Punishing {GB}K-I (deopped {GB}Bubba` on #pwnt)
[00:51] <{GB}Bubba`> [00:49] Now deopping {GB}K-I[~foo@GunBusters.on.EnterTheGame.Com] ((17 Sep) deopped {GB}Bubba` on #pwnt)

but he never gets his ops back , so the deop never happens

i have also noticed that it is set to notice the user that deops him and tell him not to , and that is also not working.