News for hackers. Stuff that matters.
Re:EA is permanently banning Linux players on Battlefield V by Aperocky on Friday January 03, 2020 @11:54AM (#21947662)
The real solution? Send only information players are supposed to see. Sacrifice some speed for true cheat proof games.
Re:EA is permanently banning Linux players on Battlefield V by dharmab on Friday January 03, 2020 @11:59AM (#21947718)
That wouldn't prevent commonly used cheats such as aimbots.
Re:EA is permanently banning Linux players on Battlefield V by AnthonyMouse on Friday January 03, 2020 @12:37PM (#21948200)
Maybe the solution there is to stop making games be about the things computers are better at. They're better at aiming, fine, let them be. Put the aimbot in the game from the start.

Then instead you have a FPS with multiple weapons and it takes several seconds to switch between them. One has a high rate of fire but is useless against players with armor, another is the opposite. Cheaters don't know if the opponent is wearing armor (or what kind) because the server doesn't tell them that until they're in the same room, by which point it's too late.

Make certain weapons better against certain defenses, so it's a matter of predicting what your opponent will do and being ready for it. Make the humans do the things that humans are still better at, instead of trying to prevent a computer from beating them at things computers are better at.

Re:EA is permanently banning Linux players on Battlefield V by m11a on Friday January 03, 2020 @01:35PM (#21948849)
You can't tell people to play something else other than what they enjoy just because it'll "make cheating harder".

Many of the very popular games now require good aim. Some people spend countless hundreds/thousands of hours just practicing their aim and muscle memory. It's part of the fun for them. CS:GO is a notable example.

The problem isn't really that it's impossible to ban such cheating. ESEA do it pretty well in CS:GO - their anti-cheat is practically a RAT.

It's that banning cheaters and making a bulletproof anticheat has two issues:

1) To do it properly you need to basically code a RAT, which has some privacy issues. If Valve do it, it could hurt activity, platform support, and be controversial. ESEA have done it since day one, but their player base is much smaller and more competitive. ESEA is also limited to Windows.

2) It's not profitable. That's the honest truth. They ban obvious public cheats and the cheaters will buy another account and come back, probably use another cheat again, get banned again, repeat. Some games don't have awful cheat protection because the company can't make a good one, they have awful cheat protection because it's not profitable to alienate all the cheaters in the game away from the platform (and their many purchases per person; legitimate players only buy once).

Re:EA is permanently banning Linux players on Battlefield V by AnthonyMouse on Friday January 03, 2020 @04:31PM (#21950592)
It's somewhat worse than that, because anti-cheat and anti-anti-cheat are basically two things in ring-0 fighting each other. So it's a resource war, whoever spends more development time trying to win does. But the economies of scale favor the cheaters.

If only one game has working anti-cheat, it may not be worth the cheater's time to break it because it's only one game, and they can go cheat in a different game. If all the games had it then more people would try to break it and more would succeed. And once they have a working method, it can be employed against any other game that uses the same kind of anti-cheating, even if it's not the same vendor's, as long as the mechanism is similar.

But having all the vendors get together to pool resources and design one good anti-cheating software makes it even worse, because then it might be a little harder to defeat, but the prize for defeating it is being able to cheat in every game without even having to translate the cheating method to each new game.

So you get small victories or nothing. There is no winning at scale because increasing scale only increases the number of adversaries and the gains from finding an effective way to cheat.

It's basically the same problem as keeping the latest Hollywood releases off of pirate sites. They count success as occasionally having a week before a new release is on the pirate sites instead of being there the same day, and even that doesn't happen very often.

It turns out it's more effective to make it so it doesn't matter. In their case by making it so easy and cheap to watch Netflix on your TV that it's not worth most peoples' time to figure out how to use BitTorrent even if it has 100% of their content. In this case by making more games that humans are better at than computers, so you can't use a computer to cheat.

Re:EA is permanently banning Linux players on Battlefield V by Wowfunhappy on Friday January 03, 2020 @04:46PM (#21950716)
> But the economies of scale favor the cheaters.

I feel like the concept of "ban waves" ought to help a lot here. Wait a couple weeks between banning people, and then randomly don't ban some people during the wave. Should make it pretty hard to test your anti-anti-cheat.

Re:EA is permanently banning Linux players on Battlefield V by AnthonyMouse on Friday January 03, 2020 @04:57PM (#21950812)
That's assuming the way they test is based on whether they get banned or not, instead of analyzing the anti-cheat code to see how it works so they don't get banned to begin with.
Re:EA is permanently banning Linux players on Battlefield V by Wowfunhappy on Saturday January 04, 2020 @09:56AM (#21955163)
Shouldn't most of the cheat detection be happening server side for exactly this reason? Is that not feasible?
Re:EA is permanently banning Linux players on Battlefield V by meheleventyone on Friday January 03, 2020 @05:59PM (#21951227)
Is that actually a thing that happens routinely?
Re:EA is permanently banning Linux players on Battlefield V by AnthonyMouse on Friday January 03, 2020 @10:45PM (#21952744)
Whether things happen routinely depends a lot on whether other effective alternatives exist.

It's a thing that enables cheaters to not get caught. They may not need it if they have some other way to not get caught, but you can expect to see it if it is or becomes the easiest thing that works.

Re:EA is permanently banning Linux players on Battlefield V by meheleventyone on Saturday January 04, 2020 @02:30AM (#21953495)
So no then.
Re:EA is permanently banning Linux players on Battlefield V by meheleventyone on Friday January 03, 2020 @06:37PM (#21951501)
The economies of scale actually favour the game makers. People build cheats for profit, every person that buys a cheat is also buying the game (and rebuying) the cheat makers are in competition, and further the number of people that cheat is generally a lot smaller than the game playing population. Because they are sold for profit the most popular cheats are easy to find and detect. As long as companies can keep cheating at a tolerable level for their audience they win as do a small number of cheat makers able to make a living in the space.
Re:EA is permanently banning Linux players on Battlefield V by AnthonyMouse on Friday January 03, 2020 @10:51PM (#21952766)
Scale here isn't the number of copies of the game sold (which is basically independent and for these purposes fixed), it's the number of games that have strong anti-cheating mechanisms. The more there are the more resources go into defeating them, the larger the community around defeating them grows etc.
Re:EA is permanently banning Linux players on Battlefield V by meheleventyone on Saturday January 04, 2020 @02:29AM (#21953493)
Is there any evidence this is actually true?
Re:EA is permanently banning Linux players on Battlefield V by meheleventyone on Friday January 03, 2020 @06:12PM (#21951334)
Many more people will play the fun game with cheating than will play the game you make to be “secure”.

In your game design not only is it dull because you have a 50:50 chance of having the right gun equipped to take advantage of a situation even if no one is cheating. But it’s still very amenable to cheating both because the cheat would be able to switch weapon the instant the client was informed of the state of the opponent, beating a human where it actually matters and would still be able to have a mechanically perfect aim.

Most videogames actually have the sort of human reaction prediction you are talking about and that’s why people cheat because they are bad at it. So make it up by exploiting information sent but not displayed or through mechanical assistance. The interesting case there is that mechanically good players that have a good read can beat cheaters.

Stuff like the DeepMind successes playing Chess, Go and Starcraft ultimately show that even with an environment where things are fairly level that computers have the edge in games albeit with an unattainable for cheat makers level of technology.

Re:EA is permanently banning Linux players on Battlefield V by AnthonyMouse on Friday January 03, 2020 @11:04PM (#21952813)
> In your game design not only is it dull because you have a 50:50 chance of having the right gun equipped to take advantage of a situation even if no one is cheating.

Except that it's not random, because you can try to figure it out. You know what's in the map. If you go to where a particular weapon is and it's not there, now you can expect the opponent to have it, so you start looking for defenses against it etc. Or you know that you're playing against Bob and Bob always goes for the same weapon like a chump because he doesn't know what to do with any of the others. Or you get a weapon and then go around collecting every defense against it on the map so the opponent can't get them.

> But it’s still very amenable to cheating both because the cheat would be able to switch weapon the instant the client was informed of the state of the opponent, beating a human where it actually matters and would still be able to have a mechanically perfect aim.

Which is why it's not about switching faster, it's about making the right choice to begin with. The whole idea is if you have to switch at all you're probably already dead and switching a half second faster isn't going to save you.

Re:EA is permanently banning Linux players on Battlefield V by meheleventyone on Saturday January 04, 2020 @02:29AM (#21953490)
I’d suggest you build this design and try it out because you have some really rosey eyed ideas about how this will work.
Re:EA is permanently banning Linux players on Battlefield V by spathi_fwiffo on Friday January 03, 2020 @12:41PM (#21948257)
first person/multi-player rock paper scissors. would be an interesting game.

probably family friendly.

should make it.

Re:EA is permanently banning Linux players on Battlefield V by AnthonyMouse on Friday January 03, 2020 @01:00PM (#21948465)
It doesn't even have to be that arbitrary. You've got an opponent with a defense against all your current weapons, but you can run faster than them, so you can escape but you still need to find something that can kill them. They need to find something that can make them faster so they can catch you, or take their chances by giving up the defense which is slowing them down.

There can still be strategy in it without leaving any easy way to cheat.

Re:EA is permanently banning Linux players on Battlefield V by Aperocky on Friday January 03, 2020 @12:51PM (#21948365)
We don’t even need those fancy things, just the angle of view. If someone come up behind without being seen they can still knife the player. Alternatively, the aiming would be slower if you are looking at the peripheral.
Re:EA is permanently banning Linux players on Battlefield V by drdaeman on Friday January 03, 2020 @04:33PM (#21950610)
> Then you have the mechanical helpers like aimbots

I wonder if anyone had ever designed a completely external aimbot. A camera, a computer vision system and a hardware mouse or gamepad multiplexer/proxy that mixes real controls with the adjusting movements.

That won't be fun to use (except, maybe, for PvE, if manual dexterity is just a irritating mechanical hurdle - there are games like that, too), but surely fun to hack.

Heh. Sometimes I regret that I won't live long enough to see all the drama around cyborgs in sports and gaming...

Re:EA is permanently banning Linux players on Battlefield V by LoSboccacc on Friday January 03, 2020 @12:42PM (#21948259)
if your turn speed is limited and the server only send you precise enemy position information within your field of view aimbot can only help so much, having a drop in the enemy will enable better player to overcome aimbotters

war thunder does it and it works well enough. it still has other problems, like p2w vehicles, but the system is solid

Re:EA is permanently banning Linux players on Battlefield V by Aperocky on Friday January 03, 2020 @12:27PM (#21948080)
You’re right.
Re:EA is permanently banning Linux players on Battlefield V by kgwxd on Friday January 03, 2020 @01:27PM (#21948775)
Game and console companies would love it if users only had dumb terminals with DRM protected input and output, and they're working towards that dream: https://www.ign.com/articles/2019/03/19/e3-2018-the-rise-of-...
Re:EA is permanently banning Linux players on Battlefield V by SeanBoocock on Friday January 03, 2020 @12:30PM (#21948117)
That’s already often done at some level, but doesn’t eliminate the ability to cheat via aim bots (and other similar tools). I have worked on several server authoritative multiplayer games and while they were mostly immune to common types of cheating, there are always things that people can exploit/automate to their advantage.
Re:EA is permanently banning Linux players on Battlefield V by int_19h on Friday January 03, 2020 @06:55PM (#21951632)
You have to send more than that for the game to be playable, if your game involves fast movement or turning (which is pretty much any FPS). Otherwise the player would see empty spaces after e.g. turning around, before the server can catch up with the movement.

This problem is as old as competitive multiplayer itself, and various approaches have all been tried.

Re:EA is permanently banning Linux players on Battlefield V by spathi_fwiffo on Friday January 03, 2020 @12:10PM (#21947855)
This would require a hardened OS and is outside the control of the game creator.

Transparent walls, for example, can be done via the graphics driver (or by replacing your graphics driver).

Re:EA is permanently banning Linux players on Battlefield V by derefr on Friday January 03, 2020 @12:27PM (#21948076)
No, they’re talking about writing netcode in such a way that if you report to the server that you’re in position XYZ, then it’ll cull all player-events invisible to players at position XYZ out of the event stream being sent to your client.
Re:EA is permanently banning Linux players on Battlefield V by spathi_fwiffo on Friday January 03, 2020 @12:31PM (#21948129)
I actually wonder why this isn't done.

Pre-rendering the scenes on the server and then sending those is just not really possible today due to latency -- even google can't get it right with Stadia so far.

But, if the game engine/server just crunched the line-of-sight numbers and didn't even send location data for rendering enemies that were out of LOS, then that would work and while it is heavier than doing nothing, it isn't really that heavy.

That wouldn't stop an aimbot, but it would prevent some classes of exploits.

Re:EA is permanently banning Linux players on Battlefield V by coldpie on Friday January 03, 2020 @12:37PM (#21948194)
It's not about server-side computation resources or bandwidth, it's about latency. If it takes 50ms to communicate your position to the server and 50ms for them to reply, that's 1/10 of a second for every position update, which is an eternity in high-level play. Netcode is really hard, anti-cheat is really hard, and mashing them together is really, really hard :)
Re:EA is permanently banning Linux players on Battlefield V by derefr on Friday January 03, 2020 @12:51PM (#21948368)
I think it could be possible if you structured your FPS like an MMO: build the game out of "zones" with "rooms" in them, and then clients only get pushed events for the "zone" and the "room" they're in. (Unlike an MMO, the whole map and all relevant models would always stay loaded into memory, so there wouldn't be any latency in transitioning between rooms; there'd just be a moment where you'd be outside and not see anybody, before they popped in from your perspective and you popped in from their perspective. You could cover it up with a lens flare or something.)

Of course, people would then gyrate back and forth across zone/room thresholds as a way of protecting themselves, which seems obnoxious, but also seems like a very easy behavior for the server to detect and punish.

Re:EA is permanently banning Linux players on Battlefield V by Izkata on Friday January 03, 2020 @01:58PM (#21949093)
The top-down MMOs I've played have line-of-sight fog-of-war while in caves/buildings (with limited range smaller than the screen in caves), which has the same issue. The clients have access to invisible things so they can accurately predict when they move - including when they become visible - and correct a split second later if the prediction was wrong.
Re:EA is permanently banning Linux players on Battlefield V by vel0city on Wednesday January 08, 2020 @12:38PM (#21993721)
This is already how some first-person shooters work, notably Counterstrike. Maps are segmented into areas and you only get updates for things happening in the local area. This has actually been a source of bugs, where a grenade going off near the area never gets its sound transmitted to people in the area next to it as to those clients that grenade was never thrown.
Re:EA is permanently banning Linux players on Battlefield V by arminiusreturns on Saturday January 04, 2020 @12:37AM (#21953108)
Funny enough this was actually an issue in the earlier days of a hardcore bigworld MMO I used to play called Mortal Online. Reds (gankers) would hang out near the boundaries and pop in out of nowhere. This was largely more of an engine limitation of UE3 as I understand it, and was eventually mostly worked around. Now many of the UE3 painpoints are softened with UE4 they have started Mortal Online II.
Re:EA is permanently banning Linux players on Battlefield V by derefr on Friday January 03, 2020 @01:22PM (#21948721)
> Pre-rendering the scenes on the server and then sending those is just not really possible today due to latency -- even google can't get it right with Stadia so far.

Ah, but Stadia (and Playstation Now, and Geforce Now) are trying to solve a different problem: moving all the compute to the cloud, so that the game console can be wimpy (or of a different/incompatible architecture, in PSNow's case.)

If you remove that requirement—or rather, impose the requirement that the client hardware must be just as powerful as if it were running a full game—then you can do something clever by splitting the game not into "renderer on the server, frame buffer on the client" but rather into "game and projection matrix on the server; display-list renderer on the client."

In other words, the server (or per-client server-side agent) would be responsible for doing all the evaluation of local physics (e.g. soft-body dynamics, constraint-resolution during rigging, etc.), lighting calculation, and all the other stuff that currently requires the client to "know stuff" about the world; and then it'd output to the client, on each tick, just a display-list—a bunch of loaded-model references, their positions in space and the positions of their rigged limbs, and the reflected-light amount on each of their polys; any temporary particles that exist for that frame, and their positions; etc. This would all be culled down to a virtual viewport.

The job of the client would then just be to receive this display-list, each frame, and draw it. It would also perhaps be responsible for doing client-side visual lerps between server ticks. (Probably each rigged limb would be annotated with linear+angular velocity properties.)

In other words, this would be a recapitulation of the X11 protocol, but where the primitives are 3D objects rather than 2D ones. (It'd kind of look like the protocol between games and OS display drivers, but at the same time higher-level in some ways and lower-level in others.)

This would be highly bandwidth-efficient (and jitter-tolerant!) compared to what Stadia is doing. You'd probably be able to play a decent game through this on 3G, even. But you'd need a computer that could do the final rendering passes.

Re:EA is permanently banning Linux players on Battlefield V by AndrewStephens on Friday January 03, 2020 @01:37PM (#21948871)
Interesting idea that might work well for simpler games but what you call display lists on today's games can be very large. Modern video codecs are also very good, so the trade off is not as obvious as you make it seem.

And even then it wouldn't stop cheating. Bots would just look for triangles drawn with enemy uniform textures (very easy if you have the display lists) and aim at them.

Re:EA is permanently banning Linux players on Battlefield V by derefr on Friday January 03, 2020 @01:46PM (#21948959)
> Bots would just look for triangles drawn with enemy uniform textures (very easy if you have the display lists) and aim at them.

I think you missed the "viewport culling" step in the above description. The server would only be sending the client enough information to draw what's going to be on the client's screen (since that's the only information that's naturally left after that step of the rendering pipeline!) So, on any frame where another player is obscured by a wall, data about that player wouldn't be in the display-list sent to the client, any more than it would be in the image Stadia sends.

Re:EA is permanently banning Linux players on Battlefield V by AndrewStephens on Friday January 03, 2020 @02:00PM (#21949119)
And the during the first frame where the tiniest sliver of the enemy is visible around the edge of the wall, the bot running on the local computer will move the crosshair exactly over the visible area and shot.

This is ignoring things like player shadows which are rendered separately and need polygons which are not in the visible fulcrum.

Also we are both ignoring audio. Sounds like gunshots come from a specific place in the world.

Re:EA is permanently banning Linux players on Battlefield V by derefr on Friday January 03, 2020 @04:03PM (#21950336)
> And the during the first frame where the tiniest sliver of the enemy is visible around the edge of the wall, the bot running on the local computer will move the crosshair exactly over the visible area and shot.

Well, yes, but I'd categorize that as "acts indistinguishable from theoretically-optimal human performance", rather than cheating per se. Or would you ban The Flash for cheating?

> This is ignoring things like player shadows which are rendered separately and need polygons which are not in the visible fulcrum.

No, not really; a shadow mesh is generated on the server, as part of the lighting step. The client then receives the shadow mesh, potentially disconnected from whatever's casting the shadow if the thing casting the shadow was culled. Just like what happens inside your GPU.

> Sounds like gunshots come from a specific place in the world.

In a paradigm like this, audio-cue triggers would essentially be "scripted particles" in the scene. If you can't see them, they're not rendered, so you can't hear them, either.

I'm not trying to describe something here that's a lossless approximation of how the game would work if run locally. I'm describing something with real effects on gameplay balance, but potentially good ones.

Mind you, I'm less picturing FPS games as the best use of this, and more picturing RTS games. Take the "fog of war" of a game like Starcraft, and implement it server-side, such that it's not the client not-rendering unexplored stuff, but the server.

Re:EA is permanently banning Linux players on Battlefield V by AndrewStephens on Friday January 03, 2020 @04:39PM (#21950666)
Counterstrike aimbots have done what I describe for decades. They can aim and shoot in one frame, then aim and shoot at someone else as soon as the gun animation allows, exactly like playing against The Flash. The Flash might not be cheating per se, but he would be unsatisfying to play against as he decimates your entire team in a second.

Shadow meshes are often generated by rendering the scenes from the viewpoint of the light sources. This would have to be done on the server, so the server is already doing some rendering.

Sounds certainly need to be rendered, even for non-visible players. Otherwise you couldn't hear someone shooting behind you.

You ideas would work much better with a RTS. But so do solutions like Stadia.

Re:EA is permanently banning Linux players on Battlefield V by jimmydorry on Friday January 03, 2020 @03:57PM (#21950280)
Dota2 (more accurately the source2 engine) already does this. The cheats are then limited to acting on things at bot speeds instead of at human reaction speeds.
Re:EA is permanently banning Linux players on Battlefield V by derefr on Friday January 03, 2020 @04:37PM (#21950643)
That's cool! Is there a deep dive somewhere into the architecture of Source2 (or any game built with it) that you'd recommend?
Re:EA is permanently banning Linux players on Battlefield V by EamonnMR on Friday January 03, 2020 @12:17PM (#21947957)
I think what the parent means is that if a player is behind a wall, don't send that player's position at all. Of course you could still have a hack which, say, visualizes sound origins.
Re:EA is permanently banning Linux players on Battlefield V by mottosso on Friday January 03, 2020 @12:23PM (#21948031)
Unless the server truly sent only what the user is meant to see - i.e. video; no hacks can reveal more than what's in a grid of pixels.
Re:EA is permanently banning Linux players on Battlefield V by zttxc on Friday January 03, 2020 @12:37PM (#21948197)
You can't replace the graphics driver in Windows unless you boot in test mode, and some games like Fortnite will refuse to run if the system is booted in test mode.
Re:EA is permanently banning Linux players on Battlefield V by nkrisc on Friday January 03, 2020 @01:14PM (#21948633)
Transparent walls wouldn't help if the client wasn't even informed at all of players that were behind it.