PetuniaEpoch Posted December 2, 2014 Report Share Posted December 2, 2014 So... all was working, then I updated to the latest client files (0.2.5.1) and now ALL players get kicked with the message: 02.12.2014 18:04:16: (name)((IP):(port)) (SteamID)- #0 "PLAYER_REJECT_NotReady2" = true I obviously swapped the private data out - but that error is for all.All I've done is update the client files... did I do something wrong :( - I updated battleye files too - but should I have updated the server files>?EDIT - in my server files I checked the version, it does say this - is the client/server out of date to each other?---class CfgPatches {class A3_server_settings {units[] = {};weapons[] = {};requiredVersion = 0.1;epochVersion = "0.2.5";===(its 0.2.5 not 0.2.5.1? Link to comment Share on other sites More sharing options...
mimic Posted December 2, 2014 Report Share Posted December 2, 2014 Both server and client files need to be updated to the new version. 0.2.5.1 When updating the server files just replace the server .pbo files, and the mission .pbo files. Everything else can stay the same. Link to comment Share on other sites More sharing options...
PetuniaEpoch Posted December 2, 2014 Author Report Share Posted December 2, 2014 Thanks for the reply... Odd though - when I download from here: http://epochmod.com/download_server.phpand extract the settings pbo, it seesm to say version 0.2.5 - not 0.2.5.1? Am I doing something stupid? LoLBoth server and client files need to be updated to the new version. 0.2.5.1 When updating the server files just replace the server .pbo files, and the mission .pbo files. Everything else can stay the same. Link to comment Share on other sites More sharing options...
Remix Posted December 2, 2014 Report Share Posted December 2, 2014 im getting this 2 reloged fixed it for me tho Link to comment Share on other sites More sharing options...
nedfox Posted December 2, 2014 Report Share Posted December 2, 2014 That string is in config.cfg , edit it. Link to comment Share on other sites More sharing options...
PetuniaEpoch Posted December 2, 2014 Author Report Share Posted December 2, 2014 Okay this is sorted - anohter problem now though - runtime error! will make a new post Link to comment Share on other sites More sharing options...
GreenXtc Posted December 5, 2014 Report Share Posted December 5, 2014 I have the same problem but the error is: #0 "PLAYER_REJECT_NotReady1" = true What's the solution ? Link to comment Share on other sites More sharing options...
drsubo Posted December 11, 2014 Report Share Posted December 11, 2014 same here I have to relog and go back in to get on server, every time Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now