Page 1 of 1

[XASECO2] Anti cheat bug ?

Posted: 03 Apr 2018 09:50
by Askerad
Okay so i've been trying to setup a server and i've been hitting obstacle upon obstacle upon obstacl- you get the idea.

So. Now the server's running, and my buddy tries to set his new PB on a map. First run is okay, However his second PB is not validated. i check the logs and find :

Code: Select all

[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:09.984 index: 0
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:14.051 index: 1
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:20.031 index: 2
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:09.725 index: 0
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:13.648 index: 1
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:19.436 index: 2
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:26.732 index: 3
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:28.542 index: 4
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Finish: 0:28.542
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:10.024 index: 0
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:09.735 index: 0
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:13.438 index: 1
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:09.879 index: 0
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:09.849 index: 0
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:13.775 index: 1
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:19.537 index: 2
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:09.754 index: 0
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:09.684 index: 0
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:09.615 index: 0
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:14.038 index: 1
[XASECO2 Warning] Cheat by 'prinovex' detected! CPs: 0:10.354/0:14.571/0:21.089/0:27.182/0:28.875 Last: 0:19.983 index: 2
After some research, i found out that Xaseco was checking for cheating by ensuring correct CP order. (like index 1 comes after index 0).

HOWEVER. Here we can clearly see his checkpoints from his first run are never flushed. We can see his PB (Finish: 0:28.542) and it didn't register.

Now for the questions : Is this a common issue ? was there any precedent on this ? could it be a permission problem on my part ? (server runs on debian 9) How can i fix it ?