Every bot that wants to auto-connect to another bot has the "a" bot flag in it's record for the other bot, so it knows to attempt to connect to the other bot automatically. For example, fubaria keeps a record in it's user list that fewb is another bot, and the "a" bot flag is set in that record. That way when the bots are both in the channel, fubaria (should) attempt to link up to fewb if they get disconnected.
=fewb= [09:23:39] #frank#
bottree
=fewb= fewb
=fewb= `--fubaria
=fewb= `--Fubari
=fewb= `--xXfoobXx
=fewb= Average hops: 2.0, total bots: 4
You can initiate a dcc chat session to any of the channel bots. This will put you into the (sort of) private party line. conversations on the bot-net perty line have a slightly smaller chance of being recorded by feds, narcs, nosy operators, etc.
The bots use a combination of your "ident", your hostname, and your domain to recognize you. When you change any of this information, you will probably need to update your record in the bot. If you update your record on the "main" eggdrop, the change will (eventually) propagate to the other bots.
For example, the bot might have a record of you like so:
lamer *!~ident@coolhostname.kewl-ISP.com
If you join the channel using a different shell account on your Linux box, the "ident" part will not match. If you join the channel from a host on your network other than "coolhostname" then the hostname will not match. If you change your ISP, then obviously the TLDN will not match.
Simply use the ident command to let the bot know who you are. Note that this will add your current information to your user record on the bot so you might want to think twice if you are logging in temporarily from another account.
| nick | host | port | link to | shell owner | shell name |
| fewb | 99-89-223-91.lightspeed.cicril.sbcglobal.com | 6067 | frank | fubaria | |
| xXfoobXx | ganondorf.loclhst.com | 6057 | Dan | nilknarf | |
| fubaria | cbgbiotech.com | 3335 | Brad | ||
| fubari | noc3.cbgbiotech.com | 3334 | Brad | ||