adch++ dont disconnect user

[Janne]

we run 2.9.0 r624 with TagCheck2.01LUA5.1x [strict] [API 2]. Lua this kicks the user but dont send a message to the user why they've been kicked on connect. if you have good speed typ 100 Mbit will the message sometimes pops up at connect but not on lower speeds..

I think this has to do whith soft only have 5 sec to disconnect ??
the soft kicks out the user before the message is sent to the user
we have about 1000 users

we run 2.10.0 r641 with TagCheck2.01LUA5.1x [strict] [API 2]. Lua this dont kicks the user but send a message to the user that he has the wrong number of slot on connect but user never gets disconned.

somthing is wrong I've talked with Night and he would talk to Poy about this problem

we need help

Janne

[poy (poy)]

hi,
thanks for the report.
rev 110 should fix this.

[Janne (barajag)]

why disconnect user before reason? still have the same problem in new soft and bridge.
we have change the disconnect time to 15000 and it seems to work better.
 has this to do because we are so many users?
softet kicks user before reason have time to get to user

Janne

[Janne (barajag)]

15000 might be too much but I tested with 15000

[poy (poy)]

that number should have been a setting because it depends on each hub (for example the current 5000ms works just fine for me). ADCH++ 2.11, to be released shortly, will allow changing the setting from adchpp.xml: it's the "DisconnectTimeout" setting.

so when you have it, just adjust DisconnectTimeout in the config file (make sure to remove the <!-- TODO and --> lines that used to surround it).

[poy (poy)]

check rev 112 for a better fix (that allows every bot to issue bans, not just the main bot).