hohlraum

Anyone know if there is a scripts/remoteexec.txt entry that can detect players warping vehicles around the map? We had someone do it last night while I was in the vehicle. absolutely nothing in the scripts/remoteexec.log files when it happened.

We had no less than 10 individuals using the TWS tonight on our server. It's become a bit of an epidemic. I now have a message that shows every 5 minutes on the server that reminds people about the TWS.

GreyEcho, Have you considered having your software have a built in list of log entries it checks for? That way people can keep the DCBL filters updated regularly but your software only bans for specific log entries? The way I understand your software works is that it completely removes certain entries from the DCBL filters so they don't kick or log. Then you rely on kicking/banning based on whatever shows up in the logs? EDIT: Reading the source it already appears that you are doing this for createvehicle.log entries. Which makes me wonder why you need custom filters for your software? kicking players based on the standard DCBL filters is pretty minor compared to banning them permanently.

I've been seeing a few of these: "if (name vehicle player == TTT5NamePl) then {_xcompiled = compile TTT5derCode;call _xcompiled;};" Anyone know what these people are doing? Is that something with thunderdome?

On the BIS forums Dwarden says to ban for anything that shows up in the remoteexec.log.

Does the software pull the newest remoteexec and createvehicle files from the dayz community ban list on a regular basis or only use the versions you include with each distribution?

And we're 100% sure on this when these show up in the remoteexec? Seeing a lot of them recently. I submitted the log file. How are other admins integrating the community ban list into their existing ban files? Does BE have some facility for "including" a secondary read-only ban file?

19.08.2012 11:57:12: [»©Я«] The End (:2304) - #0 " if (isServer) then { _dsasadsa = createVehicle ['S1203_TK_CIV_EP1', [4898.79, 2291.6, 0], [], 0, 'CAN_COLLIDE']; _dsasadsa setVariable ['ObjectID', 5602.6, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _dsasadsa]; _uid = _dsasa" 19.08.2012 11:57:12: [»©Я«] The End (:2304) - #3 " if (isServer) then { _dsasadsa = createVehicle ['S1203_TK_CIV_EP1', [4898.79, 2291.6, 0], [], 0, 'CAN_COLLIDE']; _dsasadsa setVariable ['ObjectID', 5602.6, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _dsasadsa]; _uid = _dsasa" 19.08.2012 13:12:54: Dylan Coe (:2304) - #0 " if (isServer) then { _object = createVehicle ['PBX', [11644.8, 3413.89, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 9654.21, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objectUID" 19.08.2012 13:12:54: Dylan Coe (:2304) - #3 " if (isServer) then { _object = createVehicle ['PBX', [11644.8, 3413.89, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 9654.21, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objectUID" 19.08.2012 13:16:41: Dylan Coe (:2304) - #0 " if (isServer) then { _object = createVehicle ['S1203_TK_CIV_EP1', [11647.6, 3408.86, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 6373.26, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call d" 19.08.2012 13:16:41: Dylan Coe (:2304) - #3 " if (isServer) then { _object = createVehicle ['S1203_TK_CIV_EP1', [11647.6, 3408.86, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 6373.26, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call d" Any idea what is going on here? These guys actually spawning these things or just getting in them or fixing them?

IAnon, I'm the admin on the server. We do specifically state in the motd upon connecting to our server that using hacked weapons results in a perm ban. The fact that you came in here and admitted you were using a hacked weapon, got a trial by fire and appear to have corrected your load out is enough for me to remove your ban which I just did.

Arrgh. Using newest scripts/remoteexec/createvehicles. Had a full server of people enjoying themselves and then some douche hacker gets on and starts killing everyone. Still nothing in the remoteexec.log :/ Scripts log started showing some stuff other than the standard isDedicated while it was happening but appears to be stuff happening TO the other players. Edit: I just noticed something. Downloading the files from the google code site directly saves them with unix crlf encoding. I wonder if maybe that's the issue? The standard BEserver bans.txt is written using Windows crlf encoding. If BE doesn't understand unix encoding then lots of people might be putting .txt files in place where the entire thing is a single line comment or not properly formatted so BE is just ignoring the entries.

See if it works with individual lines: %curlpath%\curl.exe -T %temp%\createvehicle.txt %ftpurl% --user %ftpuserpass% %curlpath%\curl.exe -T %temp%\remoteexec.txt %ftpurl% --user %ftpuserpass% %curlpath%\curl.exe -T %temp%\scripts.txt %ftpurl% --user %ftpuserpass% If so I'll update my example.

I updated my post to include a local batch you can run that will update your files automatically if your dayz server is hosted and supports ftping battleye files. You'll still need to refresh your server manually though unless your host automatically detects new files and does so for you.

Here is a batch file that updates the filters. I run this along with the job that kills and restarts the arma 2 server. You just need a copy of curl on your drive somewhere. http://curl.haxx.se/...atic-bin-w64.7z Edit the batch files accordingly. Here is the code: set a2oapath="C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\cfgdayz\battleye" set curlpath="C:\Users\Administrator\Desktop\curl" %curlpath%\curl.exe http://dayz-community-banlist.googlecode.com/git/filters/createvehicle.txt -o %a2oapath%\createvehicle.txt %curlpath%\curl.exe http://dayz-community-banlist.googlecode.com/git/filters/remoteexec.txt -o %a2oapath%\remoteexec.txt %curlpath%\curl.exe http://dayz-community-banlist.googlecode.com/git/filters/scripts.txt -o %a2oapath%\scripts.txt If you want to do this with a managed server you'd normally have to upload the files manually. BUT here is a batch file you can run that does it quickly without interaction on your part. I didn't test this at all :( but it looks about right :) You will still need curl downloaded and in a folder on your desktop: set curlpath="C:\Users\Administrator\Desktop\curl" set ftpurl="ftp://myhost/pathforbattleyefiles/" set ftpuserpass="myuser:mypass" %curlpath%\curl.exe http://dayz-community-banlist.googlecode.com/git/filters/createvehicle.txt -o %temp%\createvehicle.txt %curlpath%\curl.exe http://dayz-community-banlist.googlecode.com/git/filters/remoteexec.txt -o %temp%\remoteexec.txt %curlpath%\curl.exe http://dayz-community-banlist.googlecode.com/git/filters/scripts.txt -o %temp%\scripts.txt %curlpath%\curl.exe -T "{%temp%\createvehicle.txt,%temp%\remoteexec.txt,%temp%\scripts.txt}" %ftpurl% --user %ftpuserpass%

Are the extra log files not created until an event actually occurs? (createvehicle.log and remoteexec.log )

I've got a strange issue with a couple legit players who are being kicked from our server by battleye when I install the newest scripts.txt. We've gone as far as having these players completely reinstall arma2/arma2oa. We've had them respawn etc. They can connect to most other servers (although some exhibit the same behaviour) but there really isn't a way to determine if the servers that work are running the newer scripts.txt or not. Has anyone else seen this happening? And BTW, these guys have tried all the reinstalling battleye etc etc. Router MTU, creating new profiles etc etc. Nothing seems to work.

If only stuff wasn't bugged. Next server restart all those tents will be back filled with the same stuff.

Rocket, None of this stuff matters with the current state of hacking in the game. 20 minutes after restarting our server with the new scripts.txt someone teleported everyone into the air and they died from the fall.

Set your scripts to restart at a uncommon time. Everyone and their grandma restarts every 6 hours on the hour. Switch it to restart at like 43 after the hour or something. guessing hive is getting hammered by all the servers trying to restart at the same time.

That is what I figured as well. I also think that using FPS to measure what the regularChecks is doing was a flawed recommendation by the dayz devs. We get the EXACT same server side FPS but horrible lag/de-sync and disk i/o with it turned on.

It doesn't matter what you get when you first restart. If you let the game run for about 20 minutes and let it fill up that is your REAL server side FPS.

If you are the admin of your server you should have received instructions in an email that was sent out to all server admins last night. If you aren't the admin you can't monitor it.

This server we are renting is pretty underpowered. I see about 5 FPS but zero actual in game lag without the line. With the line its the same but unplayable. What kind of hardware/cpu you have in your dedicated server?

Removed for the following (next post) douche baggery.

Well to be fair they were killing a guy OFFERING to hack the game. And if you consider a goofy/useless glitch that has been in arma 2 for years to be hacking you need to CTFO.