Blake2394 Posted January 2, 2016 Report Share Posted January 2, 2016 Hello Everyone! After updating Arma to the latest patch, some of my players are getting kicked for (RemoteExec Restriction #0) and when I look in the remoteexec.txt all I see is (02.01.2016 15:22:33: AuTel (75.135.1.33:2002) **GUID** - #0 ""). What could be causing this? Out of date filters? I am running the latest version of infistar. Thanks, Blake2394 Link to comment Share on other sites More sharing options...
Blake2394 Posted January 3, 2016 Author Report Share Posted January 3, 2016 bump. Anyone? lol. Link to comment Share on other sites More sharing options...
theduke Posted January 4, 2016 Report Share Posted January 4, 2016 tell them to revert the update. there is probly a mod you have or something they are doing at that very moment that the corepatch team has changed, like a core variable that is causing that. I explain how to revert it here http://epochmod.com/forum/index.php?/topic/40560-problem-with-manual-dl-dayz-launcher/&do=findComment&comment=270317 Link to comment Share on other sites More sharing options...
Blake2394 Posted January 4, 2016 Author Report Share Posted January 4, 2016 2 hours ago, theduke said: tell them to revert the update. there is probly a mod you have or something they are doing at that very moment that the corepatch team has changed, like a core variable that is causing that. I explain how to revert it here http://epochmod.com/forum/index.php?/topic/40560-problem-with-manual-dl-dayz-launcher/&do=findComment&comment=270317 Hi theduke! Thanks for the reply! I host the server myself on a dedibox so how would I do that using SteamCMD? Is that possible? Thanks, Blake2394 Link to comment Share on other sites More sharing options...
theduke Posted January 4, 2016 Report Share Posted January 4, 2016 Im on a dedi also, but my server files are not automatically updated. I copied the files from the arma folders to a new folder i created on the desktop. So for me the server files havnt been updated. There is too much that went wrong in the corepatch im not taking the chances till the epoch devs can figure out the mess the behemia corepatch team did... as for the steam CMD i dont know. If you server files have been update then maybe thats why you are getting that error. As my server isnt updated, just the client Link to comment Share on other sites More sharing options...
Blake2394 Posted January 5, 2016 Author Report Share Posted January 5, 2016 21 hours ago, theduke said: Im on a dedi also, but my server files are not automatically updated. I copied the files from the arma folders to a new folder i created on the desktop. So for me the server files havnt been updated. There is too much that went wrong in the corepatch im not taking the chances till the epoch devs can figure out the mess the behemia corepatch team did... as for the steam CMD i dont know. If you server files have been update then maybe thats why you are getting that error. As my server isnt updated, just the client Hi! Thanks for all your help. I used the steam client to download the legacy version of Arma and it looks like its back to working! Thanks Again, Blake2394 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now