Magotchi

If you were banned at any point in the last month or so for joining US 303 with a hacked (invalid) item in your inventory, the ban has now been lifted. Now that public variable value detection exists in the newer BattlEye builds, along with other server-side methods for preventing the use of hacked items, I don't feel the need to ban for them anymore. For anybody wondering, nobody has told me I had to quit doing it or quit using my script; I've just found better ways to handle things.

Regarding my post for DCBL filter compatibility: I did some experimenting. I added '1 "\""' to the end of publicvariableval.txt and removed the '1 "dayzPlayerSave"' from publicvariable.txt, and every dayzPlayerSave which included any items still showed up (as they all contain double-quote marks around each item class name). This therefore means that having an entry for dayzPlayerSave in publicvariable.txt is not necessary. Sorry to mislead people in the first place, but I thought the dayzPlayerSave was necessary originally. I have so many layers of protection on my server, I don't often get people that trigger Venthos' detection, so it takes a bit of time to experiment with it properly.

Yeah. That's unfortunate, but I believe necessary, to get the best behavior out of it. When you see a value restriction matching the lines in your publicvariableval.txt, that's a hacked item kick. Edit: This is incorrect information. There is no need to add anything to publicvariable.txt for this.

http://dayzmod.com/forum/index.php?/topic/62195-server-hosting-rules/ Banning hackers is allowed by this statement. Banning hackers is allowed by this statement. Please stop arguing just for the sake of arguing. I've already had a DayZ Forum Team member give me beans for this script, and I've had another PM me just to explicitly tell me it's not against the rules. Even without that, it can't be shown to be against the rules. The only real area where I might have a problem is that I'm not reporting my hacked weapon bans to anyone. That being said, everyone that joins my server can see exactly why they were banned, and I unban anyone that asks (regarding hacked items).

You're the one that believes admins aren't allowed to ban hackers, not me.

With a statement like that, I don't even see a need to respond in full.

This only affects items that aren't in the game. It also tells a person the offending items they had that caused them to be banned every time they connect to the server and on the initial ban. The most commonly hacked-in items are weapons, and if you're not sure if a weapon is hacked, familiarize yourself with http://www.dayzwiki.com/wiki/Weapons . In real life, if you weren't sure if some crack cocaine you found was legal or not, it would still be your responsibility to familiarize yourself with the local laws on the subject. Also, I understand that people don't always realize they've acquired a hacked item; that's why my policy is to always unban, no questions asked, with the understanding that they'll try their best to not use hacked items in the server.

It's up to each admin, as they can edit the whitelist, but by default, yes, as ItemRadio is not in the game and is therefore an invalid/hacked item. VidKo: My script only bans people if they enter a server with hacked gear. It doesn't do anything about people acquiring it while in-game. Venthos' publicvariableval.txt method does kick for that, though.

Sounds pretty awesome to me. Great work.

My script (the one in the OP of this thread) automatically adds anyone to the ban list that joins the server with a hacked item. Venthos' publicvariableval.txt method kicks someone as soon as the server makes a save of their equipment to the hive (if they have a hacked item). If you want warnings, Gotcha might be more up your alley.

FYI, I found out that Gotcha actually detects players with hacked weapons in virtually the same way that Venthos' publicvariableval.txt method does. The difference is that Gotcha tells you make all publicvariable entries log to the server console (and therefore to RCon/Gotcha), and then Gotcha handles it from there, while with the publicvariableval.txt method, BattlEye can just directly kick for the hacked weapons.

I updated my post about using this with the DCBL publicvariable.txt and publicvariableval.txt. I figured it out: I just had to add the "dayzPlayerSave" detection to publicvariable.txt. Edit: I later discovered that this wasn't true. Don't do this. The linked post should be accurate, though.

Does it reload the banlist only when it detects something, every time it checks, or at some other frequency? I have other scripts that add to the ban list, in addition to manually editing it, so I liked the old recommendation of just having Bec reload it every minute. EDIT: I realized the error of my ways on my original question. The filters haven't been updated at the CBL since I started using 0.7.

What all does 0.7 do when it interacts with the server via RCon (apart from showing its advert)? Does it reload the ban list and filters? Anything else? Also, is it redownloading every filter file plus the DCBL on every log check, or at a lower frequency (as per my, zcallear's, comment about the frequency here: http://code.google.c.../detail?id=6#c4)?

I do not have M4A1_Aim_camo in the above list twice. I just doublechecked, and it's there only once.

As a start, here's a list of every invalid item actually detected on my server between August 19th, 2012 and now (using my script and its whitelist of valid items), with the number of times they were each detected, with only one count per item per player login: Moved to Google Code project. If you're wondering why M240, M249, m107, and Mk_48 are on the list, it's because the actual items that are in the game are called M240_DZ, M249_DZ, M107_DZ, and Mk_48_DZ. EDIT: Updated item list.

http://dictionary.reference.com/browse/insolence

I'm not still telling you it's against the rules, and I haven't been for a few posts now. If you just have disableVON=0, that's of course fine. I only said it's against the rules to have any sort of in-game global chat. Your admin implied you had global chat by saying that the players in the server could communicate with your team, and the only way that would have made sense is if he were referring to some form of global chat.

It was a reasonable assumption.

http://dayzmod.com/f..._20#entry871119 You've taken that quote out of context. When the post is read in full, it's obvious he's talking about the use of private hives. If he really meant that there are no rules, they'd probably be taking down the stickies about rules by now. Originally your guy said the following: As it would be pretty hard to communicate to the admins while in-game if you must be within 100-200m, I assumed he must mean some sort of global chat. If you have any chat that all living players in the game can see or hear, that's what's against the rules. Group chat normally only works in the lobby. Vehicle chat normally only works with others in the same vehicle, and direct chat normally only works at a short range.

If you edited your mission file at all, you're violating the rules: "You must not edit your server files in anyway..." If you have group set up so that everyone can hear it while in-game, then you likely edited your mission file.

Yeah. The setting is specific to the timezone of the server it's running on, so there's no reasonable default.

If you'd like, I can try to help you out with it some time. Going to bed now, though. If you give more specifics, though, I might have an idea before then.

That's against the rules: