hohlraum

Sound is jacked up with this beta. The environmental sounds are much quieter and the directional sounds are way off.

Lots of entries from people who I know aren't cheating. Crossbow bolts appear to use it for sure.

So what kinda stuff should people NOT be attaching to? Looking at how it's logging I've seen known hackers attaching to Camo1_DZ, Sniper1_DZ and Survivor2_DZ what were they doing?

Thanks brother! :)

What does the new attachto.txt do and does it require a specific arma 2 beta?

start /min /wait /AFFINITY E /REALTIME Expansion\beta\arma2oaserver.exe "-beta=Expansion\beta;Expansion\beta\Expansion" "-mod=Expansion\beta;Expansion\beta\Expansion;Expansion;ca;@dayz;@bliss_1.chernarus" -name=Bliss -ip=199.19.67.231 -port=2302 -config=dayz_1.chernarus\config_XXXXXXX.cfg -cfg=dayz_1.chernarus\basic.cfg -profiles=dayz_1.chernarus -noPause -noSound -cpuCount=3 -exThreads=1 -maxMem=2047 -noCB Many players cannot connect via the arma 2 oa server browser (it shows up they just get connection failed and nothing shows in the logs). It is almost like gamespy is telling them the wrong ip/port to try to connect! They can connect just fine by entering the ip/port directly or using dayz commander. Going nuts on this one. Anyone have any ideas?

Getting the same issue. Can remote connect to our server but some players can't connect via the gamespy browser. Driving me nuts.

Anyone have any ideas how to prevent this new debug monitor replacement from being injected into the server? It was called Mr Mc Epicness. Always have the newest filters running from the DCBL.

This is on a windows server btw. Ignore the linux/unixish commands. I just use a cygwin shell because it's easier to work with the log files. Anyway, here is a better example of a dbag flooding our server and being ignored by battleye. Same MaxSetDamagePerInterval and setdamage.txt are in place as in the previous post. EDIT: I just checked the logs and this guy WAS kicked for set damage by battleye. But that doesn't change the fact that it took 9 seconds and 4500 violations before it took place. :/ First command shows how many set damage the guy did before he was eventually banned by dayz anti-hax. $ zgrep Freddie *.gz | grep '1.000000' | wc -l 4592 This command show when it started. $ zgrep Freddie *.gz | grep '1.000000' | head setdamage.log.20121024_044015.gz:24.10.2012 04:19:06: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #0 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:06: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #1 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:06: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #0 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:06: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #1 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:06: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #0 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:06: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #1 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:06: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #0 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:06: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #1 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:06: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #0 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:06: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #1 1.000000 27:743 This command shows how long it went on. $ zgrep Freddie *.gz | grep '1.000000' | tail setdamage.log.20121024_044015.gz:24.10.2012 04:19:16: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #0 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:16: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #1 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:16: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #0 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:16: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #1 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:16: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #0 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:16: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #1 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:16: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #0 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:16: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #1 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:16: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #0 1.000000 27:743 setdamage.log.20121024_044015.gz:24.10.2012 04:19:16: Freddie (86.9.210.94:2304) 563cc824a0ec3e619f2f6328abfceac2 - #1 1.000000 27:743

The player was not kicked until he was banned and that job only runs every 15 seconds. I've reviewed EVERY set damage ban (since implementing the new interval and 5 "1.000000") and not a single one of them was kicked before they were banned and it was always several seconds later. It seems unlikely that DAH would always be able to beat battleye with a banning vs. a kick. Every other .txt kick seems to be instant.

The set damage stuff isn't working. Just had someone flood 1.000000 over 2400 in 5 seconds. setdamage.txt: 1 "" 5 "1.000000" beserver.cfg: MaxSetPosPerInterval 1 9 MaxSetDamagePerInterval 2 1 Confirmed via BERCon: MaxSetDamagePerInterval 2/1s He should have been booted instantly for the setdamage or he should have been booted for flooding. Neither did squat. Ideas?

I wouldn't bother with MaxCreateVehiclePerInterval. When a player logs into the game they will get kicked if you use it depending where they are in game. Just use dayz anti-hax to deal with createvehicle stuff.

What are the rest of you using for starting values? DCBL already is kicking for any setdamage 1.000000 so maxsetdamageperinterval is really just for flooding non-1.000000 protection. and once every second is plenty for those. maxsetposperinterval. I've gone through my logs looking for innocent entries and it looks like 1 every 9s should be sufficient. For maxcreatevehicleperinterval I don't see how it can really be used because of heli explosions. actually looking closer basically anything more than 3 per second should be fine at a minimum and I think 4 per second is safe. So for now I guess I'm starting with MaxCreateVehiclePerInterval 4 1 .... strike that one. 4 1 randomly kicks people on login. guessing their clients call several of them very quickly on login. MaxSetPosPerInterval 1 9 MaxSetDamagePerInterval 1 1 ... ended up going with 2 1 instead. This is all using 1 second intervals. I think that stuff like MaxCreateVehiclePerInterval might be better suited for checking a larger interval. Dunno.

status?

Players are DOSing servers with setdamage as well. Had a guy flood 1.000000 damage to an object/player last night to the point (7MB setdamage.log) that battleye could no longer deal with the setdamage.log and kept spewing something about not being able to access the event log.

RE: setpos.log 25:507 [11416,3316,54] So I understand the second block is the coordinates. What are the XX:XX numbers?

Any reason why the first post hasn't been updated to include any of the new event log types that have been added recently? (setpos, setdamage, publicvariableval, etc)

Still having server hacked to bits at will. publicvariable.txt identified a single guy a couple days ago and he just kept changing his ip and generating new keys everytime I banned him. Nothing in the logs with regards to the guy who just teleported 50 people to the same location a few minutes ago on our server.

If anyone has a chance to cook one of these (publicvariable.txt) up for DayZ and/or DayZ Lingor a link would be much appreciated.

I hope you figure something out soon. We had someone inject something into the server that ran continuously for hours injecting code into clients connecting which made them run something that would cause a script restriction. In essence automatically kicking everyone who connected.

Came here to ask the same question.