Register
Events
Popular
MoreOK, I'll be the idiot for everyone else on Google:
WTF are the codes for in the "kicked for violation" disconnects?
I've heard various things from various threads, but no definitive list of codes and their attributed errors. Now, I understand that sometimes, coders will throw up obscure errors to keep the public confused and guessing, because there are bugs in the code that are just unresolved. But my understanding with these is that they're a direct result of enforce.truth, so I'm just failing to see a reason why there's not information on what the violation codes actually represent? Are they even a code? Or, an actual value on some property?
-
-
Dafuq?????????????????????????????????????
Its just some script, not enabled on all servers, it is there to encounter some exploit abuse.
I only remember getting kicked for going through doors that actually seemed to be open but were in fact closed (happens when you alt-tab during the game).
-
Different "kick for violation" errors have different codes with them. Supposedly they all represent different things, he's just asking for any information regarding what they all mean.
Certainly does not require 40 question marks in response, it's a legitimate question.
-
That I'm aware of.
My question is, what are the numbers in the violation? Do they represent a Failure Code, or are they a value to a property?
Edited:
Ding! Ding! Ding!
I'm glad someone here understand my question. Now, if only we can get the answer...
-
This question has been asked many times before...
...I have yet to see a list matching the code violations though...so good question.
I'd like to know as well.
So far though, I know you can violation kicks sometimes for desync/lag and sometimes for door or geometry clipping, i.e. walking through a door too fast or if you manage to get yourself stuck on some geometry.
-
It would be nice to know what they are. I get the kicked for violation thing 4 or 5 times a session. Usually when it's real stuttery or laggy. I try to avoid the known bad areas (like around giant towers or anywhere near the center of small rad town.) If I knew what the violation was, I could alter my play to avoid whatever randomness is being violated.
-
16th April 2014 Last edited by Kanegasi; 16th April 2014 at 02:17AM. (wrong boolean values (t/f instead of 1/0))
Post #7
There are two server commands/options called "truth.punish" and "truth.threshold". The "truth" function is a very basic front-line defense against possible cheating/hacking. This is some kind of internal calculation that monitors the difference between your client and the server. If this function calculates a high enough number pertaining to this client/server difference, it will "violation kick" the player. The number associated with this violation kick is the calculated value at the time of the kick. The default value of "truth.threshold" is 400. If a calculation goes above 400, the player gets kicked. "truth.punish" enables/disables this function with "true" or "false" respectively.
No one knows exactly what is involved in these calculations or exactly what the difference is, if it's anything more than the difference between your ingame position in your client and the position in the server. In my experience, both playing on other servers and monitoring my own, the majority of the time this truth function serves to annoy lagging players more. A truth violation commonly happens with falling players or players opening/closing doors quickly while passing through, suggesting that this truth calculation takes into account objects relative to a player's position or somehow your client position ends up on the opposite side of the door from the server's position.
If a server owner wants to help fix truth violation kicks, increase the "truth.threshold" value or just disable it as mentioned above. My server has it set to 1000 and I haven't seen a kick in weeks.
-
Thanks Kanegasi! I was really starting to assume that it was a value and not a code, your post confirms that. Unfortunately, that means that these violations are very vague and really don't help indicate any misconduct from a player, aside from having shit-tastic internet.
-
When I began my server and had that initial rush of players, I started teleporting while invisible to players who had a violation kick and followed them around to catch them cheating somehow. None of them did anything abnormal, so then I just arbitrarily chose a few of the high numbered kicks. Eventually I realized that even though they're called violation kicks, there wasn't really a solid sense of violation. That's when I began testing it while observing known lagging players and the console.
-
I've been able before to replicate the conditions for a violation kick. I created a wooden shelter, put a door on it, put a wooden barricade right behind the door (inside) and then put another wooden barricade right behind the first barricade, there's barely enough room for it and it may take a little angling but once you do it, you're literally stuck in the very back of the shelter while partially clipping through the second barricade you placed. You'll get kicked, log back in, you'll be right back in the same spot and will get kicked again within about 30 seconds of logging back in. This will repeat until you suicide or otherwise find a way to get yourself unstuck.
It's pretty similar to the door kick, because the client/server detects you clipping through geometry and boots you from the server.
Ironically, it pretty much only kicks people who manage to glitch through game geometry but doesn't seem concerned with players using no-clip cheats.
Dumb x 2
Informative x 3