Jump to content
  • 0

Problems on new Private Server setup (Battleye)


legato

Question

We're finally leaving Dayz.st for a dedicated box.  But having some major issues with Battleye kicks that may be indicative of a more major issue, but I'm just not sure.  Hopefully someone here can help.  Here's the scripts.log:

 

18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #171 "rcallVarcode={diag_log("WARNING illegal RE rcallVarcode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #107 "rclearMagazineCargocode={diag_log("WARNING illegal RE rclearMagazineCargocode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #109 "rclearWeaponCargocode={diag_log("WARNING illegal RE rclearWeaponCargocode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #14 "rcreateMarkerLocalcode={diag_log("WARNING illegal RE rcreateMarkerLocalcode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #16 "rcreateSimpleTaskcode={diag_log("WARNING illegal RE rcreateSimpleTaskcode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #23 "renablesimulationcode={diag_log("WARNING illegal RE renablesimulationcode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #131 "rexecfsmcode={diag_log("WARNING illegal RE rexecfsmcode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #103 "rhideObjectcode={diag_log("WARNING illegal RE rhideObjectcode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #140 "rremoveAllWeaponscode={diag_log("WARNING illegal RE rremoveAllWeaponscode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #106 "rsetCaptivecode={diag_log("WARNING illegal RE rsetCaptivecode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #39 "rsetCurrentTaskcode={diag_log("WARNING illegal RE rsetCurrentTaskcode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #39 "rsetCurrentTaskArrayscode={diag_log("WARNING illegal RE rsetCurrentTaskArrayscode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #42 "rsetDatecode={diag_log("WARNING illegal RE rsetDatecode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #200 "rsetTaskStatecode={diag_log("WARNING illegal RE rsetTaskStatecode with args:"+str(_this));};"
18.07.2013 21:17:25: XXXXX (192.168.3.10:2304) ce533f6a73175cf4945ffaeb986dc1ea - #87 "rskiptimecode={diag_log("WARNING illegal RE rskiptimecode with args:"+str(_this));};"

The X's are my buddy's username, I just removed it.

 
We got kicked first for 171, then 42, and by the time 87 happened I had to start wondering what the heck is going on.  All server files are current, including Battleye.
 
Those warnings caught my eye but I'm not sure what the issue is.
 
 
Edit:  Alright, it's this file: REsec.sqf.  I'm not sure what it's supposed to be doing, but I commented it out.  Running fine now.
Link to comment
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement
  • Discord

×
×
  • Create New...