CS:GO is usually in the top 3 of most popular games on steam. Last time I checked, it was number 1. I would be surprised if Battlefield V has a quarter of the amount of players (across all platforms) versus CS:GO (which is just on PC).
I am not trying to make excuses for EA (Which has been nothing but a trash fire of a company for the last few years), but how could they justify putting those kind of resources behind a game like BFV?
Doing nothing, or doing the wrong thing has atrocious effects on the community. Just read some of the other threads in this post. Seasoned players who wait weeks for flagrant cheaters to be removed. It kills a game quickly.
Maybe that's actually what EA wants.
It does slightly come down to what sort of multiplayer experience you want. Budget in the temporary archiving of ranking multiplayer games. Sell it as a feature. It'll keep the whole thing ticking over a lot longer.
The review cost is nothing. Really. Communities love to self-police so giving them the tools to do it completely, or to a point where they can identify flagrant cheaters for paid mods to verify... It's the Stack Overflow model. It works.
Logging a rolling week's activity at that higher rate requires 53GB but you could dramatically reduce the burden by only keeping things with in-game reports and then deleting recordings after the last issue was dealt with.
My point is it's not nothing, but it's nothing by modern standards if you've got more than two brain cells to rub together.
If you only record player input: mouse movement, clicks and keystrokes, it should be much lower.
Technically you could record only the players' inputs but to play back such a recording, you would then have to deterministically reconstruct the entire match from all players' inputs. That's a bit more complicated than just replaying the local part of the simulation that your client already does with what data the server sends to players during normal course of gameplay.
oliwarner's numbers amount to about 45 bytes per frame per player, which is not unreasonable.
As I said, it's not nothing, but it's not bad.
Presumably to fulfill their end of their transactions? It’s not like the game is free; presumably you’re paying for something.
It also doesn’t launch on Linux for the same reason. Is at least a touch more user friendly than getting bans I guess.
To be honest, other than having better communication on the issue, I'm not sure how I'd handle this one differently than EA...
Some information in this talk: https://www.youtube.com/watch?v=ObhK8lUfIlc
That's literally wrong, the gameplay you see in OW is not based on recorded inputs of the player's client. You are watching a demo recorded by the server, which does not match the PoV of the player precisely. The demos are also 32 tick, which makes it hard to tell if the aiming of the player is legit [1], unless they are very blatant about it. Due to interpolation and lag compensation the PoV that the player saw is not what you see in the server's demo. If you record the player's PoV using screen capture and compare it to the demo recorded by the server, there are subtle and sometimes relevant differences.
tl;dr OW is only there to catch obvious cheaters.
[1] Because the server runs at 64 tick, but the demo is only 32, the crosshair snaps every time a shot is taken. The aim of everyone looks way snappier and suspicious in a 32 tick demo compared to their PoV.
It was a slight simplification. You send your input to the server. Yes, filtered. Yes, not 1000Hz. But essentially what the client was doing. You could increase the resolution here but again, who's paying for it? I do agree that the rebuilt context is what the server saw, not what the user saw after network and screen latency, but we're talking about behavioural analysis.
And that's where I think you're flat out wrong. One kill could be a suspiciously-tracked headshot. But systems like this can compile hundreds of kills over dozens of matches from a single user. Its volume builds an accurate picture about whether a user is a cheater or not.
And it's a country mile better than games that have no repercussions for cheaters where the cheats haven't been detected by Gaming's answer to Norton AntiVirus 2003. Because zero-days still get by those.
(Edit: I'll also use my edit window to add that many servers run a lot faster than 64 - just as you can record at any speed you like - by Overwatch may be locked lower for disk space reasons)
> And that's where I think you're flat out wrong. One kill could be a suspiciously-tracked headshot. But systems like this can compile hundreds of kills over dozens of matches from a single user. Its volume builds an accurate picture about whether a user is a cheater or not.
I don't know what OW does behind the scenes. But you and I as "OW investigators" only get to see ~eight rounds of gameplay with no rewind button and make a "beyond reasonable doubt? Yes/No" decision.
I stand by what I said - OW is to catch obvious cheaters, not people who cheat subtly.
> (Edit: I'll also use my edit window to add that many servers run a lot faster than 64 - just as you can record at any speed you like - by Overwatch may be locked lower for disk space reasons)
Overwatch only applies to Valve MM (which is 64 tick); community servers and non-MM game modes are not subject to OW.
Not particularly correct. It only works for official matchmaking, because you will have your match game demo stored on Valve's server, for future reference to you maybe. Valve simply took advantage to replay these demo by allowing volunteering moderators to access the private demo and hiding the names of the others (but actually these name & steamid are accessable through cheat client); it does not record precise movement, as part of the engine limits, demos are sampled in 16 ticks, or 16fps that sometimes even creates wrong artifacts that misjudged people. You can see that in some pro CSGO matches there are some fishy kills but in fact thats due to 128 ticks -> 16 ticks illusions
Seems EA is doing —like a lot of very lazy anti-cheats— balls-simple stack inspection. They determine whether people are cheating by looking for known signed drivers, known hardware, known bad processes and input drivers. It's cheap and scales well but it's brainless. They have to know about a hack to detect it in the future. Version checks are constantly slackened off because legitimate updates come out all the time.
Battlefield is seeing Wine and the drivers Wine reports (which are a mix of real and fake) and baulking out. It's to be expected from such plastic anti-cheat software. Many games do this.
There are better options.
CSGO's overwatch allows the community to self-moderate by replaying a player's gameplay. They literally record the player's input and rebuild what the player could see in the reviewer's client. Reviewer determines whether or not their gameplay was possible. It sounds hardcore but it's simple, and adds no latency because it's done after-the-fact. Makes it super-simple to detect most wall-hacks and aim helpers.
So why isn't it everywhere? Logging data costs money. And EA, for all their moneybags are cheapskates.
And you could automate this. You could do a server-side render to determine whether or not a user is tracking players that are not physically visible to the player, or tracking impossibly tight hitboxes, or is triggering massive killcounts far too regularly (ie exploiting a bug). But that's more money.
But I'd expect a better response shouting into the wind than asking EA to be better. They're a trash company.