i am using it, i do ban but player back after few mins 3/5mins
// DiveBan X 2019
// Serial Number of the plugin | Serial Number
// Put key here | Put key in this cvar
License_Key ""
// Secret Key | Secret Key
// Secret key is used for clear banlist
Secret_Key "mykey"
// Flag of main Admin | Flag of main Admin
// Main admin can ban and unban everyone |
divebans_flag_main "x"
// Flag of Deputy Admin | Flag of Admin
// Deputy admin can ban everyone and regular admins | This admin can ban any players without main Admin
divebans_flag_sub "g"
// CsBans support
divebans_support_csbans "0"
// CSBans tables prefix
divebans_csbans_prefix "amx"
// Name of Server for ban
// If empty, server name will be used
divebans_server_name ""
// Delay before ban/kick | Delay before kick/ban
divebans_delay_time "5.0"
// Time between kick player when he is banned.
divebans_kick_time "1.0"
// Time between checking player ban.
divebans_check_time "1.0"
// Subnet ban limit
// If you have players with the same IP, set 1, otherwise - 0
divebans_prevent_ip "1"
// Sync time with SQL
divebans_sqltime "1"
// Time of max power of ban
// If there are false ones, reduce the value by half or more, otherwise do not touch
divebans_maxeffect_time "1440"
// Ban by Cookies | Cookie Ban
// We will work if you specify two following cvars
// Path to file ban.php on your web server | Path to file ban.php on your web server
divebans_cookieban_banfile "http://host/diveban/ban.php"
// Path to file check.php on your web server | Path to file check.php on your web server
divebans_cookieban_checkfile "http://host/diveban/check.php"
// Sending command to the client | Client cmd type
// 2 - When banning use SVC_STUFFTEXT, in other cases client_cmd, 1 - only SVC, 0 - only client_cmd
// 2 - When ban player use SVC_STUFFTEXT, and when connect use client_cmd, 1 - only SVC_STUFFTEXT, 0 - only client_cmd
divebans_cmd_type "0"
// Log level \ Log Level
// Values\Value : 0 - 1
divebans_log_level "0"
// Specify how many days the logs will be stored\Enter number of days for store logs
divebans_clear_logs "7"
// Log by what tag the player was detected. \ Log the marker on the player
// Extra load after all :D
// 0 - off
// 1 - Only steam\ip
// 2 - All (Steam\ip\cookie\name\lastname)
divebans_marker_log "2"
// Log of players with >= bans \ Log players with bans value greater then current value
// 0 - off
divebans_bancount_log "0"
// Check for updates \ Check updates
// 0 - off, 1 - every map, 2 - every day, 3 - every week, 4 - every month.
// 0 - off, 1 - per map, 2 - everyday, 3 - per week, 4 - per month.
divebans_check_updates "0"
// Check for actual ban before banned player
// 0 - don't check (off), 1 - check (on), 2 - optimize (optimize)
// In fact, this will remove one query to the database before banning a player, but then you can ban the same player
// If you set it to 2, there will be no query to the database, and the ban will try to locally determine the presence of a ban.
divebans_check_ban "2"
// Cache
// Caching players to reduce the number of queries to the database. Necessary if there are many players (up to 32) on your server.
// Cache Status 0 - off, 1 - on \ 0 - Off, 1 - On
divebans_cache_status "1"
// How long to remember players (in maps) (by default for 2 maps) \ Cache time for players (default 2 maps)
divebans_cache_time "2"
// Delayed
// Stores all players on the server so that you can ban them by IP\Steam\name at any time via the website
// Delayed Status 0 - off, 1 - on \ 0 - Off, 1 - On
divebans_delayed_status "1"
// How many days are the players stored (in days)
divebans_delayed_store_days "7"
// More server load, but faster search
// If you are very rarely use this function then set to 0
divebans_delayed_optimize "0"
echo [DiveBan X] Config 'diveban.cfg' loaded...
thanks for answer, i have it already but this one work for steamers only i guess (steamID/IP) ban
thanks for answer bro, dopban i never tried, fresh ban is just menu ban with time/reasons right? , Bypass Guard to block proxies&vpns ASN, reunion iam not sure how it can help with bans
11214 клиентов имеют оригинальные STEAM_ID и в случае бана тоже не смогут зайти на сервер. Поэтому 95% игрового трафика можно заблокировать с помощью 1 единственного бана. 1644 из оставшихся игроков имеют 3 и более STEAM_ID получив бан по любому из которых они, с очень большой долей вероятности, не смогут более зайти на сервер. Они "склеены" методом, аналогичным DopBan, который вы зря критикуете. Уровень фильтрации в 99,5% для паблика - сверх избыточный, потому что для поддержания онлайна все таки приходится "закрывать глаза" на некоторые нарушения.Паблик это всегда баланс между количеством игроков и их качеством. На каждом проекте он свой. А выследить и закрыть доступ на сервер какому-то одному очень "настойчивому" игроку с любыми географическими или сетевыми признаками - дело 5 минут. В этом случае покупка разбана будет неизбежной и это будет намного дешевле эксплуатации средств для обхода установленных ограничений. Это уже проверено временем.
If use 1% of brain then they gonna understand what are they doing, btw it easy can be bypassed, i did yesterday, the main result that you are getting that percentage is because ur server is 32/32 in moostly of the time, with proper protector, with steamid changer by settind sid steam, and 1 value, because its hard to enter from first try i get kicked like 4,5 times with reason server full, then it records nick, steamid, ip, if compare and not match values, kicks with reason steamid changer. I have done something that i should not be used in not any way that method is forbidden in any cases game is exploitable and ond so no one cares.kaktuspo, You are full of pessimism. I looked at the current data of our project for the last 3 months... out of 37876 unique and active STEAM_ID - 24820 have such a unique "identifier" that does not depend on the client...
Public is always a balance between the number of players and their quality. Each project has its own. And to track down and close access to the server to one very "persistent" player with any geographical or network characteristics is a matter of 5 minutes. In this case, buying an unban will be inevitable and it will be much cheaper than using means to bypass the established restrictions. This has already been tested by time.
PS: If Karaulov had not shared the source code of his anti-cheat plugins with the general public, cheat developers would not have been able to implement means of bypassing these restrictions so quickly.
, который закрыл вам доступ на сервер для стим версии игры с любыми вариантами вашей "защиты".. Попробуйте используя 1% своего мозга, "все почистить" и войти с любой учетной записью STEAM 
Я не нашел никаких других признаков вашего "обхода", с того же компьютера (физически), поскольку все ваши 4 попытки закончились неудачно 
you are so annoying, just prove you can bypass diveban without to change the client, but all what you can do is just to say some irrelevant words without proof
what? will you also beg a cheater: "I ban you, but please do not change your client. "