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.
Rely TCL
Well, first off.. I don't have a clue what you mean by "making the server/network bigger by already is"
But a relay script which makes 2 eggdrops transfer data/chat/what's up from one channel to the other on the other network, and vice-versa, you'll find plenty in the egghelp tcl scripts archive
But a relay script which makes 2 eggdrops transfer data/chat/what's up from one channel to the other on the other network, and vice-versa, you'll find plenty in the egghelp tcl scripts archive
Dormant egghead.
Re: Rely TCL
I need an eggdrop TCL that transfers users from one IRC network to another. It's some kind of rely script. IT'S NOT SOME KIND OF INVITE TCL!!!
For example:
I join my eggdrop on this server - irc.server1.just.example.com #example and the eggdrop (EXAMPLE_EGG) is joining the users from irc.server1.just.example.com #example to irc.server2.just.example.org #example, but ther arn't actually connecting through irc.server2.just.example.org actually.
You've got it didn't you?
For example:
I join my eggdrop on this server - irc.server1.just.example.com #example and the eggdrop (EXAMPLE_EGG) is joining the users from irc.server1.just.example.com #example to irc.server2.just.example.org #example, but ther arn't actually connecting through irc.server2.just.example.org actually.
You've got it didn't you?
he didnt say anything about a relay script. what yourname is referencing is imo what you are looking for. have you tried searching the archive (http://www.egghelp.org/tcl.htm). i am sure a simple search for "relay" will get you what you want.
dvV
dvV
if you want something that will relay what is said, who joins/parts, kicks/bans, on a channel to another channel both being on two dif networks than these scripts are what you want, if not please try respecifing:
http://www.egghelp.org/tclhtml/1256-0-1-relay.htm
dvV
http://www.egghelp.org/tclhtml/1256-0-1-relay.htm
dvV
What you are talking about, is not the job for eggdrop.
UserA joins ChannelA on ServerA.
BotB, makes a fake connection to ServerB, and makes that fake conection join ChannelB
Sofor each users that joins a channel, the bot must start a new connection, and manage it.
This has four potential flaws.
1: Bandwidth: For each person that joins, you add a tonn of traffic
2: Speed: For each person that joins, you add another set of processing to do.
3: Clone KILLS: Each fake connection made, will use the hostname of the bot. Most networks limit the number of clones possible, thus you run out pretty quick.
4: T&C and AUP's: Most shell providers do not allow more than one outgoing IRC connection per process.
UserA joins ChannelA on ServerA.
BotB, makes a fake connection to ServerB, and makes that fake conection join ChannelB
Sofor each users that joins a channel, the bot must start a new connection, and manage it.
This has four potential flaws.
1: Bandwidth: For each person that joins, you add a tonn of traffic
2: Speed: For each person that joins, you add another set of processing to do.
3: Clone KILLS: Each fake connection made, will use the hostname of the bot. Most networks limit the number of clones possible, thus you run out pretty quick.
4: T&C and AUP's: Most shell providers do not allow more than one outgoing IRC connection per process.
You will find what you have said is true with most shell providers.
Have you looked in the T&C's and/or the AUP's. You will likely find that while it's not a restriction, but there right to terminate and/or suspend your account without notice, for overuse of memory, CPU, bandwidth and so on.
Most providers, while not specifying specific limits on these, will state that programs like energymech and/or, only one connection to a IRC server per process.
I strongly sugest reading these documents.
Most people seem to think they can do what they wish with a shell account.
As for point 3 of my post. Regardless of what your shell provider gives you, it will never solve this. Killing clones is part of the IRC server, not the limitations of your shell.
As for the script, I would seriously sugest learning Tcl yourself, if you so wish to use Tcl. However, due to it's slowness, it's not suited to what you want.
It would be far better to learn C, and code your own system from scratch.
It is very unlikely you will find people willing to code you this, due to the fact it can't be done in under 100 lines of code.
You may want to look into the option of linking the IRC servers together. It's far more sensible.
Have you looked in the T&C's and/or the AUP's. You will likely find that while it's not a restriction, but there right to terminate and/or suspend your account without notice, for overuse of memory, CPU, bandwidth and so on.
Most providers, while not specifying specific limits on these, will state that programs like energymech and/or, only one connection to a IRC server per process.
I strongly sugest reading these documents.
Most people seem to think they can do what they wish with a shell account.
As for point 3 of my post. Regardless of what your shell provider gives you, it will never solve this. Killing clones is part of the IRC server, not the limitations of your shell.
As for the script, I would seriously sugest learning Tcl yourself, if you so wish to use Tcl. However, due to it's slowness, it's not suited to what you want.
It would be far better to learn C, and code your own system from scratch.
It is very unlikely you will find people willing to code you this, due to the fact it can't be done in under 100 lines of code.
You may want to look into the option of linking the IRC servers together. It's far more sensible.