Code: Select all
*** Joins: Bot1 (~Bot1@Bot2.users.undernet.org) - Clones from *!*@Bot2.users.undernet.org (Bot1 Bot2 [2])
Code: Select all
[10:03] No longer ignoring *!*@Bot1.users.undernet.org (expired)
Code: Select all
[10:03] No longer ignoring *!*@Bot1.users.undernet.org (expired)
[/quote]nml375 wrote:Simply create a second copy of the initial config, and edit it accordingly.
1. I'd suggest you double check which files are loaded on each bot. Seems to me they're actually using the same copy of mc.irc_services.tcl, or the two copies holds the exact same information
2. Only activate the trigger in one bot. If you've got both bots linked in a botnet, it may be possible to rewrite the script to try and sync responses over the botnet. I would not consider this a trivial rewrite however.
This simply means that Bot2 stopped ignoring bot1. Most likely, it thought bot1 flooded earlier, and placed it on ignore...Code: Select all
[10:03] No longer ignoring *!*@Bot1.users.undernet.org (expired)
On a side note, with respect to your topic, I do hope you are using two separate user files for both bots?
NO, the bot will not be killed don't worry, I'm not on Undernet for 2 days..Moonster wrote:If your using two bots from one IP address with two Undernet Usernames they will both get killed (the Usernames) if someone from usernames does their job and scans
Only supposed to use one Username per ident@iprange as far as I know.
Yup, unless someone used the .+ignore command. But most likely, it was ignored due to flooding.eXtremer wrote:I understand that the Bot2 stopped ignoring Bot1, bot why it ignored it at all ? was flooded or what ?
I would strongly recommend not using the same user and channels file with both bots. If you wish to share user settings, link the two bots and set up sharing properly instead.eXtremer wrote:Once again I say, both bots use their own *.conf file, but have the same chan and user file.
No one has acc to partyline except me, so the .+ignore was not used, interesting why and how the Bot1 flooded Bot2...nml375 wrote:Yup, unless someone used the .+ignore command. But most likely, it was ignored due to flooding.eXtremer wrote:I understand that the Bot2 stopped ignoring Bot1, bot why it ignored it at all ? was flooded or what ?
I really don't want to mess with linking the Bots, It will give me headaches, I saw once two Bots linked that at almost every command gave me the "Sorry busy, transfering files" and the Owner of the bots just gave up & unlinked them. But why to link them ? they work perfectly as it is..nml375 wrote:I would strongly recommend not using the same user and channels file with both bots. If you wish to share user settings, link the two bots and set up sharing properly instead.eXtremer wrote:Once again I say, both bots use their own *.conf file, but have the same chan and user file.
I'm really not blind I already looked in the bots .conf files several times, and they use different mc.irc_services.tcl script, maybe it is because of the cache or the user.file, I really don't know..nml375 wrote:As for your issue with bot2 using bot1's login-credentials with X, either you did something wrong when editing the different scripts, or both config files load the same script.
Could be that weather script flood you mentioned earlier?eXtremer wrote:No one has acc to partyline except me, so the .+ignore was not used, interesting why and how the Bot1 flooded Bot2...nml375 wrote:Yup, unless someone used the .+ignore command. But most likely, it was ignored due to flooding.eXtremer wrote:I understand that the Bot2 stopped ignoring Bot1, bot why it ignored it at all ? was flooded or what ?
The problem is, that your two bots are having a "race condition" as to who gets to write to the userfile. This could lead to some very odd results whenever the data stored in the userfile is altered. That would include when bans, ignores, etc are placed and/or removed.eXtremer wrote:I really don't want to mess with linking the Bots, It will give me headaches, I saw once two Bots linked that at almost every command gave me the "Sorry busy, transfering files" and the Owner of the bots just gave up & unlinked them. But why to link them ? they work perfectly as it is..nml375 wrote:I would strongly recommend not using the same user and channels file with both bots. If you wish to share user settings, link the two bots and set up sharing properly instead.eXtremer wrote:Once again I say, both bots use their own *.conf file, but have the same chan and user file.
eXtremer wrote:I'm really not blind I already looked in the bots .conf files several times, and they use different mc.irc_services.tcl script, maybe it is because of the cache or the user.file, I really don't know..nml375 wrote:As for your issue with bot2 using bot1's login-credentials with X, either you did something wrong when editing the different scripts, or both config files load the same script.
NO, I use many scripts, I just said weather script as example...nml375 wrote:Could be that weather script flood you mentioned earlier?eXtremer wrote:No one has acc to partyline except me, so the .+ignore was not used, interesting why and how the Bot1 flooded Bot2...nml375 wrote: Yup, unless someone used the .+ignore command. But most likely, it was ignored due to flooding.
eXtremer wrote:I really don't want to mess with linking the Bots, It will give me headaches, I saw once two Bots linked that at almost every command gave me the "Sorry busy, transfering files" and the Owner of the bots just gave up & unlinked them. But why to link them ? they work perfectly as it is..nml375 wrote:I would strongly recommend not using the same user and channels file with both bots. If you wish to share user settings, link the two bots and set up sharing properly instead.eXtremer wrote:Once again I say, both bots use their own *.conf file, but have the same chan and user file.
Noop, I don't think I need to link...maybe later when I'll not be lazynml375 wrote:The problem is, that your two bots are having a "race condition" as to who gets to write to the userfile. This could lead to some very odd results whenever the data stored in the userfile is altered. That would include when bans, ignores, etc are placed and/or removed.
As for those issues you are describing with linking bots, personally, I've never had such restrictive issues. Actually, I can't even find such a message within eggdrop's source or language files.
Getting flags and bot records correct the first time may be a slight hazzle, but once that's done you'll never have any issues with syncing users in both bots.
I already looked, a few seconds ago I logged on my server and checked again...anyway it's not a big problem, I'll lived as it is.eXtremer wrote:I'm really not blind I already looked in the bots .conf files several times, and they use different mc.irc_services.tcl script, maybe it is because of the cache or the user.file, I really don't know..nml375 wrote:As for your issue with bot2 using bot1's login-credentials with X, either you did something wrong when editing the different scripts, or both config files load the same script.Look again, look more throughout, look yet again, go get a friend to have a good look... Not to be rude, but you've screwed up somewhere in there. They use different config files, the different configs load different mc.irc_service.tcl copies, but are the different copies setup properly?
- There is no script cache...
- There is no cache stored on disk whatsoever...
- Scripts must not access the userfile directly. They may only use commands to add, alter, and remove user records, bans, ignores, etc.
- mc.irc_services.tcl does not store any data in any user record or other data entity present in the userfile.