Variables */? at nick level for bans

Ask your questions about ircu and GNUWorld, share your ideas, and help the coders in their work.
gemeau50
Posts: 76
Location: Trois-Rivières, Canada

Variables */? at nick level for bans

Post by gemeau50 »

Ex.: Nick baby^angel

This nick is a spambot joining the network from different ISP and using little variations in its nick format.

Unfortunately, a ban on the following address is not recognized by X:
*baby?angel*!*@*

Variables are not accepted in the nick portion of an address. Can't imagine why and it is annoying.

User avatar
Homer
Posts: 212
Location: Springfield, IL

Post by Homer »

Unfortunately, a ban on the following address is not recognized by X:
*baby?angel*!*@*


try *baby*angel*!*@*
If at first you don't succeed, then skydiving definitely isn't for you!

gemeau50
Posts: 76
Location: Trois-Rivières, Canada

Post by gemeau50 »

Homer wrote:try *baby*angel*!*@*


-X- Je ne vois pas *baby*angel*!*@* sur le canal ????????

Unless I used the exact nick, I get this reply. It seems that the nick must be exactly what it is on the channel. Also if the nick isn't on the channel anymore, it won't even accept a ban on the exact nick.

User avatar
lupuroshu
Posts: 14
Location: In the wonderland

Post by lupuroshu »

Did you really use /msg x ban yourchannel *baby*angel*!*@* 336 <your_access_level> Stop joining here ? I think that will do the job. Better yet, try loading this in the remotes: on 1:JOIN:#yourchannel:*baby*angel*!*@*:{/msg x ban # *baby*angel*!*@* Stop joining here!}. And if I didn't write this snippet correctly, please let me know ;)
Windows loaded - System in danger. To fix this error, please install Linux or *BSD. mIRC loaded - User in danger. To fix this error, please type ALT+F4.

gemeau50
Posts: 76
Location: Trois-Rivières, Canada

Post by gemeau50 »

Yes, the command was properly entered. My problem is not to keep this user out of our channel, I can easily do it via my eggdrop or simply use /mode +b or /ban.

lupuroshu wrote:on 1:JOIN:#yourchannel:*baby*angel*!*@*:{/msg x ban # *baby*angel*!*@* Stop joining here!}. And if I didn't write this snippet correctly, please let me know ;)

As far as for your snippet, there is no provision for matchtext in an "on join" event.

The on JOIN and on PART events trigger when a user joins or parts a channel.
Format: on <level>:JOIN:<#[,#]>:<commands>

on *:JOIN:#channelname: {
if (*baby*angel* iswm $nick ) {
command
}
}

What I am saying is that X is refusing to register bans of the following format in its banlist.

*baby*angel*!*@*

Hoping that you will be able to test it on your channel. Let me know if you were able to do it.

User avatar
sirAndrew
Posts: 760
Location: Romania

Post by sirAndrew »

Yep, X is stupid...doesn`t recognise

Code: Select all

^


Example:

Code: Select all

* ^baby^angel has joined #k.o
-> *x* ban #k.o ^baby^angel*!*@*
-X- I can't find ^baby^angel*!*@* on channel #k.o



The coders should do something about it. On other GNUworld versions it works. :cry:
sirAndrew @ Undernet.org

8 years on this forum and i'm still the #1 poster around.

User avatar
Homer
Posts: 212
Location: Springfield, IL

Post by Homer »

thats why * exists, to replace such codes that can't be read.

I would suggest to try to ban them when they are online, or else do a little game, join with a nickname that looks like that, set the ban on the nickname (you'll be able too) and then quit and let X taking care from that time.
If at first you don't succeed, then skydiving definitely isn't for you!

User avatar
sirAndrew
Posts: 760
Location: Romania

Post by sirAndrew »

You think Homer?! looky here...i did a test:


Code: Select all

* ^baby^angel has joined #k.o
* X sets mode: +l 15
-> *x* ban #k.o *baby*angel*!*@* Drones
-X- I can't find *baby*angel*!*@* on channel #k.o



The name of the channel is just informative and it has no spamm purposes!

X doesn`t recognise ^ and end of story....weird too!
sirAndrew @ Undernet.org

8 years on this forum and i'm still the #1 poster around.

User avatar
Homer
Posts: 212
Location: Springfield, IL

Post by Homer »

got the same error, my mistake. used to work dunno about it.

you may also e-mail to cservice@undernet.org and might be added into X or else be check if there is any bugs that keeps X from reading such charecters such as * & ?
If at first you don't succeed, then skydiving definitely isn't for you!

User avatar
DUNCAN_
Posts: 38
Location: Stars Hollow

Post by DUNCAN_ »

Nick bans only can be given on a exact number of chars. it's not about the wildcards. try banning *baby?a*!*@* . I don't know the max chars a nickname ban can use , but i'm sure you'll find out in #coder-com.

OUTsider
Posts: 435
Location: Netherlands

Post by OUTsider »

this topic has been discussed before.. regarding the error with X, it is known. blame cservice for not caring about the fix I cooked up for them.

regarding the topic.. please pretty please use the damn search feature first.
Don't bother reading, I'm just the lame botlender, right ?