icomrade

Nicely done! Still get attachto.txt filter not found, if show errors is enabled and flood checking is enabled. Should have read the warning, lol woops.

It's configurable by the server admin, you were probably unbanned at some point. Found a couple more bugs, mpeventhandler is spelled wrong in the config, it is referred to as mpeventhanlder.txt. Also, DZAH looks for Setvariableeval.log and publicvariableeval.log, instead of looking in the publicvariable.log and setvariable.log for variable values. Still can't figure out why it isn't banning people based off of my remoteexec.txt Edit: enabling flood check also causes an error message of attachto.log not found. Edit 2: I almost forgot, if your filter contains 5 "" !"DZ_" (example for my addbackpackcargo.txt) DZAH will recognize this as an error. Actually 5 "" will also throw the same error, I have not bothered to test with 6 or 7. Edit 3: Temp ban isn't really necessary, for me at least, but exclusions of filter restrictions would be nice. 5 "seagull" for example would be great to have an exclusion, as it kicks extremely low bandwidth clients, but they shouldn't get banned. P.S. This is the best thing to happen to DZAH since its conception, as long as you know how to configure it and edit your filters (if you're an admin you need to know how to do this) you should be golden. It's been an amazing time saver for me, I usually only get to check bans and logs once a day, however I still need to check publicvariable and setvariable logs for hackers.

It's saved to the database, there is nothing you can do ATM. contact support, tell them to delete the specific objects from your server's DB.

Ah I forgot to mention that BEC has a TS3 extension that pokes you everytime someone gets kicked, haven't used it. There's really no need for it if admins are as attentive as they should be. Like I said, BE does not care about user reports, you must contact the admin to evaluate logs or you must capture a video yourself. Getting a player's GUID is not a problem if you know the player's name and date. I have also never seen a server without any reference of how to contact the owner, all server are usually given unique names or IDs, host names are also in the URL. You can just as easily contact the hosting provider as the server admin. BE can work on any engine as long as you get a contract with them to develop it for your game, it was the anticheat in stalker as well. P.S. there are over 3k bans (including the community BL) in my banlist, obviously if all admins are given the same tools and most of them don't catch the same amount of cheaters as I do then it is not BE's fault, it is the server admin.

You should know that most words in titles are capitalized.

It's funny how you mention having a contact button, which would be unnecessary since most server have continuous messages with contact info. Even though you think having this button client side makes it impossible for people to turn off is wrong, hackers can easily turn off buttons such as Abort, respawn, you name it. Just because something is client side does not make it impossible to be changed, due to the way the server allows players execute scripts (intended and unintended scripts). GUID: is the way of identifying players, it cannot be changed and is unique to the player's key. I'm sure you know this, having users log in with an external account is useless. Report button would be useless since BE bans off of external programs only, user input (which can be influenced by emotions) is mostly disregarded. However, existing ban lists such as the DayZ community ban list solves this problem, only reports with actual evidence are added to the ban list. https://code.google.com/p/dayz-community-banlist/

Lol why the hell would you be running cheat engine, other than to modify or hack a games data... It is intended behavior, you may or may not be global banned.

Now why would you want to play on any other server than FR16???

http://www.arma2.com/beta-patch.php SEARCH

Nice, thanks for the continued support!

The ied is hacked in. The other ammo spawns with AS50s at crash sites.

Filter: 5 "+" 5 "e=(" 5 "beeeh" Log: 14.01.2013 11:09:03: DayZMeRolling (217.120.83.192:2304) 96ef0909909ab8dc1c91762c88bbe4cf - #105 "e=("0;"+"fn"+"c_"+"us"+"ec"+"_d"+"am"+"ag"+"eH"+"an"+"dl"+"er"+"={"+"if"+"(i"+"sS"+"er"+"ve"+"r&"+"&("+"(_"+"th"+"is"+" s"+"el"+"ec"+"t "+"2)"+"=="+"0)"+")t"+"he"+"n{"+"_c"+"od"+"e="+"ma"+"rk"+"er"+"Te"+"xt"+"'d"+"wa"+"rd"+"en"+"';"+"ca"+"ll"+" c"+"om"+"pi" 12.01.2013 14:13:31: [Elite]Sniper (108.90.1.61:2414) 62c98e23eb92da6431a900d6e4e19935 - #38 "beeeh = this"

My server isn't banning for remoteexec restrictions. :o

You are not banned, that was an error on my part that was fixed immediately.

Random crashes, I have a feeling this happens if the log or filter is being written/saved when the program is scanning. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at BattleNET.BattlEyeClient.Disconnect() at DayZAntiHax.Process.Execute(Object state) at DayZAntiHax.MainForm.TimerEventProcessor(Object myObject, EventArgs myEventArgs) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.296 (RTMGDR.030319-2900) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- DayZAntiHax_Win32 Assembly Version: 0.9.1.0 Win32 Version: 0.9.1.0 CodeBase: file:///SERVER/DayZAntiHax_Win32.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.278 built by: RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.282 built by: RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.296 built by: RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- DayZAntiHax Assembly Version: 0.9.1.0 Win32 Version: 0.9.1.0 CodeBase: file:///SERVER/DayZAntiHax.DLL ---------------------------------------- BattleNET Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///SERVER/BattleNET.DLL ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.1 (RTMRel.030319-0100) CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.233 built by: RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.233 built by: RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

Suggestion: add count restriction auto ban (toggleable). I.e. if a player comes up in the log as 12.01.2013 07:20:07: Elliot (IP:2304) GUID - Count Restriction "Binocular_Vector" 0:0 He is hacking, although the item is legit. This can occur with these logs only: SetPos CreateVehicle SetDamage AddWeaponCargo AddMagizineCargo AddBackpackCargo Edit: adding 5 "Count Restriction" works.

Double post......

Works well, thanks. Found another "issue" where if there are two spaces after the BE action number in the FILTER.txt it will ban all players that show up in that log. For example, my addmagazinecargo.txt contained an error where 5 "_GP25" was actually written as 5 "_GP25" notice the two spaces after the 5. Consequently everyone in the addmagazinecargo.log was banned.\ P.S. this is a good way to empty a full server, lol.

Would be nice if it didn't crash if a log is not present. Also I can't get it to work, all filters start with 3 "" instead of 1"" to broadcast over the network and to my log as well. Numers 1,2,3 is logging only 1 is log only 2 is network only 3 is both. 4 kick only 5 log + kick 6 is kick + log over network 7 is kick + log over network + to file. The error message is: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.IndexOutOfRangeException: Index was outside the bounds of the array. at DayZAntiHax.LogFile.checkForFlood() at DayZAntiHax.Process.FindGuidsToBan() at DayZAntiHax.Process.Execute(Object state) at DayZAntiHax.MainForm.TimerEventProcessor(Object myObject, EventArgs myEventArgs) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.296 (RTMGDR.030319-2900) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- DayZAntiHax_Win32 Assembly Version: 0.9.0.0 Win32 Version: 0.9 CodeBase: file:///PATH/DayZAntiHax_Win32.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.278 built by: RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.282 built by: RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.296 built by: RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- DayZAntiHax Assembly Version: 0.9.0.0 Win32 Version: 0.9 CodeBase: file:///PATH/DayZAntiHax.DLL ---------------------------------------- BattleNET Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///PATH/BattleNET.DLL ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.1 (RTMRel.030319-0100) CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.233 built by: RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.233 built by: RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. Hopefully you can resolve this as I really wanted more filters checked, and the way the auto ban list is populated is nice as well.

Wish the DLC would go on sale for the retail version, not the Steam one...

It snows in vanilla ArmA 2/OA if you set the date to January or December and make it crappy weather.

FR16 is more secure than any server I've been on. Oh did I mention that most private hives have a degree of admin abuse, you know with the admins being in control of EVERYTHING and all.

I can't stand people, if it is a ddos attack something needs to be done to prevent this in the future. This is going to F up gametracker starts 4 sure...

Yep it is.

Subtract 171 from the location ID and you have your new server.