I have this situation, running SCUM after hotfix v9.601, which apparently has integrated an EasyAntiCheat policy… I also sometimes run Microsoft Visual Studio, for professional reasons, as well as a SCUM WhalleyBot API based feature enhancement. But also mainly for professional career reasons (Visual Studio). EAC is falsely identifying, Visual Studio and blocking entry into SCUM. So my question is this: WHY?! And how can I configure EAC to not clamp me out of 1) my professional goals, 2) in game immersion, enjoyment, etc. Thank you…
So to be hundred percent clear, things were "fine prior to SCUM 9.601. Then 9.601 broke EAC integration, blocks for Visual Studio devenv presumably, having been detected. 9.602 seems to have “resolved” that integration policy. Then broken again 9.603; and here we are, AGAIN, 9.605 (Christmas update).
Kindly do work with your SCUM integration partners to successfully resolve: DO NOT BLOCK ON VISUAL STUDIO!
It would be one thing if you might detect devenv, or its debugging tools, attaching to SCUM process; as an integration policy matter. That is one thing. But for the simple existence of devenv, NO NO NO. That’s a massively inappropriate broad brush to be painting with, IMO.
Best, and thank you!