Cheating Manual, Tools and Equipment

[Pepe]

Is cheating taboo?

It's third mod I play (with great pleasure again), but what NEW have we done to prevent cheating? Get a proof, they say, all "awesome" pilots use some cheat... But, how? Is there any OFFICIAL place I could read about known cheats and how to get the proof? Are we encouraging cheating?

I've heard about aimbot, jitter, hitbox and lag so far. Some "smart-aces" can see their targets close and large, while targets see them far and small. Wtf Woodoo? And no one knows how to prove any of that, except using /pingtarget command on some poor soul which little brother is using youtube atm. But ofc we are losing good old members, fair pilots and good RP-ers. In tons!

Or is there any hint how to use a CD (for example) to find out if someone cheats? Or Nuke? There are plenty of hints about CDs, but how about some basic cheat-diagnostics? And if CD can't reveal out a cheater, redesign it please. You done miracles before, don't say you can't make it. Make CDs (or anything) somehow able to detect cheats, please.

Would some manual about cheats make more cheaters? Sure it would. So we can ban them while they are still small.

[SnakThree]

What is CD?

---

[Vigilia.Procuratio]

It is generally not wise to discuss known exploits as it can provide useful information to those actually wanting to cheat.

I have worked in an anti-cheat environment before and we always removed any content which was sufficient in showing the viewer how to perform a specific exploit. This ensured that the integrity of the game in question was not compromised further than it already was. In fact, I actually developed a tool which came to be used by staff to discover cheating and that tool itself could be used to cheat in the game, so naturally it was never disclosed to the general members and issued only to administrators.

There could, after all, be exploits which have the potential to ruin a game if used en-mass, and that is not what we want so disclosure should not occur under any circumstance.

Having said this, if there is a way to detect cheating without actually identifying how that cheat is executed then I for one would promote that concept. Otherwise, not a chance.

I don't believe that there is a greater authority in this game than the team we have here, as the original game developers have nothing at all to do with it now, aside of mere copyright. I'm happy to accept that the team are quite capable of discussing any matters behind the scenes and dealing with specific issues as and when they arise. We do not need to be discussing cheating in the open unless there is an obvious flurry of activity. There do appear to be problems right now but nothing which can easily be proven by the client, so it's all hypothetical (okay, "Douchebag" was blaaaatantly cheating but that was a rare case). I'm sure that if the administrators feel a specific problem is widespread and that they have established a way for players to detect its use then they'll likely mention it. Until then, there really is no point in members taking actions which might potentially worsen any such situation.

[Pepe]

There could, after all, be exploits which have the potential to ruin a game if used en-mass, and that is not what we want so disclosure should not occur under any circumstance.

Having said this, if there is a way to detect cheating without actually identifying how that cheat is executed then I for one would promote that concept. Otherwise, not a chance.

If you (or anyone) didn't see any easy to miss lucky sniper/snacer today, it's only because you didn't battle. Some days ago 4 of them were reported in chats and PMs for just one battle, with no way to prove a thing ofc.

Cheaters are not en-massed yet, it's true. Only spoiling fun and leaving Disco are en-massed atm. Pity for any mod that someone worked a lot on.

Is current /pingtarget command limited? Even Wikipedia states that jitter can be tested by repeated 160 picoseconds pings. I'm pretty sure devs source of knowledge says much much more. Hitbox can be simply measured by server side and compared to true one. Many security operations can be done while undocking. Don't take me wrong, those examples are not my suggestions. I dunno a thing about FL engine. I simply think devs put too much efforts to things that are less important than the right to play fair.

---

[Kazinsal]

160 picoseconds of increase in ping is equivalent to adding another foot of ethernet cable between your computer and your router.

---

Retired, permanently.

[Pepe]

160 picoseconds of increase in ping is equivalent to adding another foot of ethernet cable between your computer and your router.

Hey, I'm talking about Wikipedia definition of jitter tests. Wiki probably say picoseconds were invented to measure duration of my last sex. But it's not true! Miliseconds are for that!

Ofc devs know better than Wikipedia. And devs have CD, Nukes, Novas, /pingtarget, scan...

I appeal right people to start inventing tools to catch some cheats. Not all, just some for a start. Some is better than nothing. Than will see.