Let's put it this way Kev, you know I run botlending, and if there would be any feature that would make it possible to be able to use the same bot for more then current (e.g. perhaps in the way I proposed earlier many times) I would do it, in fact I'm already working on it, just need to implement the usermode (so it gets broadcasted around the servers so they also know a certain client is a bot)
The current way is through mbuna's botaddon, but after I played a bit with remote privs (yo math, getting anywhere with the tokenized thingie we discussed ? :) ), making some changes in mod.cservice (ok, I will try to make it without adding a command, but it will make certain things a bitch, for example making it able to retrieve the key (scripts would prefer it if the channel name is accompanied with the mode, in case they need to handle a lot it makes parsing for the bot easier). Since I always favoured botlending and such I think this will be something even I could work on, so you folks focus on the real neccessary stuff, and I'll work on that.. first I'll finish it for .11, later then porting it to .12, even if Kev announced a feature stop for .11, there are others that still would like to have it for there .11. Oh wennie, knowing unet a bit tells me only one channel will benefit from this anywayz, and I think we all know who that is. /me blinks at #userservice Have fun charging them 5 bucks@bot (I think they got like 20 online, not sure), that should get you some beers for the next football game :) By the way, bots should NEVER have +k, for the rest they could have some of there benefits, thats why I chose no flood/target/chan limits + modified whois as only benefits within the ircu code and some restrictions/benefits within mod.cservice, if it would get applied like that -> why run 20 bots from the same shell ? This could heavily reduce the amount of bots, resources etc.on BOTH sides, not only on the irc network but also on the shells where the bots are present. Regarding CPRIVMSG vs PRIVMSG -> I already took those into account in my tcl script by reading the RPL_ISUPPORT (RAW 005) on connect, if the network supports CNOTICE/CPRIVMSG the bot will utilize it whenever possible by tracking eventual targets in channels, if the bot is in a channel together with the target to message/notice and it is opped/voiced, it will use it. This cutted down the 439's the bots received a lot (wich was actually the reason why I coded that support) greetz, OUTsider
