-
16th January 2015
Post #1
November 2014
18 Posts
i was playing the game earlier, it froze and after restarting my computer i'm now unable to join a server for more than a couple seconds. get this error in the console "disconnected: EAC: Unconnected" I know this happens alot when an updates comes out, but i've never heard of it happening out of the blue like this before, any potential fixes any1 might know of ?
-
16th January 2015
Post #2
RustEssentials Staff
February 2014
460 Posts
I do know that EAC runs as a service, so you could check the service in your PC, it may not have started correctly.
go to run and type in services.msc, i think the service name starts with EAC so shouldn't be too hard to find (going of memory), does it have a status of started? If not you may be able to restart it.
Other than that I am not sure what else you could do sorry to say.
-
16th January 2015
Post #3
May 2014
561 Posts
you should check to see if your Rust game has been set to update even when your playing it, you have to check the Steam menu options for Rust to see if it has or not, though im not sure if it affects the game but i wouldn't be surprised if it does. Otherwise you might need to wait to an update to see if it fixes it or try validating your game cache.
-
16th January 2015
Post #4
November 2014
18 Posts
i'm on a mac, (probably should have mentioned that earlier) and i can't seem to locate any EAC files. i changed the update options as well as went over to the dev branch and opted back to the main again, didn't do anything. i am able to play in the dev branch though and the plots thickened a little further, i'm now able to join official servers on the main branch but not the community ones, which kinda sucks because i was playing in a community server and was doing rather well for myself lol. i appreciate the suggestions. i guess i'll have to go start from scratch in an official server and hope it doesn't kick me after doing 6 hours of farming preparing for a night of pvping again lol
-
16th January 2015
Post #5
November 2014
18 Posts
update: this mornings client update apears to have completely fixed the problem :)