Clan x86

Technical (Development, Security, etc.) => JavaOp Board => JavaOp Support Archive => Topic started by: fearful on April 09, 2008, 10:46:41 pm

Title: JavaOp suggestion
Post by: fearful on April 09, 2008, 10:46:41 pm

I have a suggestion for JavaOp it will be nice if the bugs for banning would be fixed... e.g

.ban fearful@useast <~ will ban even if i'm the master
.ban fearful, <~ will ban even if i'm the master too

Title: Re: JavaOp suggestion
Post by: iago on April 09, 2008, 10:53:39 pm

I think it's because it was originally written with the assumption that they'd always be on Starcraft.

However, the second one doesn't seem to make sense.. it shouldn't be able to ban if the exact account is set to "M". If it is, then there's either a more serious bug, or you're doing something wrong. Can you confirm that you have the right flags?

Title: Re: JavaOp suggestion
Post by: fearful on April 09, 2008, 10:56:04 pm

Well yea I can confirm I have the right flags: fearful => ACDFMNOPQSTU

but this bug was encounter in all the bots ever created... so i think its a b.net bug but you should fix that on Java Op

Title: Re: JavaOp suggestion
Post by: Joe on April 23, 2008, 04:20:55 am

The magic is the comma in your name. This is a bug with Battle.net. Issuing a ban on iago,lol will process as iago, as will "iago,sucks", "iago,iscool", and "iago,isabetterprogrammerthanjoe". Simply splitting at the comma before checking access should do the trick.

I'll add this to my to-do list. Thanks!