It seems that the plugin is not functioning well.

He was kicked by AdKats but he was never kicked by the BF4DB plug-in.

There was not such a thing as ever.

Plugins 06/05/2018 09:33:12 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:33:23 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:33:37 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:33:52 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:34:03 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:34:18 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:34:33 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:34:44 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:35:00 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:35:10 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:35:22 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:35:33 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Plugins 06/05/2018 09:35:45 BF4DB PluginAction BF4DB FAILED to issue Kick Player on [Vvip]SadCrow2 for [BF4DB] Suspicious Stats. Appeal at https://bf4db.com/player/ban/1895522271

Banlist 06/05/2018 09:35:46 GUIDPermanentBanned EA_CAF72B3F0C2282164DD3B91806CB3DE9 [HSK Automatic Ban [6-AK12-93-115-107-315] [AutoAdmin]] was permanently banned from the server

Playerlist 06/05/2018 09:35:46 PlayerDisconnected SadCrow2 disconnected from the server (reason: HSK Automatic Ban [6-AK12-93-115-107-315] [AutoAdmin])

Playerlist 06/05/2018 09:35:46 PlayerLeave SadCrow2 left the server

Plugins 06/05/2018 09:35:46 AutoAdmin PluginAction AutoAdmin issued Permaban Player on [Vvip]SadCrow2 for HSK Automatic Ban [6-AK12-93-115-107-315]

I noticed a similar thing when a stats analyzer is installed. The stats plugin will "reserve" the player so it can finish checking the stats. In the meantime other plugins can not kick. So seems normal.