Magotchi

Updated my supplemental filter at its Google Code project. Added: 2B14 300Rnd_25mm_GAU12 G36K Laserdesignator_mounted M252 MLRS Remington870 SmokeLauncher

In the last couple weeks there have been some terrible undetectable hacks, where it only appears that each person is running commands on their own character rather than the hacker directly running them. If I had a solution for it, I'd implement it. This is also the first line of the MOTD on the server to warn people that getting hacked is likely right now. I'm sorry I can't do more, but it's a game-wide problem at the moment, and popular servers get hit the hardest.

It often takes a few minutes for a player with a hacked item to be kicked. Sometimes it's faster. It just depends on if they do certain things that trigger the dayzPlayerSave event.

linkinxp: Yes, but you'll have to remove the lines each time you update the filter from the DCBL, and you'll have to tell DAH to not automatically update the file.

The DCBL createvehicle.txt logs everything except a specific whitelist and kicks for some specific things already. DayZ Anti-Hax can then ban for specific things in its blacklist if they show up in createvehicle.log. You could of course just add your own custom entries into createvehicle.txt with a 5 before them to auto-kick for them. I prefer to add nasty items to the DAH blacklist and have them be auto-banned for, though, personally.

Good idea: https://code.google.com/p/dayz-hacked-items-publicvariableval-filter/ http://dayz-hacked-items-publicvariableval-filter.googlecode.com/git/publicvariableval-local.txt

Glad to hear. Sorry for the mix-up.

You're already unbanned, Ernest, as you were indeed part of the batch the hacker caused. I was just explaining why didn't unban you when you first asked. That's why I said "normally" and explained that I "didn't notice". EDIT: Also, I've adjusted the settings on the server so mass-bans for this specific thing (setdamage hacking) won't ever happen again.

DayZ is a free mod for Arma 2: Combined Operations. Nobody bought DayZ.

I've unbanned that entire streak of bans that happened for that tonight. They were caused by a hacker inducing that on other players. It's a relatively new problem. I review all bans on the server about twice a day (for submission to the DayZ Community Banlist), and I eventually would have realized it. Also, if you ever want to appeal a ban, it's always faster to post in the forums at clansm.net. If you post here, I generally won't notice it until I get a Google Alert about it. Ernest: I only didn't unban you because you story was totally bogus (was referring to something a few days ago), you had a different name today (when you were actually banned), normally the detection you got is conclusive, and I didn't notice that a ton of other people had been banned at the same time.

I updated my blacklist. Added: FlareWhite_GP25 FlareRed_GP25 FlareLauncher FlareGreen_GP25 EvDogTags BAF_L85A2_UGL_SUSAT ARTY_30Rnd_105mmHE_M119 AK_47_S 500Rnd_TwinVickers

What you guys have shown so far is an incomplete whitelist and a far from complete blacklist. Also, if you're just copying and pasting from stuff you found in Google (like http://www.cheatz.cc...ayz-classnames/ , cheat forum :)), it might be nice to mention that. EDIT: Parts of that data are incorrect as well. For example, M4A1_HWS_GL is illegal, but it's in the list of valid weapons. If all you needed was a whitelist, here's the one from my script I use to make the blacklist (based on my script which banned for hacked weapons): Moved to Google Code project. I originally made it from perusing the unbinned config.bin, and then I added other stuff as it showed up (like when people logged in with "crowbar_swing", which is crowbar ammo). In reality, though, you'll need a bit more than a whitelist.

I'm familiar with looking through the spawn lists in config.bin. That's how I made my whitelist in the first place. I agree that an exhaustive list is a good idea, and you're welcome to undertake that task; I just don't know of any easy way to do it (all I said), so I'm not personally doing it.

Neither of those include any of the BAF_ stuff or the stuff created specifically for DayZ, and neither of them are particularly easy to parse into a usable list for this purpose.

I've looked into that. If it were easy, I would have already done it. It's hard to get a list of only items possible to be in one's inventory, so I've just been using my RPT scanning method, combined with the whitelist, to make the list.

Omaran: As Hohlraum said. kilz: Wrong forum and thread. Try here: http://dayzmod.com/forum/index.php?/forum/30-new-player-discussion/

ItemRadio isn't unique to DayZ, so Rocket didn't add it, but also, it's not in any spawn lists, so it hasn't been added in that sense either. I've heard that at one time (before I started playing in early June), it was in the game.

Everyone subscribed to this thread just got emailed your rcon password, worsin. I highly recommend you change it.

I had 9 dayzPlayerSave entries last night in a few hour period, all kicked for hacked items, in addition to a few disconnects. That does seem a little low, but it's doing it.

M4A1_AIM_SD_camo and M4A1_HWS_GL_camo are both legitimate.

I've updated my bad item list and instructions with the most up-to-date stuff. Bad items added: 20Rnd_9x39_SP5_VSS 8Rnd_B_Saiga12_74Slug ARTY_30Rnd_122mmHE_D30 BAF_L110A1_Aim BAF_L7A2_GPMG G36A_camo G36C G36a M240 Makarov_kobra SEARCHLIGHT SVD_NSPU_EP1

It's not information I'm allowed to share in an open forum. For more information, get access to the #DayZ-admins channel on irc.gamesurge.net (password probably findable via forums or Google).

Thanks to BI Developer Dwarden's help on the matter, the buildings are now gone from the Balota airstrip (and I got rid of the helicopters several days ago).

Yeah. It has been there from the start. I thought I had a fix in place last night to ignore any building spawns coming in from the hive, but it didn't work correctly; it ignored all spawned objects from the hive.

The problem of kicking people in vehicles (and only when they hit Escape, anyway) has been fixed. These measures aren't rigorous (only a kick, not a ban). I admit I don't have perfect knowledge, obviously, but that's why we have logs we can review to improve things. It's your server of course, so you're welcome to configure it as you please, but I personally believe only logging would be a nightmare to deal with as an admin over logging and kicking.