new-world Updated With Official Statement. WARNING: Most Recent Steam Update Makes New World Unplayable + Possible Fix

[Starym 3,800]

 

Update 2: We now have an official response from Amazon Games on the issue, and it's basically the same as below, verify game files or re-install Easy Anti-Cheat. You can read the full statement here.

Update: Easy Anti-Cheat may have been updated, which should fix the issue entirely. If it doesn't auto-update for you (after a Steam and NW restart), you can try either repairing the EAC installation from its folder or running its setup again from the New World folder. The process also might require a reboot. Players are also reporting simply verifying the New World files worked for some of them as well.

(Clarification: This isn't just a New World issue, as many other Steam games are being affected by the Easy Anti-Cheat issues.)

_______________________________________

Original post:

Here's a big warning for all you New World players  that haven't updated your Steam client today: DON'T! Apparently an interaction between the latest Steam update and Easy Anti-Cheat is making New World unplayable, as players can't enter the game, getting these errors:

  
Source: WampM.

Players who haven't updated their Steam client are completely unaffected and are playing normally and there seems to be a workaround, but we can't guarantee it's 100% safe or working correctly. However there are multiple reports of it helping/making the game run and it comes from New World forum user vinidamazza (via redditor SaltyiiBanana) :

I was able to resolve the error by taking the following steps: Download the steamclient64.dll 831 file Place the file inside the Steam folder (default location is C:/Program Files (x86)/Steam) To prevent Steam from trying to update itself, it will be necessary to create the Steam.cfg 340 file with the following content: BootStrapperInhibitAll=Enable Open the game and enjoy Aeternum xD Thanks @guidamazza for the steamclient64.dll #Edit edit to put virus scan: VirusTotal 92

This seems like one of those errors that will be fixed very soon, but it's already here for over an hour, and considering the very recent queue troubles any amount of time lost will be doubly frustrating, so let's hope the above solution works and/or there's a fix for the situation on the Steam/Easy Anti-Cheat side as well.

[Amorandra 7]

there's some serious game breaking gliches in this game, this is the first mmo i've been in thats this early in the lifespan but I feel alot of them should have been fixed before release...

[Sabejnos 10]

1 hour ago, Amorandra said:

there's some serious game breaking gliches in this game, this is the first mmo i've been in thats this early in the lifespan but I feel alot of them should have been fixed before release...

It's still good compare to ANY Blizzard's patch. 

[Slam 40]

3 hours ago, Sabejnos said:

It's still good compare to ANY Blizzard's patch. 

That level of bitterness 😄

I'm working as dev for non gaming stuff, it is hard to test everything and get it non buggy with the small apps I produce so I can't imagine for massive games like this.

I'm not saying they couldn't do better but that sadly how development has evolved and got more complex, it's not realistic anymore.

 

Games 20y ago were 5k-10k lines of code maybe, compared to now with millions! 

[LeCrom 0]

I have this very error since closed beta, then open beta and even in the released game it is there. No way to fix it. In my case it shows sensapi.dll as the untrusted file, but I can neither repair nor replace it. Clue anyone?

Otherwise I will have to return the game within this week with zero minutes played.