[rautamiekka]

Originally Posted by Kigen sv_max_usercmd_future_ticks 1

Heh, I knew We recently conducted small research that extremely low value[0.0000000000000000001] to that CVAR prevents bhopping quite well. So far we haven't had new Speedhackers so we couldn't test it that way.

[Kigen]

You can just set it to 0. Setting it to fractions has no effect to my knowledge since ticks aren't calculated in fractions but whole numbers.

Its just a scale for how many future ticks you wish to receive from the client. Basically, this means that the client is saying that they wanna do something before it has even happened. This can happen naturally with people that have their cl_cmdrate set higher than the server tick rate. However, the allowance of future ticks has been abused by cheaters to trick the server in allowing them to move forward to a position that they cannot by physics get to in the time frame allotted. This most famously was abused during GoldSrc (CS 1.6) where cheats could trick the server into allowing them to basically teleport right next to people or across the entire map.

Honestly, the main reason why I didn't just force that cvar's value to prevent speedhacking was because I was actively developing a way to detect speedhacking. So rather than prevent it I would ban speedhackers. The main problem is presented by server-side plugins and maps that teleport people. As I have no way of knowing if a client was teleported via the server or via a cheat.

[gward]

L 10/31/2009 - 223:12: TAYLOR SWIFT (STEAM_1:1xxxx) attempted to crash this server with rr_reloadresponsesystems.
L 10/31/2009 - 223:22: LIL' JON (STEAM_1:0xxxx) attempted to crash this server with rr_reloadresponsesystems.
L 10/31/2009 - 2253: Bad CVar response! Bandini (STEAM_1:1xxxx) has sv_cheats (sv_cheats) set to 1
L 10/31/2009 - 2253: Bandini (STEAM_1:1xxxxx) was banned for cheating. KAC ID:5.14
L 10/31/2009 - 225:46: Bad CVar response! Liquid Cocaine (STEAM_1:1xxxxx) has sv_cheats (sv_cheats) set to 1
L 10/31/2009 - 225:46: Liquid Cocaine (STEAM_1:1xxxx) was banned for cheating. KAC ID:5.14
L 10/31/2009 - 226:10: Bad CVar response! Halothane (STEAM_1:1xxxx) has sv_cheats (sv_cheats) set to 1
L 10/31/2009 - 226:10: Halothane (STEAM_1:1xxxxx) was banned for cheating. KAC ID:5.14
L 10/31/2009 - 226:21: Bad CVar response! A Kitten (STEAM_1:0xxxxx) has sv_cheats (sv_cheats) set to 1
L 10/31/2009 - 226:21: A Kitten (STEAM_1:0xxxxx) was banned for cheating. KAC ID:5.14

Shortly after the crash attempt it detected that everyone has cheats on which isn't the case. I'm one of the people that was banned and I own the server so know I didn't have cheats set to 1. Everyone was kicked from the server. The people that joined as people were kicked were allowed to remain.

It kicked everyone on the server again. No idea why. No one attempted to crash it.

[Kigen]

Someone must have forced the server to think it was setup with sv_cheats 1 for that to happen.

KAC 1.2.0 Beta should have this issue fixed.

[gward]

Your sockets only version doesn't work for me so I can't use the newest version My gameserver hosting is with gameservers.com

[thetwistedpanda]

gward read the past 29 pages. There are plenty of references to making your own no-sockets version.

[Kigen]

Originally Posted by gward Your sockets only version doesn't work for me so I can't use the newest version My gameserver hosting is with gameservers.com

Contact GameServers.com support and ask them about it.

The common error I'm aware of is GLIBC being out of date with GameServers.com

[rautamiekka]

Originally Posted by Kigen Contact GameServers.com support and ask them about it. The common error I'm aware of is GLIBC being out of date with GameServers.com

Even if that's true, it won't surprise me. In that case, their Servers are cheap due to low wage asked by their SysAdmins who probly use the first Debian Linux on offered Game Servers which of course uses old GLIBC, to put it very bluntly.

[Kigen]

http://kigenac.com/viewtopic.php?f=4&t=280

KAC really needs new staff.

I've been developing the project alone for far too long.

[bobbobagan]

Originally Posted by rautamiekka If you allow DXlevel 70, your Players using it are able to see thru some walls at least. Also most items either disappear or are transparent. That's why zBlock forbids using DXlevel 70 or lower.

I'm sure theres a proper way to still block the mat_dxlevel command to anybody outside a certain range? I remember reading a few pages back but can't find it now.