Scripts.txt kicks everybody for no legit reason

[Bryce23 10]

Hey all,

I am having some issues with BattlEye. After I saw the post about the new scripts.txt, I went and downloaded it and installed it properly on my server. After installing it, BattlEye kicks every single player the instant BE initializes no matter what mission we are playing. I looked in the scripts.log and there are thousands of lines. As reasons for the kicks, it says huge random numbers like #20 "0.78539816339744830961f", it also lists arma scripts like "ca\ui\scripts\ui_loadingText.sqf" and hundreds more. It seems that the scripts.txt is detecting every single thing possible and kicking for it. We use a watered down version of the scripts.txt because we do not play DayZ and half of the default restrictions are known to kick legitimate players on vanilla servers. We are running the newest version of BE

Does anyone know how I can fix my scripts.txt so it only kicks players for things that I have actually restricted instead of kicking for thousands of random reasons? Nobody is able to play on my server if I have the scripts.txt enabled. I disabled it until it's fixed, but I would like to re-enable it after it's fixed so I can have the extra protection against players who want to do "silly" things. :rolleyes:

Thanks

A few of the thousands of scripts.log entries:

16.08.2012 02:33:45: Mike (IP Address) GUID - #15 "#line 1 "ca\ui\scripts\ui_loadingText.sqf"

16.08.2012 02:13:46: Joe (IP Address) GUID - #18 "SafeZoneX + 0.26"

16.08.2012 02:15:19: Jeff (IP Address) GUID - #15 "0.78539816339744830961f"

Edited August 16, 2012 by Bryce23

[.kju 3244]

a) where did you get the scripts.txt from?

b) post a link to the file you use

[Bryce23 10]

I got the scripts.txt from here: http://dl.dropbox.com/u/18463425/DayZserver/scripts.txt and I then removed everything that can be used for a purpose outside of a hack. My scripts.txt then had about 20 restrictions, and then I added about 5 or so more scripts that I am aware of that can only be used for malicious purposes.

I also tried to delete every restriction except that troopmon restriction that comes with it just to test. And it still kicked every player right as BE initialized. It's also worth noting that I had none of these issues before BE updated the scripts.txt. For about a month it continuously renamed my scripts.txt to scripts_old.txt causing it to be of no use. Now I am using the exact same restrictions as I did when it was working properly, except it now kicks every player instantly.

[.kju 3244]

So probably your current scripts.txt is "faulty" - why not post it, so that people can review it?

[Bryce23 10]

Please check your PM's