egghelp.org community

[nml375]

Then you'll have to live with 9char handles. There should be no problem increasing nick-len however.
_________________
NML_375, idling at #eggdrop@IrcNET

[symbian001]

[BLaCkShaDoW]

your welcome
_________________
BLaCkShaDoW Production @ WwW.TclScripts.Net

[speechles]

[BLaCkShaDoW]

first of all i didnt split here "set level [lindex $arg 0]" because the levels are strict " (only voice , op , senior , admin , manager) so we dont need to split here.
second i split the nick on .o
here we see set arg [split $arg] i split the arg but we have :
if {[llength $arg] == 0} {
set arg $nick
}
and the a user that has in his nick { } does .o nick1 nick2 the bot ops the nicks if they have { } in their nicks because i split the arg but if the nick that has { } in his nick and does the command .o the arg becomes $nick and the but will not op him and that why a split the $nick
And on addhost : the host is standard because it cant have { , ] , the host is *!*@users.undernet.org
here :
-
proc pub:ub {nick host hand chan arg} {
global botnick edu
set ban [lindex [split $arg] 0]
# forgot to [split $arg] - brace problems
set why [lindex $arg 1]
the why doesnt need to be split because the why will be only the word "global"
-

I split when its necesarly.
_________________
BLaCkShaDoW Production @ WwW.TclScripts.Net

[speechles]

Any input coming from raw public binds, needs to be [split] before applying list commands onto it. Otherwise problems will be inherited from any braces already present in the string. Choosing not to fix these shows laziness, all I'm saying. At least test the script yourself using braces in both your nickname and your targets nicknames... You sidestepped this part of my last post, so I stepped back to it... Have you tested the script yourself with braces in this way?

[nml375]

The point is not the value of level, or that being a "fixed" list, but $arg not being that!

Commands expecting a tcl-list need a fully valid list, not only a part of it, in order to work. Simply stating that the first element will never hold curly braces (or other "odd" characters) won't do you any good. The whole data entity must be a valid list, or commands such as lindex will not be able to index the list properly! Thinking otherwise is foolish, and will result in non-working code, at best...

A good rule of thumb, always treat external data as insecure strings.. If you only knew what kind of damages a single accidental hostmask could cause...
That means, don't use lindex, lrange, linsert, lappend, etc with these data as list input, without first making sure it's a list. Since the data comes from an irc network, expect it not to be a valid tcl-list (average humans are really poor at crafting valid list structures).
_________________
NML_375, idling at #eggdrop@IrcNET

[BLaCkShaDoW]

[nml375]

Yes, since you actually managed to create a valid tcl structure by accident...
How about using {user{ as nickname instead...
_________________
NML_375, idling at #eggdrop@IrcNET

[BLaCkShaDoW]

And the "global" can be used only by owners. And it`s now lazyness but i have tu much work with school , work..
I understand that your advices are in the positive mean..and i will put all with split..but not right now Thanks for your time you spent on BlacKTools
_________________
BLaCkShaDoW Production @ WwW.TclScripts.Net

[BLaCkShaDoW]

same thing nml375 it works with {user{
_________________
BLaCkShaDoW Production @ WwW.TclScripts.Net

[nml375]

It is lazyness..
The flaw is even apparent in your help-command...
Just try ".h {" ..

Also, keep in mind that the tiniest of accidents with hostmasks may result in a random person being seen as someone with elevated privileges (that's why the native msg-interface always requires password verification, and there's no public commands).

And regarding the .o command, that one should work as you indeed use lists and split properly. The problem is there are numerous other commands that sporadically use split without thought...
..such as your .ub command...
Have a go at ".ub {evil!*@*.host.com" .. Perhaps not the most common of banmask, but as {} represent scandinavian characters in some charsets, this would still be a fully applicable ban on many irc networks..
_________________
NML_375, idling at #eggdrop@IrcNET

[BLaCkShaDoW]

i promise..i will split everything today
_________________
BLaCkShaDoW Production @ WwW.TclScripts.Net

[Nathema]

Blackshadow, started using 1.9 english today.

Changed the standard undernet hostmasks into a call to (i'm on Quakenet):

[BLaCkShaDoW]

Ok thanks i will see what i can do
_________________
BLaCkShaDoW Production @ WwW.TclScripts.Net