@STARRYSOCK said:
If SD has the framework to detect someone who repeatedly partied with an obvious cheater, sure.
Once a cheater has been exposed, it should be a simple database query to show players that participated with him a certain amount or percentage of games.
However, for not so obvious cheats like temporarily activated aim assists or wall hacks it’s hard to tell if someone was aware that a player in your team was cheating. And even if, it does not mean that the cheat was used in every game they played together.
Sure, you can filter matches where the cheater was actually reported and the other player did not support a votekick. Provided your data model supports all this, it’s still a fairly simple database query.
But it does not proof that in all these games an obvious cheat was used. To ensure that, SD support would have to go through a larger amount of previous games and mark the cheater as obvious or not. Which is a lot more time consuming than just checking a single game and banning an obvious cheater.
So I don’t think this is viable from a labor cost point of view.