that's it folks, I'm done with xchannel; it has everything I deemed necessary for most people, and it should make all other protection scripts obsolete j/k, time will show, but I think I achieved my objective - highly-optimized and versatile code with 100% chanset-based configuration that should appeal to the majority of bot owners
there will be no next version unless people report bugs
the last is version 3.2, I've added drone detection (based on improved spambuster heuristics) and done some final [punish] changes
connection, sharing, dcc problems? click <here>
before asking for scripting help, read <this>
use
that happens because on (re)start eggdrop actually loads chanfile after loading its config (and any scripts sourced in it), so at that point xchannel doesn't know about any channels
I'll find a way around this
connection, sharing, dcc problems? click <here>
before asking for scripting help, read <this>
use
Some settings of the 'User defined channel strings' return to default after a restart. I can succesfully set every setting before ' x:bad:punish'
all settings that come after that return to default when bot's restarted.
These are de ones that return to default on my bot :
CooLB0Y wrote:x:drone:score (n), i didnt get the score, N and what should it be there? can i have an example for it please?
when you enable the drone scanner (.chanset #channel +x:drone), the script will be analyzing every nick!user on join and assign a score to it; that score is proportional to the degree of randomness of that nick & user; normally, people would have nicks that yield a score less than the threshold x:drone:score (by default 30), and (lame) drones with randomly generated nicks will yield a score above the threshold
you can experiment with the score by invoking the proc directly:
Some settings of the 'User defined channel strings' return to default after a restart. I can succesfully set every setting before ' x:bad:punish'
all settings that come after that return to default when bot's restarted.
These are de ones that return to default on my bot :
this is an eggdrop bug, I'll report it to eggheads
it is caused by length limitations in processing of channel options read from chanfile - xchannel adds plenty of those and eventually some are ignored on loading chanfile because of limited buffer size
I hope they'll fix that in 1.6.18, but for the time being you can fix it yourself just as I did, by editing src/mod/channels.mod/tclchan.c and substituting all occurances of the number 2048 with 4096, also 2047 with 4095 (these are in one function only, tcl_channel_add()); don't forget to recompile, reinstall & restart the bot after you are done with that
connection, sharing, dcc problems? click <here>
before asking for scripting help, read <this>
use
this message occurs because you either running eggdrop with englishnot as default language or you obviously added the source line before the loadmodule of channels.
When running bot with German as primary language:
[19:18:21] tcl: evaluate (.tcl): loadmodule channels
Tcl: Bereits geladen.
Edit: added missing "not" ^^
Last edited by De Kus on Mon Sep 26, 2005 3:36 am, edited 2 times in total.
demond wrote:umm heh, I haven't thought about that
blame it all on eggheads who chose to return language-dependant string as status indicator from a proc
Hmm, i haven't found a TCL command to access the language file. Maybe that would be worth a feature request for the bugtracker ^-^?
I mean you could create your own language files for your script (packs) . The benefit would be, you could even use the capility to use a channel specific language and not only a global one.