Magotchi

Yeah. You make it go away by following the instructions in the error message: "You are *required* to use the date.timezone setting..." That's in your php.ini .

1. http://dayzmod.com/f...rm/#entry752302 "...so I think banning someone for it is not the right thing to do at the moment;..." That's a far cry from a rule. 2. http://dayzmod.com/f...rs/#entry446536 Rocket is saying players won't be globally banned for having hacked items.

Hmm. Its About page doesn't say that it bans or kicks for hacked weapons. Is that a recently-added feature?

It's of course up to each admin what they include or not in their whitelist. The default in the script just has every item that's actually valid.

That could be done, of course, but it would require a database to be kept of hacked item infractions by GUID, and it would require direct BattlEye RCon interaction via the script. I'm not interested in doing it, but it would probably be a worthwhile effort for those who would prefer it to instantly banning.

http://dayz-communit...ters/setpos.txt Please show us where the DayZ dev. team said this; I don't believe they did.

I hadn't heard about that. I do know about http://dayzmod.com/forum/index.php?/topic/93007-howto-use-publicvariablevaltxt-to-auto-kick-players-with-hacked-weapons/ , though. Hopefully any new solution would use a whitelist where possible rather than a blacklist.

I've never banned anyone for duping or for stealing a helicopter, so you must be remembering a different server.

That's the reason I'm always willing to unban for these, if appealed.

That's your opinion. I think it's a great idea.

Setpos.log records instances of people using the "setpos" scripting command (teleporting). Normally most, if not all, entries in it therefore represent hackers, but I don't know much about Lingor, private hives, or modified mission files.

For those using another publicvariableval.txt already (like the DayZ Community Banlist version), I added this to the script that downloads that file on my server to merge them, after the line that downloads the fresh DCBL publicvariableval.txt: copy /b publicvariableval.txt + publicvariableval-local.txt publicvariableval.txt publicvariableval-local.txt contains Venthos' entries, with an extra line break at the top to make the merge work correctly. Update: I'm actually using the following in my publicvariableval-local.txt, though, based on the list of personally-detected invalid items I provided, and it seems to work great: Moved to Google Code project.

That's incorrect. You just need to run the "loadscripts" and "loadevents" commands via RCon (via BERCon tool, Battleye Extended Controls, etc.).

Tinoshi: I looked at my ban list, and I don't see the name "Tinoshi" anywhere in it. If you were actually globally banned, I didn't do that, I have no control over that, and I can't help you, but if you were banned from specifically US 303, and it said it was for hacked weapons, if you provide your in-game name you were using at the time or your BattlEye GUID, I will unban you, but please don't use hacked weapons in the server. PhilB: Every popular server is a hackfest, especially when full. It's the name of the game right now. BattlEye's ability to detect and log things keeps getting better, but for now, it seems the hackers are always one step ahead. I try my best, and I'm always on top of the latest methods for keeping the hackers out, but there's only so much that admins are even capable of doing at this point due to the logging bypass methods that hackers are still able to use. Also, DayZ Wiki and DayzDB are both good sources for what equipment is valid and what isn't.

Sounds good. I'll look forward to getting sniped by you. :-)

Unbanned. Have fun, but please don't play with hacked weapons. Thermal AS50 might as well be godmode.

Hackers: Maybe. It's hard to catch all but the dumbest of hackers these days, due to BattlEye bypasses and hacks that don't rely on scripts. On the gun: No: http://www.dayzwiki.com/wiki/M4A1_CCO_SD

You're unbanned, but please don't use hacked equipment on the server.

Yeah. It comes with the territory. Nothing in the logs to even diagnose it, either. :-( I got killed too, right before it happened.

They're backwards-compatible, but servers can require a minimum build, and until tonight, I've always required the absolute latest build. For several days, though, DayZ Commander was 3 updates behind, and Six Launcher was (still is) weeks behind, so that really put a dent in population. On a restart earlier, I had allowed 96493, so that's why you got in with it. It was at the restart 26 minutes ago that I lowered it further to 96061. EDIT: I'd say it worked pretty well, lol.

This is kind of a side-note, but I just changed the server's config. at the reboot just now to allow people with 96061 to join, even though it's running 96584. I think I'm going to start doing that, allowing for people with the latest version that comes with DayZ Commander or Six Launcher to join. Hopefully that should get it rocking again, population-wise, as it always had been until a few days ago.

Nice.

It's frustrating that people in this thread are just taking it as read that it's against the rules to ban for hacked weapons. Rocket has never said, that I know of, that admins are not allowed to ban for the possession of hacked gear. He only said that players won't be globally banned for possessing hacked gear.

I accordingly didn't waste any time unbanning, and if it becomes a problem, I'll add ItemRadio, TruckHorn, TruckHorn2, CarHorn, and BikeHorn to my whitelist, but so far, a large majority of people with these items already have other hacked gear in their inventory.

A hacker can't force anyone to join a server with hacked equipment.