egghelp.org community

tandilboy · Voice Joined: 01 Apr 2006 Posts: 2

It´s possible? help me!

deadite66 · Posted: Sat Apr 01, 2006 6:54 pm Post subject:

energymech appears to be the way to go for multiserver
_________________
<- tcl newb

minted · Halfop Joined: 20 Jul 2005 Posts: 64

its not possible, no
the eggdrop developers say they wont make it possible either
shell admins wouldnt like it very much

ladynikon · Voice Joined: 08 Sep 2007 Posts: 5

wow.. now i feel better. I been trying to get something like this working all day. I guess I will have to deal with this fact...

sadly I am the shell admin. So it kinda sucks that I can't have one bot on more than one network Sad

.

_________________
Have fun storming the castle!

r0t3n · Owner Joined: 31 May 2005 Posts: 507 Location: UK

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.
_________________
r0t3n @ #r0t3n @ Quakenet

Sir_Fz · Posted: Mon Sep 10, 2007 7:20 pm Post subject:

sKy · Op Joined: 14 Apr 2005 Posts: 194 Location: Germany

Bad? Really? I don`t think so. Because of speed or what? To connect to a server and to do some things don`t need so much. It would just be a lot of coding work.

You can also use a trick way to write in C and look here.
_________________
socketapi | Code less, create more.

nml375 · Revered One Joined: 04 Aug 2006 Posts: 2857

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.
_________________
NML_375, idling at #eggdrop@IrcNET