AllProtection won't consider 3 consecutive (not equal) lines as repeats. As for the time problem, it can be caused due to changes to date and time on your bot - restart your bot and it should be fixed.
Sir_Fz wrote:AllProtection won't consider 3 consecutive (not equal) lines as repeats. As for the time problem, it can be caused due to changes to date and time on your bot - restart your bot and it should be fixed.
That particular user was using eggrop 1.6.17 and after chatting to them on IRC the problem seems to have been fixed [upgraded to 1.6.18].
A suggestion is to have information included specifying that the beta script requires eggdrop 1.6.18 and/or a version check via the script itself.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
You're right, I don't know why I forgot to mention that this version works best with eggdrop1.6.18. But the problem that Zircon faced wasn't due to eggdrop's version, the command is the same on both versions; it was probably a problem from the box as I mentioned before.
Sir_Fz wrote:You're right, I don't know why I forgot to mention that this version works best with eggdrop1.6.18. But the problem that Zircon faced wasn't due to eggdrop's version, the command is the same on both versions; it was probably a problem from the box as I mentioned before.
I should mention that Zircon is a French speaker and has a difficult time understanding English correctly.
When they return (on IRC) your post will be translated for him.
PS: Am glad that you agree about the version check.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
Alright, I've been working on the script and did a few changes:
Added the ability to add/rem drone exempts via the .ap:add/rem DCC commands.
Fixed an unknown exploit caused by the string2list proc, replaced it with another.
Added 2 extra ban types *!user@* and nick!*@*.
Now you can exempt users from being banned for revolving door if they have specific part messages (set by you for exempting). This is usually used on networks where a user quits with a certain message when registered.
If you have any bug reports or suggestions not mentioned in the above list, it's time for you to speak for I won't be releasing any new version soon.
PS: The modified version has not been released yet, it's loaded on my bot for now.
Is it possible to make it multi bot, so it can interact with other bots on the same botnet, so if one bot is missing another takes over ??
Im thinking a bit like this:
bot1 normaly controls everything, but if bot1 for some reason is missing bot2 automaticly takes over?
Or is that something that shouldt be handled another way ??
This can be implemented, but should take more time than the other options. I'll see what can be done, probably will implement it thanx for your suggestion.