Sereglach, on 11 May 2015 - 09:26 PM, said:
This . . . just . . . wow. For one, there's plenty of middleware to sniff out cheaters/hackers. For two, RSI (Star Citizen) is another game being built on the CryEngine and they've also stated that there's already a TON of tools to help them prevent cheating, and they plan on squashing it every time it comes up. Therefore, your statements about CryEngine are already debunked from official sources.
I'd really like more information about what forms of hacking they're addressing and how they're doing it, so I'm going to go look this up now.
Sereglach, on 11 May 2015 - 09:26 PM, said:
For two, most cheating doesn't happen in the game engine, it happens with exterior plugins and addons that alter data that's sent through the network traffic; or they directly alter game files. Both of these things are actually pretty easily detectable by the right tools. Network traffic is wrong/off, or the data in files isn't matching up with what the servers say it should be.
This is the biggest eyeroller. Even when I was a kid playing Brood War UMS games with a maphack (which is analogous to walling) I knew this. Aimbotting, much less something much more subtle like walling, doesn't require any data to be transmitted to and from the server that would be subject to verification, much less directly altering game files. Blizzard, a much larger company with a much larger budget, can barely, if at all, catch people maphacking in Starcraft 2.
Sereglach, on 11 May 2015 - 09:26 PM, said:
For three, have you ever sat down and coded something big? I'm not talking a couple hundred or even thousand lines of code. MWO is in something like the millions of lines of code at this point. It's really easy to mix up one small thing and cause unexpected effects. For example, the engine probably handles most, if not all, modifiers to the weapons as multipliers, but yet they stack additively. Therefore, it would have been really easy to have a situation that was meant to be a +(addition, in case you need to be told) be treated as a situation with a *(multiplication, in case you need to be told).
Regardless of the specifics of how the final jam chance is calculated, it either demonstrates a lack of understanding about something very basic in their own code or demonstrates that whoever was working on quirk values can't do basic math. The end results of the UAC jam chance quirks they initially put in the game was very different from the effect they clearly intended. Compare the UAC jam chance quirks before:
http://mwomercs.com/...h-notes?id=1132
and after:
http://mwomercs.com/...h-notes?id=1159 . Somehow this made it through? This is a very unnecessary discussion and I only brought it up to illustrate that a basic mistake like this, something caused and fixed by changing a few numbers, no new code necessary, made it through. Even if they never made a mistake like this, I don't think that would actually increase the odds of PGI making an effective anticheat.
Sereglach, on 11 May 2015 - 09:26 PM, said:
Lastly, even if something is vulnerable to hacking doesn't mean that there aren't things to address it. That's like saying that there's nothing stopping you from walking off on a White House tour and going into places you're not supposed to go. You actually can just wander away from the tour (like hacking, in this case). After all, it's not even roped off. However, it's really stupid to do so, because before you get to round that next corner there's going to be a lot of people with really big guns waiting to "remedy the situation" and get you back to where you need to be, willing or unwilling.
In this case, because people weren't willing to play the game honestly and do what is expected of them, the situation was "remedied" in a very direct and unwilling fashion for the cheaters.
Perhaps a better analogy would be that you have a disembodied consciousness that can fly around while on the tour that no one else can see, allowing you to see more than the tour operators intended. And also the guards have glaucoma. This is very imperfect, as it does not include any mention as to how your fellow tourists' experience was harmed by your actions, as cheating would certainly do, but it is an analogy.
Edited by Coordinator Aigis Kurita, 11 May 2015 - 10:17 PM.