Easy Anti cheat bootstrapper has stopped working? [4:05 PM] Only game im having easy anti cheat issues with?

[Scraf]

Easy Anti cheat bootstrapper has stopped working?
[4:05 PM]
Only game im having easy anti cheat issues with?

[Yoshiro]

Have you tried a re-install/repair of EAC

[KMickle]

I've been having EAC malfunctions since today. It fires mid-wait in a lobby, some 30 seconds before the match. Redeploying EAC won't fix it.

upd. (!): related (Linux):
https://forums.tripwireinteractive.com/index.php?threads/eac-problems-linux.2340153/

upd.: might be related: https://steamcommunity.com/app/820520/discussions/0/6733519464636572367/

upd.: related:
https://steamcommunity.com/app/820520/discussions/0/4030223299344696724/
https://steamcommunity.com/app/820520/discussions/0/3812910932504216705/
https://steamcommunity.com/app/820520/discussions/0/3833171151459071369/
https://steamcommunity.com/app/820520/discussions/0/3874841497808194890/

...upd.: it's not bootstrapper, though. I think it didn't work either, some 10 days ago. But I just installed EAC manually via a script in the game folder, and that did the trick

[KMickle]

1. I've fixed the problem by *completely* deleting and reinstalling the game. Just verifying game files in Steam and reinstalling the EAC did not help;
2. EAC bootstrapper is most certainly not working. After I deleted and installed Deceive in Steam, I had to install EAC by hand.

[KMickle]

The EAC problem reappeared 1-2 days after. Here is what I've done:
1. Delete the EAC-related files from the game directory:
2. Delete the EAC cache from `AppData\Roaming`;
3. Rescan the game files;
4. Reinstall EAC via the script in the game directory;
5. Reboot the system.

The game is now passing the EAC checks again. Let's see for how long
*Rem.: I'm not sure what of the above really solved the problem, nor whether this was a complete coincidence*

[KMickle]

It became worse. Nothing helps any more, even a full clean reinstall.
Search results on the Internet basically reveal other Deceive players having the same problem and the developers saying they'd look into it.

I've updated the link list on my first post to refer to these materials.

[KMickle]

[currently broken beyond my repair ability; spend 2 hours looking through potential solutions and mentions on the Internet; dropping this idea untif further news]

[Scraf]

Ursprünglich geschrieben von KMickle:

[currently broken beyond my repair ability; spend 2 hours looking through potential solutions and mentions on the Internet; dropping this idea untif further news]

Glad im not the only one and you seem alot smarter than me, if you cant fix it then im screwed xD

[KMickle]

Well, we're definitely not supposed to (be able to) fix this.

Firstly, it's not our Operating Systems, as it appeared both on Linux and on Windows (see the link above);
Secondly, the culprit is either Deceive or Easy AntiCheat, as these problems seem to appear at the same time. Several days ago, and once before that, some time in 2023.

If that's Deceive, — they've probably forgotten to update something in the distribution. This might make some/new/all installs to fail on some condition. If that's Easy AntiCheat, — they've gone too agressive and started banning legit environments.

There is one certain thing, though: the blame is 100% on the programmers (at least one side, may be both). If you come to a restaurant, place an order. Then, after a 30 minute wait, the waiter comes up and hits you with a wooden oar shouting "Food Error!", what would you think of the institution?

Then the reason turns out to be you paid with a 100¤ bill, and they didn't have 5¤ coins to pay you the change, so you're noncompliant and basically to blame. It could also be an unproper outfit. Coming outside of working hours. Raw ingredient shortage. Some kitchen incident. A typo in the tab. You name it.

The worst part is: if the Deceive developers are getting the Food Error from Easy AntiCheat, that'd be extremely hard for them to repair, as... you know: no idea, what's really happening.

The bottomline: the developer who typed in the 'EAC Validation Failed' string is definitely the one to blame in the current situation, and deserves their arse delivered to 'em :-)

*rem.: just checked again, still fails. Shall attempt an update and report back if something new emerges*

[KMickle]

Upd.: It has been working perfectly fine for the last several days: just started working, I didn't do anything, didn't attempt repairs. It just logged in as miraculously as it had failed the day before.

There is only one clue that could help. My sister plays on the same subnet as me, and the problem disappeared roughly the same time she successfully logged in after a brief absence. I'm positive we're sharing the same IP, so the EAC service could have confused our 2 PCs for one.

I lack any insight into how EAC actually operates (and any wish to help develop this ware as well), but I'm leaving this information here just in case the developers on either side need it.

[Scraf]

Ursprünglich geschrieben von KMickle:

Upd.: It has been working perfectly fine for the last several days: just started working, I didn't do anything, didn't attempt repairs. It just logged in as miraculously as it had failed the day before.

There is only one clue that could help. My sister plays on the same subnet as me, and the problem disappeared roughly the same time she successfully logged in after a brief absence. I'm positive we're sharing the same IP, so the EAC service could have confused our 2 PCs for one.

I lack any insight into how EAC actually operates (and any wish to help develop this ware as well), but I'm leaving this information here just in case the developers on either side need it.

thanks buddy, ill check it