I have gone through the add operators process, and set them up to autoop as the people are going through a membership system(I know, still a big no no) Well, when they come in, The bot recognizes them and ops them, but once they are op'ed they cannot do anything because they "aren't the channel operator" I was the one who originally set up the accounts and I can do everything, but they cannot. Has anyone run into this before or know what could be happening? Thanks in advance. Oh, and the flags have been set to +an, so it isn't that they don't have permission to do things. They can "talk" to the bot and he will respond to them(when they type help), but they cannot kick, ban, give or take op and voice.
It is not 100% on why it's done, but can understand when explained.
The +a flag is to signify an auto-op. In other words, the user is auto set +o oin the channel. This is all it does, nothing more, other than generating the mode change on the channel.
The +o flag on the other hand, is the real workhorse. This is used to allow all the command to be used.
No they have the o flag already. The flags they have are "ajmnoptx". The bot recognizes them when they enter and they are changed from a normal user to a user with the "@" in front of them (this means they are a channel op right?). They can talk to the bot and he will respond to them, but they cannot do any of the actions that operators should be allowed to do (kick, ban, etc.)
In response to ppslim: They are gettting the error when they try to do any of the op commands (give voice, kick, ban, give op status, etc). These are being done through the irc interface. The error message is coming from the irc side that they are not channel operators even though eggdrop has supposedly made them one (gives the "@"). We are running 1.6.12 on a closed network, so we have it setup as "other" right now, but I have also set it up as an irc network (option "1") and it made no difference.
The answer for where they type the command (you stated "irc interface"), still partialy evades me.
When you say IRC interface, do you mean IRC commands, being sent tot he server, or are you talking about using a DCC chat with the bot, and usign ".op" commands?
If it's the first method, then I have to tell you it's a IRC problem, and nothing to do with eggdrop.
This is most likely caused by a restricted connection to the IRC servers (a lot of networks now do this), or by a desynch in the IRC servers.
If the bot has set some1 +o, other users clients are seeing this happen and they are using commands direct to the IRC server, the it's time to contact the server admins.