muppet1856

Nope. AntiHax will do it.

Updated the source - will be included in the next build.

It seems that my builds frequently need 0.x.8,9,10 to get all the fiddly bits right. Jeez. OK. For the second time today. With the right cfg and the right damage.lst http://dayz-anti-hax.googlecode.com/files/DayZAntiHax-v0.8.1.1.zip

DAMMIT!!! I put a new together and didn't put it in.

Ok. Nevermind - I just rolled 0.8.1 - Added scan options for each of the scannable logs. Fixed a couple of bugs. All of which can be seen in its glory at http://code.google.com/p/dayz-anti-hax/downloads/detail?name=DayZAntiHax-v0.8.1.zip

Set it to 10000000 It will likely never see it. At least until I get around to adding this in the config.

A line about catching flies is bouncing around my head at the moment... Nevermind. Here's the answer - the restrictions 38 & 40 are used to exploit DayZ. Hence the reason they kick. The default CBL filter haas them set to a 5. A 5 means 1 - log PLUS 4 Kick. ANY entry that ends up in Remote Exec results in a ban. So, if you're comfortable with the risk, change your remoteexec.txt from 5 to 4 and it will kick, but not ban (it will also not log it.) Mind, that when you do that, you will need to change the remoteexecUpdate flag from true to false otherwise it will overwrite the file with the CBL. As far as the ban goes, I guess you need to understand the way AH works. It scans the log files and bans. You need to remove the offending lines from remoteexec.log, scripts.log or wherever it is indicating. It sounds like scripts.log. Once you take it out of scripts.log you can then remove the ban from bans.txt and it will not show up again. Just find the GUID of the player and search all the log files and remove the player from them. EASY AS PIE. Oh, and you should probably try reading more. This is a known issue, but is mostly accepted as a necessary evil.

If you reboot the server you will indeed need to restart Anti-Hax. You do not need BEC if you run this, unless you want to restart the server on a schedule.

So I was able to roll 0.8.0 tonight. I fixed the connection issue. It now connects and disconnects as needed. I also added additional config options for mpeventhandler, as well as the logic to support it. Additionally, you can now set your banlist update frequency and filter update frequency. Also, for those who care, setdamage.txt is now in the cbl filters. Available for download here: http://code.google.com/p/dayz-anti-hax/downloads/detail?name=DayZAntiHax-v0.8.0.zip

There were some programming decisions made early on that made that a bit challenging. Maybe in a future release. I have gone back to the connecting and disconnecting, but now I am not filling the console with messages.

I know about this issue. I was going to fix it last night, but the kid bit through her tongue and we had to take her to the ER. I'll try again tonight. :) Its a simple fix. I'm going to go back to connecting only when I have a reason to send a message. It will result in more connect/disconnects, but it will remove this bug. I think the result will be much better.

Fixed a bug where the filters weren't loading and the message was still working. I reversed the conditions. New version 0.7.1 posted.

I don't recall the version of ArmA, but if you just create a blank file called setdamage.log in the same folder as your bans.txt you'll be all set. If you didn't put the DayZAntiHax in that folder and set the working dir to that, then you need to fix that, but that doesn't sound like your problem. I think it's the blank file.

It does reload the bans and the event file's and scripts as well. The filters are downloaded on the same frequency as the message (configurable). Also, you can individually enable each filter file. I could add a multiplier for the ban list to reduce the load. (It's not like the ban list is updated hourly).

UPDATED to Version 0.7. Fixed: SPAM SPAM SPAM SPAM Unnecessary RCON Disconnections and Connections Added: Filter File Download from community ban list Filter FIle URL can be customized (to support users running beta servers) Filter File Download can be disabled **Enabled by default** Can disable Protected by AntiHax Message Can change frequency of AH Message Working on: Active file monitoring - no more polling - ban 'em when they do it. Adding automatic IP ban - to ensure someone doesn't use another GUID More GUI features for both Command Line and GUI - such as download status (bytes etc.) and AH statistics (# local bans, community bans, Admin Bans)

Yeah, the spam is annoying. I''ll add a frequency value in the config. I'll also change the connection mechanism. I'm currently connecting every-time I have a message. That seems bad now that I've run Several thousand cycles.

http://dayz-anti-hax.googlecode.com/files/DayZAntiHax-v0.6.zip

Removed. False Positive.

Exactly - *facepalm* Corrected.

I have just updated the source, binaries, and zip. FWIW, I've stepped in to help with the updates. Version 0.6 is live. It has been split into a class library as well to support the two interfaces - a command line and a GUI. The GUI is sparse right now, but the foundation is laid for more. Latest update includes publicvariable scanning, setdamage scanning, and integration with the RCON utility BattleNET. https://github.com/ziellos2k/BattleNET

The hackers have been pretty busy warping them around. It should be better now that they have added the ability to see when ppl are warping them. They exist. We had the Ural Chopper and UAZ for while.

No reason? You admitted to playing with a hacker. Then all of a sudden, I have 20 sandbags spawned in. You keep showing up in the logs, when NO ONE ELSE DOES. I spent 3 hours yesterday pouring over the logs trying to convince myself that you were right and there was no reason to ban. But then I saw the logs today. I haven't had that many entries from ANY ONE PERSON. There are plenty of servers. FIND ANOTHER.

Here's to hoping I see you first. <_<

Next time, make sure your story is straight the first time. I have conferred with the DayZ team and found there is a bug that supports this scenario. Please be careful who you run with.

Je parle français.