[Fixed] banning nick

[light-angel]

when i try and log in with a multi hub bot i keep getting this

 [Invalid Connection] [1] IP: ***.***.***.** is autobanned for two hours. Message: $Key òÑÀ° A ѱ±ÀÀ01‘ Ñ
ÑqÑ!‘Ñ‘ ѱ±ÀÀ01Q/%DCN096%/aö|$ValidateNick ****|

i have tryed protecting the ip and nick but keeps happening

[FlipFlop™]

The bot doesn't send a $Supports first, it starts with $Key. A lot of spambots use this, normal clients (if they aren't ancient) do send the $Supports first. To prevent a lot of old spambots from connecting the IP is autobanned when $Key is sent first.

So to be able to connect you could modify the hubbot (or have it modified by the coder) to first send $Supports.

[FlipFlop™]

On second thought: I can make an exception for protected IP's, so the bot can login.
Update: added this for next update

[Flopp]

So they can fill up hubs with bots? Fake promotion.

[light-angel]

So they can fill up hubs with bots? Fake promotion.

errr no not fill it up with bots its just one bot what dose chat thought diffent hubs

[FlipFlop™]

Indeed, since this was about a multihub bot i assumed it was to link chat. Not to fake users.
I've looked into it, and it still is proper NMDC protocol, if the client doesn't support any special options, then $Supports doesn't have to be sent.

Hubowners using fake users in their hub will find a way anyhow, there are probably more scriptkiddies able to fake users than to write a proper hubchat link...

Allowing it won't be default on protected IP's though, i'll add an option for it that needs to be enabled for it
allow no $Supports to be sent on protected IP's.