This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
commands from my bot to services
commands from my bot to services
Is it possible to send commands to the services like operserv that appear to come from the bot? I am trying to get my bot to become an IRCop. Also how do I make my bot connect as a bot and not as a client.
Re: commands from my bot to services
yep, see this thread. I don't really understand what you mean by making your bot connect to IRC as a bot and not as a client. You mean you don't have a shell account? All connections to the IRC are pretty much the same... I don't understand this question.Zippy[D] wrote:Is it possible to send commands to the services like operserv that appear to come from the bot? I am trying to get my bot to become an IRCop.
In addition to YooHoo's response, there are three different kinds of connection classes; being "server", "client", and "service" (sometimes considered a subclass of "client").
Server: is obviously an irc-server to which other servers, clients and services may connect, and builds the framework of the irc network. Eggdrop cannot act as a server without serious patching or scripting.
Client: pretty much any participant in the irc chatter. Can join channels, can send and messages and notices. May gain elevated privileges such as channel operator and/or server operator (IrcOp). This is how eggdrop connects to the irc network.
Service: Somewhat of a hybrid in-between client and server, allowed access to more sensitive information, but with limited access to communications. Does not join channels or receive normal messages or notices. Recieves instructions using the SQUERY command and responds using NOTICE's. Does not relay connections like a server. Most common use would be to provide services for statistics, NoteServ/MemoServ, and such. Services generally cannot have elevated privileges such as IrcOp privileges. Eggdrop cannot register as a service without some patching.
Keep in mind that services such as NickServ on DalNet technically is not a service such as described above, but rather an integrated part of the server-software.
Server: is obviously an irc-server to which other servers, clients and services may connect, and builds the framework of the irc network. Eggdrop cannot act as a server without serious patching or scripting.
Client: pretty much any participant in the irc chatter. Can join channels, can send and messages and notices. May gain elevated privileges such as channel operator and/or server operator (IrcOp). This is how eggdrop connects to the irc network.
Service: Somewhat of a hybrid in-between client and server, allowed access to more sensitive information, but with limited access to communications. Does not join channels or receive normal messages or notices. Recieves instructions using the SQUERY command and responds using NOTICE's. Does not relay connections like a server. Most common use would be to provide services for statistics, NoteServ/MemoServ, and such. Services generally cannot have elevated privileges such as IrcOp privileges. Eggdrop cannot register as a service without some patching.
Keep in mind that services such as NickServ on DalNet technically is not a service such as described above, but rather an integrated part of the server-software.
NML_375