IPv6 patch for eggdrop 1.6.13, after you extract original eggdrop enter that directory and do:
Quote:
then compile your bot.

Original author: Sascha Bielski

Very nice tool that tells which programs are started on boot.
Useful for removing viruses/trojans/spyware etc.

eggdrop1.6.13+multilevel_sharing by TaKeDa <takeda (at) takeda (dot) tk>
updated for eggdrop1.6.15 by Adam Golebiowski <adamg (at) pld (dot) org (dot) pl>

- This patch adds additional settings:

# When sharing user lists, which channel flags changes from other bots
# should be ignored?
#set private-chanflags "mn"

(This setting works same as private-globals, except that is for channel flags)

# When you have multilevel botnet, this option permits hub, to make changes,
# even when private-global, private-chanflags and/or private-user are set.
# NOTE: this option doesn't permit hub to force flags filtered by
# private-globals
#set permit-hub 1


- Creates additional flag:
s (protected) is working similar like u flag, but changes can be made only
from bot that is aggressively sharing with us (Hub).
User cannot be changed by bot that is connected below this bot.
(This flag can be useful in multilevel sharing)

(When you don't use setting private-user, it is highly recommended, to set this flag for
bots, and bot masters, to make your botnet more secure)

NOTE: this flag was changed since 1.6.10, because 1.6.13 has halfop support and use
+r flag for auto de-halfop, if you're upgrading bot, you need to change flag in
userlist :/ to do it, you can write on DCC:

.tcl foreach tmp [userlist +r] {chattr $tmp -r+s}


- Provides additional command:
noshare <command> [<arg1> <arg2> ...]
Executes command with setting noshare = 1 in code,
that means, if you i.e. do chattr using this command,
bot will make changes on his userlist, but won't send changes
to other bots. This is useful in some situations.
returns: whatever is returned by <command>


How to apply:

Step 1: get the patch file (duh!) and uncompress it
Step 2: in your eggdrop1.6.15 dir, type:

Quote:

when you do this, you should see something like this happening

Quote:

this is good

Step 3: type "make" to recompile your bot
Step 4: type "make install" to install your bot like you did lasttime
Step 5: restart your bot

NOTE: Actually you only need to patch Hubs and Sub Hubs, but is recommended to patch all bots,
to get full advantage of this patch.