Rule enforcement

[TittenIgnition]

nooo santile how could you D:

[bunny]

Deleted (2011-04-10):
Khetti (+left) [demos]

Santile (+left) [demos]

freakin liar...

[<hk>]

care to elaborate?

[bunny]

santile just has a very large desk, no need to check the demos (don't u trust him?)
and khetti didn't say anything about using +left either

u btw forgot to do sumthing about all the others, like novaa, ryze or ally

besides that i would really like to see any proof... u just shared sum demos there and i see no attempt even to try on explaining why we all have to be convinced that these two fellows are cheaters now

mb ure paranoid or just don't like ppl(people) with an i at the end of their nick..anyways, how u handle this stuff is not very satisfying and u might want to consider getting urself sumone to help u there (after all, i'd say the freakin server demos only made us get rid of 1-2 cheaters so far..lots of potential nobody seems to give a shit about)

[<hk>]

santile just has a very large desk, no need to check the demos (don't u trust him?)

Well, duh!

u btw forgot to do sumthing about all the others, like novaa, ryze or ally

I only check demos on accusition. My time is somewhat limited. Especially right now.

besides that i would really like to see any proof...

When it's obvious, I don't explain demos. Turn on the gaz hud with the compass and you can see the turn rate. But OK, since you asked for it.

These are the yaw values dumped from the demo. I substracted the advance of every previous snapshot so you can see how much the player turned since the last snapshot.

Khetti:

Code: Select all

[servertime (time since last snapshot)]: yaw angle change since last snapshot
[1187904 (64)]: 2.834473
[1187968 (64)]: 2.834473
[1188032 (64)]: 2.834473
[1188096 (64)]: 2.131348
[1188160 (64)]: 3.306885
[1188224 (64)]: 2.834473
[1188288 (64)]: 2.839966
[1188352 (64)]: 2.598267
[1188416 (64)]: 2.834473
[1188480 (64)]: 2.834473
[1188544 (64)]: 2.603760
[1188608 (64)]: 2.598267
[1188672 (64)]: 3.070679
[1188736 (64)]: 2.598267


Yeah, that's right. Identical down to the 6th digit behind the decimal point.

Santile:

Code: Select all

[servertime (time since last snapshot)]: yaw angle change since last snapshot
[998064 ( 8)]: 0.368042
[998072 ( 8)]: 0.324097
[998080 ( 8)]: 0.324097
[998088 ( 8)]: 0.368042
[998096 ( 8)]: 0.411987
[998104 ( 8)]: 0.368042
[998112 ( 8)]: 0.411987
[998120 ( 8)]: 0.324097
[998128 ( 8)]: 0.368042
[998136 ( 8)]: 0.324097
[998144 ( 8)]: 0.368042


One might see a pattern here. In case you aren't any good with numbers:
All the numbers are the same. That's because the script turns with the exact same speed.

And this is what a normal run looks like:

Code: Select all

[servertime (time since last snapshot)]: yaw angle change since last snapshot
[1444368 (72)]: 0.818481
[1444440 (72)]: 2.900391
[1444512 (72)]: 5.976562
[1444584 (72)]: 4.158325
[1444656 (72)]: 3.345337
[1444728 (72)]: 3.202515
[1444800 (72)]: 2.680664
[1444872 (72)]: 2.955322
[1444944 (72)]: 3.499146
[1445016 (72)]: 2.362061
[1445088 (72)]: 1.966553
[1445160 (72)]: 2.416992


Also, did you notice that these demos are a sequel?
You can watch them in a row. Start at the slowest demo and watch all the way up to the fastest. They never reset their mouse. Not even at the 4th revolution.

[bunny]

ty!

to the ppl(people) who wonder why hk not just parses all the demos, looking for this to happen:
that would be black magic, which is forbidden in our country

[<hk>]

I didn't get to writing a proper smoothing algorithm that enables me to scan for such things automatically.
As you can see the values tend to jitter, even though the turn rate is the same. We don't have that many cheaters.

[Arcaon]

A "normal run" doesn't tell me much. Can you post some yaw values from one of my runs (recycle for example), and a yaw script? Just for reference.

[<hk>]

This IS the reference.
I can give you your values but it takes time to download,parse and check the demo. My diploma thesis is due on May 1st. I can spend some time on these kinds of things after that. I am planing to write an article about smoothing demo data and finding patterns.
You'll have to wait.

What you can see in the 'normal' run is that the values differ every time. They may be close to each other every now and then but not exactly the same.
That's because you can't turn your mouse 100% smooth. The flicker in the values that pop up are there, due to an aliasing effect.
With the new server demo system I am going to write pretty soon, this won't be a problem any more.

[$$-albion]

This IS the reference.
I can give you your values but it takes time to download,parse and check the demo. My diploma thesis is due on May 1st. I can spend some time on these kinds of things after that. I am planing to write an article about smoothing demo data and finding patterns.
You'll have to wait.

What you can see in the 'normal' run is that the values differ every time. They may be close to each other every now and then but not exactly the same.
That's because you can't turn your mouse 100% smooth. The flicker in the values that pop up are there, due to an aliasing effect.
With the new server demo system I am going to write pretty soon, this won't be a problem any more.

I'd say good luck with the thesis Things like this can wait, the example is pretty clear now. And btw arca, yours would just be something like:

Code: Select all

[Arca cheat run]: yaw angle change since last snapshot
[35465 (00)]: N/A
[35474 (00)]: N/A
[35483 (00)]: N/A
etc...