byteslam (DayZ)

This works only for private hives! it does not solve the issue for public servers. and yes @Piranja13 it is a shame that no one from the dev team even confirm that they aware about this issue we suffer since a month, but it is like it is, the success make them blind for the community and if the do keep going this way, they will learn a pain full lesson being ignored from the community with the stand alone ... but this is a story about public relation :-)

Did you know how many people try to cheat or even do it per day? It is nearly impossible to run after them and verify all the logs just for only one server. Imagine you run a couple of servers, it will take hours everyday to do what you ask for. The evil is not the Admin, the Admin only tries to keep the game playable by reasonable amount of time for all of you. If I get 98 Cheaters out, and 2 non cheaters by mistake the ratio is fine. Everybody can come to our teamspeak and I will immidiatly look for the GUI and if it is not sure, I will unban them... happend once since 5 weeks now by more then 2500 Cheaters now. Play fair do not cheat and nothing will happen to you. And if, ask the support of BE to help you... but pushing whinny forum posts will not help you in any case.

Normaly you end up in the cumunity ban list if the admin proofs this with logs and if you have been reported by at least twice admins.. I am sure there is a minority of false positive but since we use this ban list in combination with the latest anticheat files from BI the cheaters on our server have been dropped down to an level where we can almost enjoy the game... And BTW we are about 10 Players and nobody of us have been banned or kicked by a flase dectection which brings me to the point where I belive that all this whinny kids here have been cheated and now facing the consequences. Very simple, do not cheat and all will be fine.

I am tiered to hear this stories about kicking for clan members, wtf? There are so many other issues because of Teleporting, cheating and hacking that this topic, even if it is true is such a minor thing....We have per day about 10 detected (logs) and varius undetected( radar, esp, loot spawning...) cheaters that this should be the first pain point which should be solved...

I guess, there is nothing we can do against RADAR hacking or?

I see no reason why it should be legit to call a createVehicle which spawn a usable device, (exceptions are wrecks and craters). In all other cases, it will lead immediately to a ban. Banned players can join the TS and I will give it a deeper look, but so far all of these guys who tried it never complained... means all of them (about 157 since two weeks) are guilty. Since I use always the latest scripts.txt createvehicle.txt and remoteexec.txt (auto synced and loaded every minute) and the community ban list in combination with BEC and DayZAntihax, we face no real cheater incidents anymore. The game runs smooth and makes fun again. However I am willed to risk a minor false positive, if someone complain I will immediately investigate and remove the ban if I can proof it was legit.. We receive a lot of positive comments from the players on our server, all of them appreciate these strong counter measures.

Mariko, please REMOVE the link immidiatly, you give these scriptkiddies the information they are looking for. Write this information in PM to the Battleye team from BI

19.08.2012 12:50:12: Admin (IP:2304) UIDUIDUIDUIDUIDUIDUIDUIDUIDUIDUIDU - #0 "AmmoBoxBig" 242:17 [7749,3185,5] 19.08.2012 12:50:12: Admin (IP:2304) UIDUIDUIDUIDUIDUIDUIDUIDUIDUIDUIDU - #0 "DZ_Backpack_EP1" 242:18 [0,0,0] 19.08.2012 12:50:12: Admin (IP:2304) UIDUIDUIDUIDUIDUIDUIDUIDUIDUIDUIDU - #0 "DZ_Backpack_EP1" 242:19 AmmoBoxBig is not allowed in DayZ or?

whats about the changed dayz_server.pbo of 1.7.2.5 which is reported hereand the ready compiled pbo from here? 1) is that legal to use in terms of do not lose the hive access? 2) has someone already tried this successfully? It is really painful with this saving and repair issues. UPDATE: it does not work, the problem is probably also in the hiveext.dll

He makes himself invisible to all other players. Anyway, there is no reason why a player should execute scripts like this, I would say Kick an Ban if you see such behavior on your server. I do the same now, strong law and order strategy and nobody complained so far, so they are all guilty I assume.

17.08.2012 13:56:08: umaidez (91.103.79.216:19810) a0bf6acremoved48db5 – #122 “_i = _i+1}] do { [nil, _targetClient,"loc", rJIPEXEC, BIS_MPF_ServerPersistentCallsArray select _i] “ could this be cause a death of all players?

6.08.2012 19:52:00: Jason (95.32.5.143:19525) 4c2f7fda5c48452f71b3b1801c1d0ca8 - #0 "if (isnil ("trtrtrtrtr0n")) then {MYplayersobj hideObject true;};" 16.08.2012 19:52:00: Jason (95.32.5.143:19525) 4c2f7fda5c48452f71b3b1801c1d0ca8 - #6 "if (isnil ("trtrtrtrtr0n")) then {MYplayersobj hideObject true;};" 16.08.2012 21:00:42: Stein (195.1.208.26:41183) 94aabe93257849695fd07616391f4967 - #0 " if (isServer) then { _dsasadsa = createVehicle ['UH1H_DZ', [3273.27, 13862.2, 0], [], 0, 'CAN_COLLIDE']; _dsasadsa setVariable ['ObjectID', 2044.89, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _dsasadsa]; _uid = _dsasadsa cal" 16.08.2012 21:00:42: Stein (195.1.208.26:41183) 94aabe93257849695fd07616391f4967 - #35 "ble ['ObjectID', 2044.89, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _dsasadsa]; _uid = _dsasadsa call dayz_objectUID; _dsasadsa setVariable ['ObjectUID', _uid, true]; _dsasadsa setVariable ['OwnerID', 0, true]; }" 16.08.2012 21:45:00: thebos (86.0.231.244:2304) f902e278d93cb76774a94e6113b0ebba - #0 " if (isServer) then { _dsasadsa = createVehicle ['TT650_TK_CIV_EP1', [3043.74, 1972.36, 0], [], 0, 'CAN_COLLIDE']; _dsasadsa setVariable ['ObjectID', 7879.53, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _dsasadsa]; _uid = _dsa" 16.08.2012 21:45:00: thebos (86.0.231.244:2304) f902e278d93cb76774a94e6113b0ebba - #35 "ble ['ObjectID', 7879.53, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _dsasadsa]; _uid = _dsasadsa call dayz_objectUID; _dsasadsa setVariable ['ObjectUID', _uid, true]; _dsasadsa setVariable ['OwnerID', 0, true]; }" 17.08.2012 11:28:47: QtexIRL (88.134.25.68:2304) 878a7039c85d42f676c7cf372fc3ced1 - #0 " if (isServer) then { _object = createVehicle ['UH1H_DZ', [7904.3, 13221, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 8480.19, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objectUI" 17.08.2012 11:28:47: QtexIRL (88.134.25.68:2304) 878a7039c85d42f676c7cf372fc3ced1 - #1 "7904.3, 13221, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 8480.19, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objectUID; _object setVariable ['ObjectUID', _uid, true]; _object s" 17.08.2012 13:57:11: Jase (92.17.64.127:63198) 70b307d6efe7363bf4fb0ab112030fc3 - #0 " if (isServer) then { _object = createVehicle ['UH1H_DZ', [3430.62, 4067.96, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 4131.42, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objec" 17.08.2012 13:57:11: Jase (92.17.64.127:63198) 70b307d6efe7363bf4fb0ab112030fc3 - #1 "0.62, 4067.96, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 4131.42, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objectUID; _object setVariable ['ObjectUID', _uid, true]; _object s"

The provided ban list contains a lot of double entrys.

Hi, the new BE features are working pretty well, cheater amount has dropped almost to zero for now...only two things are looking not normal to me in our my remotexec.log, can someone tell me if it is legal before I put a BAN on this guys? UPDATE: I got the confirmation from Dwarden (Bohemia) that this is cheating 16.08.2012 19:52:00: Jason (95.32.5.143:19525) 4c2f7fda5c48452f71b3b1801c1d0ca8 - #0 "if (isnil ("trtrtrtrtr0n")) then {MYplayersobj hideObject true;};" 16.08.2012 19:52:00: Jason (95.32.5.143:19525) 4c2f7fda5c48452f71b3b1801c1d0ca8 - #6 "if (isnil ("trtrtrtrtr0n")) then {MYplayersobj hideObject true;};" 16.08.2012 21:00:42: Stein (195.1.208.26:41183) 94aabe93257849695fd07616391f4967 - #0 " if (isServer) then { _dsasadsa = createVehicle ['UH1H_DZ', [3273.27, 13862.2, 0], [], 0, 'CAN_COLLIDE']; _dsasadsa setVariable ['ObjectID', 2044.89, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _dsasadsa]; _uid = _dsasadsa cal" 16.08.2012 21:00:42: Stein (195.1.208.26:41183) 94aabe93257849695fd07616391f4967 - #35 "ble ['ObjectID', 2044.89, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _dsasadsa]; _uid = _dsasadsa call dayz_objectUID; _dsasadsa setVariable ['ObjectUID', _uid, true]; _dsasadsa setVariable ['OwnerID', 0, true]; }" 16.08.2012 21:45:00: thebos (86.0.231.244:2304) f902e278d93cb76774a94e6113b0ebba - #0 " if (isServer) then { _dsasadsa = createVehicle ['TT650_TK_CIV_EP1', [3043.74, 1972.36, 0], [], 0, 'CAN_COLLIDE']; _dsasadsa setVariable ['ObjectID', 7879.53, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _dsasadsa]; _uid = _dsa" 16.08.2012 21:45:00: thebos (86.0.231.244:2304) f902e278d93cb76774a94e6113b0ebba - #35 "ble ['ObjectID', 7879.53, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _dsasadsa]; _uid = _dsasadsa call dayz_objectUID; _dsasadsa setVariable ['ObjectUID', _uid, true]; _dsasadsa setVariable ['OwnerID', 0, true]; }" 17.08.2012 11:28:47: QtexIRL (88.134.25.68:2304) 878a7039c85d42f676c7cf372fc3ced1 - #0 " if (isServer) then { _object = createVehicle ['UH1H_DZ', [7904.3, 13221, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 8480.19, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objectUI" 17.08.2012 11:28:47: QtexIRL (88.134.25.68:2304) 878a7039c85d42f676c7cf372fc3ced1 - #1 "7904.3, 13221, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 8480.19, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objectUID; _object setVariable ['ObjectUID', _uid, true]; _object s" 17.08.2012 13:57:11: Jase (92.17.64.127:63198) 70b307d6efe7363bf4fb0ab112030fc3 - #0 " if (isServer) then { _object = createVehicle ['UH1H_DZ', [3430.62, 4067.96, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 4131.42, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objec" 17.08.2012 13:57:11: Jase (92.17.64.127:63198) 70b307d6efe7363bf4fb0ab112030fc3 - #1 "0.62, 4067.96, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 4131.42, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objectUID; _object setVariable ['ObjectUID', _uid, true]; _object s" They traveld directly to the BAN list, but does somebody knows what I have to add into the remotexec.txt to fire the ban in an automated way and immidiatly?

How to clean up a server which suffered under several Cheat attacks? At the positions where two cheater clans spawned vehicles, we found also about 20 tents with all the equipment in you normaly can only dream off. Nice to have but this tens always get filled again after a server restart...this means the position becomes now a more popular location then the airfield. Any chance to get this tents removed? mayby with the risk of loosing all other tents as well

whats about the SQL file which holds the local Server data like tents and vehicles? if I remove it, the server starts from scratch or not? May this is also the reason for the save issue, if the file has been not converted to the current 1.7.2.5 release, all data saved are not stored to this file perhaps??

I just guess, but as the tents exactly at the position where ATV, Helicopter etc. has been created, I assume the content like NV Googles, 10xSD M4A3, 10x M107 and so on is not legal and I dont want all players on our server going there to get equipped as best as possible all the time... I am thinking of deleting the hive DB on our server or something like this, to start from zero.

The current files do not prevent teleporting and I can not find the information back about the players who teleport himself behind us and killed, also a teleport into a building was recognized and proofed but in the logs I am not able to locate these guys

I agree, I contacted the support team and even posted logs from possible hacks to get a proof to ban, but no response until now. This mean as an Admin you are alone and you have to take counter actions to protect the 49 players on your server which would like to play against the 1 script-kiddie. I do perm BAN if I am sure about the person who did it. should we not exchange BAN lists? Does it make sens to have a standard way of identify hacks and deliver always the proof along with the BAN file? This is some work but it will make live harder for script-kids. what do you think?

I can confirm, there are still graphical issues ver often at the northern airbase if you look into the direction of Humwee wracks.

Hi, yesterday all players on our server died at the same time and in the death screen the message " livestream being hacked" appears. Everybody is now starting at zero. Does this hack means the hacker was connected to our server as a player? is there a way to identify the guy? Thanks for sharing your expirience and knowlege

Thats what I did, but in the log (server_console) is seems to be fine. What das "livestreaming" mean in this case? The Battleye log shows the following suspect part at the time when it happens but I am unable to interpret it (I removed the UID and name from the player ) 06.08.2012 17:23:49: Suspect (178.4.148.10:2315) 64e88888888888888888888888888fac - #107 z_code\system\server_monitor.sqf"; }; if (!isDedicated) then { 0 fadeSound 0; 0 cutText [(localize 06.08.2012 17:23:49: Suspect (178.4.148.10:2315) 64e88888888888888888888888888fac - #107 = 30; dayz_spawnPos = getPosATL player; if(isDedicated) then { dayz_disco = [];

The sixupdater deploy Arma2 Beta version 1.6.1.95057 and NOT 95054 anymore.... most of the servers are named wrong to 95054 by running already 95057. It seems to be an issue because players with the 95054 version are on trouble by joining higher version.