DJ_Teschmi

If your server is up to date (1.7.7.1) and if this one is a classic public hive server without any modification you will have no problem with the filters.

Hi, Sorry but i just double check and i don't undertstand why this flare is logged in my createvehicle.log... Here the createvehicle.txt up to date: Line1 !="F_40mm_Green" !="F_40mm_Red" !="F_40mm_White" !="F_40mm_Yellow" !="G_40mm_HE" Line46 1 "M_" !="G_40mm_HE" //!="40mm_" //keep monitoring to catch obvious abuse The flare should be removed from logging but here a sample of my createvehicle.log: 21.06.2013 12:12:21: Simon (IP_removed) GUID_Removed - #46 "F_40mm_White" 66:44 66:5 Survivor2_DZ [6338,7935,330] [-52,59,12] 22.06.2013 11:57:41: mort parmis les morts (IP_removed) GUID_Removed - #1 "SeaGull" 94:2 [-18639,25825,395] 22.06.2013 14:23:51: yannick (IP_removed) GUID_Removed - #46 "F_40mm_White" 190:117 190:5 Survivor2_DZ [6584,2404,20] [0,78,16] This behaviour happens only with the white Flare. Not really important but i'm curious :) Thanks

Hi Faco, hope your are well. Apparently "F_40mm_White" is missiing from the list of unlogged legit items in "createvehicle.txt" Thanks DJ Teschmi

Hi, Very strange way to enjoy DayZ... "Admin-only gun SCAR-H/L" WTF ???? :o These filters are very usefull but there are dedicated to the legit dayz mod, if you have a custom server you have to modify these filters as needed. The kick for bloodbag was because the filters was not up to date. DJ Teschmi

That was already discussed in the "1.7.7.1 Hotfix" thread. http://dayzmod.com/forum/index.php?/topic/140121-dayz-mod-1771-hotfix/page__st__160#entry1378217 As i understood RAZOR would change the way we use tents, for the moment they are stashes but in the future they will be other way to hide stuff. That is just my opinion after reading Razor replies regarding this tents issue.

Do you have a "battleye" folder in the "ROOT/@dayz/" path? If yes that should be the right one. I don't have this kind of arborescence on my current server but if i remember well that was the path on my old server. :thumbsup:

Can you paste the path of your Battleye folder please?

Thanks for the work ;) Edit: Faco are you sure that "DMR" was not the legit name for DMR before the upgrade to 1.7.7? Because some people are still carrying this weapon, maybe they looted it before the 1.7.7, no? I dont' have an old log here to verify that. Anyway i will not kick "DMR" on my server for the moment. Thanks

Hi Faco, Can you explain the difference between the weapon "DMR" and "DMR_DZ" because you add a kick this morning in the addweaponcargo.txt for "DMR_DZ" and someone was kicked for that on my server. Maybe this rifle was renamed in 1.7.7 and some people are carrying the old version of this gun. And maybe you just wanted to remove it from logging, no? Thanks

With the new filters up to date? Your server is in 1.7.7.1 version?

Hi, You are reading my mind, we have the same question :D It cause setvariable restriction #0 if remember well. We don't ban for that for the moment but yes it will be great to know.

Ahah ! I told you Ameo ! Kick for "remExFP" was not a good idea ;) Lot of work with all these new cheats dedicated to the new 1.7.7 version.... Good luck Faco ;)

Hi, I found some things yesterday evening while browsing my server (1.7.7.1) logs: - If you see something in createvehicle.log is that it is something abnormal and you have to investigate. - If you see something in selectplayer.log is that it is something abnormal and you have to investigate (often a ban). - Hacked weapons and hacked ammo are displayed in the addweaponcargo.log and addmagazinecargo.log and people will be kicked for that. - If you see something in setpos.log is that it is something abnormal and you have to investigate (often a ban). If you see many people at the same time in this log, it's probably because of a hacker was executing a malicious script and you have to cross-check in the remoteexec.log, pubvar.log and script.log to catch the hacker. Setpos of vehicles is a hack except if the vehicle's driver got a desync while driving. - attachto.log is working as usual like in the previous version but you have to check if the objects positions in the logs are always [0,0,0] or [0,1,0]. Wrong positions is a hack, attachto of vehicles is a hack. - If you see something in mpeventhandler.log is that it is something abnormal and you have to investigate (often a ban). - setdamage.log, setvariable.log, publicvariable.log, script.log. remoteexec.log seems to work as usual like in the previous version I can't find any server_console.log but i don't know if it's because of the new version or because of our new provider... Hope it will help ;) DJ Teschmi

Ok good to know, but we really need any branch of the tree touches the tent. We have to change our way to hide tents.

I don't have picture here but it's impossible to pitch tent close to tree trunk for example. That's why we can't hide tent properly in a group of trees. Thanks

This hack script should be detected now with new filters: http://dayzmod.com/forum/index.php?/topic/139058-battleye-server-filters-for-dayzmod-1771/page__st__20#entry1377876

;) Perfect ! Thx

Just applied the new filters and one person has been instant kicked for "script restriction #192": Any idea? Thanks

Thanks Facoptere, i will update my filters as soon as possible. The new "SRVFACO4567" remoteexec script will be catched with he new version of remoteexec,txt?

Hi, This is brand new Debug Monitor ! Click on it to navigate or ESC to quit. Enjoy !

Hi, The same script on our server. I already reported it on the battleeye filter topic: http://dayzmod.com/f...20#entry1376998 That's weird because this kind of remotexec script should be detected by the filters... no?

Hi Facoptere, Other little thing to add in the createvehicle.txt for the new 1.7.7.1 release: Add in the first line: Thanks

Hi guys, We are in 1.7.7.1 version for a couple of hours now and a hack just happened: All people were kicked for a setpos restriction #0 (BattleFieldClearance) and the hacker did this in the remoteexec.log: Facoptere, the hack was i guess dedicated to your server :( but was already used yesterday on many servers.... I don't understand because this kind of hack was normaly catched by the filters right? Thanks for your help. DJ TESCHMI

;) Maybe Facoptere would be the right person to help us on how the new filters are working and what logs we need to monitor.

Agree with u, they are many changes in the way the new filters are working. For example, i don't have any createvehicle.log on my server <_< How to catch hackers with this new version? Thanks