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.
Just 1 Eggdrop on Multiple networks!!
Just 1 Eggdrop on Multiple networks!!
It´s possible? help me!
. 
You would have to program an Eggdrop using Tcl for the socket bot to act as an Eggdrop, so that's a really bad ideaTosser^^ wrote:Well, it is actually possible.
With enough tcl and irc protocal knowhow,
you could code a tcl script using sockets.
Either pure tcl or just an normal eggdrop tcl script.
You just need to know the USER, PRIVMSG, NOTICE irc protocals and/or raws.
The point is, you're trying to tweak and patch eggdrop into being something it was not intended to be. Sure you could write a different, or even complementary, server module to permit additional server connections.
You would still have to go through each and every single sourcefile and make sure they can differentiate between the different server connections wherever neccesary.
You could also write some fancy tcl-package that handles a separate server connection. However, this would simply be an irc-client written in tcl, running in eggdrop's tcl environment. Integrating with eggdrop's native functions for userlist, channel maintenance (opping, kicking, etc) would be very messy...
In most cases, it's really easier to just start from scratch. This usually permits far better performance, as you can design the software to support multiple servers from scratch.
@sKy:
Wether writing it as an eggdrop module, or a tcl module really does'nt make much difference. You'd still have the daunting task of modifying vast parts of the source to properly handle multiple server connections.
You would still have to go through each and every single sourcefile and make sure they can differentiate between the different server connections wherever neccesary.
You could also write some fancy tcl-package that handles a separate server connection. However, this would simply be an irc-client written in tcl, running in eggdrop's tcl environment. Integrating with eggdrop's native functions for userlist, channel maintenance (opping, kicking, etc) would be very messy...
In most cases, it's really easier to just start from scratch. This usually permits far better performance, as you can design the software to support multiple servers from scratch.
@sKy:
Wether writing it as an eggdrop module, or a tcl module really does'nt make much difference. You'd still have the daunting task of modifying vast parts of the source to properly handle multiple server connections.
NML_375