|
|
|
|
|
by rollcat
214 days ago
|
|
Oh that's interesting! I've never played Rust (or any PvP shooter outside of Quake 3...), so forgive me my ignorance. Questions, out of curiosity: - Why no matchmaking, why no win/loss condition? What's the incentive structure / stakes for the participants? Is that a differentiator in the genre? - Other than raw mechanics (aiming), what other kinds of skillsets affect gameplay / success? - What are you allowed to share about the mitigations? I don't wanna try any further backseating, just curious. |
|
Other than aiming there's just game and map awareness, including understanding the current meta. Base design is a whole other area relevant to defending against raiding while you aren't online or away from your base.
We use EAC but also have our own layers of protection. We do some of our own anti-tampering in the client, a player reporting system with staff to investigate, server-side antihack to guard against all kinds of weird state modified clients send, and a lot of data collection+analysis. If you look up Rust or any other popular FPS game up you'll see it's still not enough.
The most effective anticheat tool really is game design. Games can be designed to limit or even eliminate the worst of cheating... but only by significantly changing the games. It'd be simple if everything was like the Civilization games because they're turn based and have well-defined actions. All input can be 100% verified without the need for tolerances and hidden state (fog of war) can be networked only when necessary.