walkerbait421

To add... HFB also has a simple update button and they are pretty quick about getting updates on, usually within an hour or so of being available. I think all the hosts do this (for slotted servers... not for dedicated, where you must do everything yourself). Logs are really hard to a) download, B) view and c) understand. After about a month I am getting the hang of it but you should know most hacks are not logged at all as they bypass battleye. Only the blatant old-news hacks and obvious stuff are really logged, and then you need to dig deep to get to the proof. I've given up on that, its just way too much work. I also agree the best bet when you find a hacker is to restart the server (with a warning of course so legit players can save/disconnect first) and they usually go on to the next one. Nametags also help, we started doing that with all players ready to fraps anything fishy, so we can get easier/quicker proof than the logs.

Yes I think its best DayZ handle it. If this is in error then it will get sorted. The server is going down not just for this event, this is just a drop in the bucket compared to the stuff we have dealt with recently. You guys are on a lot, so I'm sure you'veseen the problems. FWIW this has nothing to do with your group, just observations of a single player. You guys sound legit for the most part but I was acting for my user base (not just those I play with).

*troll bait removed*

The logs at the time of the event show that you died and disconnected a minute later (first death event). Then you log back in. 10 minutes total after dying the first time, you die again. I compared this with accounts from those who were there and it appears both your deaths were at the private camp so 10 minutes to get back fully geared and in the firefight again. Their location was basically middle map next to novy. Apparently you were able to die, disconnect, reconnect a couple minutes later, spawn, have your buddies drive to you, then come all the way back for a second assault and die, all in 10 minutes death to death? Relevant log details follow (only last 3 digits of player ID shown for privacy - note that it matches yours): ... First death .... 20:14:15 "PDEATH: Player Died *****814" 20:14:20 "DISCONNECT START: Mr. Ian ("*****814") Object: 38fe4080# 1097336: frost.p3d REMOTE" 20:14:20 "UPDATE: [38fe4080# 1097336: frost.p3d REMOTE,[],true]" 20:14:20 Client: Remote object 104:0 not found ... Second death .... 20:24:52 "PDEATH: Player Died *****814" 20:24:30 "UPDATE: [b 1-1-F:1 (Mr. Ian) REMOTE,[],true]" 20:24:31 "HIVE: WRITE: "CHILD:305:218425:[19,[10612.8,14303.4,0.0436096]]:0.534362:"" 20:24:31 "WRITE: ['PASS']" We have videos and screenshots and full logs + event excepts, all 3GB or so. In my opinion definitive proof and is why I banned. You can take it up with DayZ staff. I don't have time to bicker over this, nor deal with this crap in general, so the server goes down at the end of the cycle and you guys can freeload some other guys server or rent your own. As to the clone? Found it, right after you were banned and tried reconnecting a few times: "LOGIN ATTEMPT: "*****606" Mr. Ian" Different player ID. Was seemingly constantly respawning. As to crosshairs and nametags? An effort to deal with this and all the other hacking events going on at the time, as was clearly stated in server messages. Nice conspiracy theory though!

Hopefully your scripts log is fairly pruned so you can download and actually view it. But FWIW even with this log most the nuke hacks seem to by bypassing battleye entirely and won't be logged. You can check for "marker" string, apparently some hacks like this use a marker position on the map, so you would be looking for script code related to setting a map marker right before everyone dies. I believe the actual strings are createMarker and setMarkerPos. Also look for createMarkerLocal ["nukemarker".

Fiendlytags is bugged. Won't stick in configuration editor. When editing text to fix it, server name for this flag shows up wrong value.

And when you have proof, get ready to have to spend hours bickering in the appeals forum even before your log files have finished downloading so you can prepare your "proof" report that you witnessed on stream. Or do what I am doing, shut your server down and let them sort this mess out before you try and host again. Everyone dead on the server at least 3 times in the past 48 hours, multiple heli spawns, ESP, teleporters and ghosters/exploiters (not to mention the d/c exploiters) totally rampant. And I can't even trim my logs any more so I can download them. Done!

Yep, please avoid 755. This is the only ban we've every applied, but we are obviously ban happy abusers. More important to avoid it due to bomb, heli and teleport hacks which are going on since yesterday, but whatever.

US 755 will be shut down within the next few days for several reasons that aren't important and have already been discussed too much already. Please move your stuff soon!

Here's the deal: I don't know about this clone ordeal but things are based on GUID not name. I have what I feel is definitive proof of you hacking as well as exploiting via server log stream and video... but since you've posted details to help compare I am actively re-reviewing things (logs are over 1GB in size and having trouble downloading/viewing atm so this may take some time). In the mean time you have been un-banned until re-review is complete. Don't count on this server any more however, it will be going offline in a few days as I am done supporting all the hacking and cheating going on with little support or resources to prevent it. If I made a mistake, I'll find it and correct it. If not, the ban re-applies while the server is still on anyway.

Hi, There are a few of us admins hoping for some clarification. Sorry for the new thread but questions posted in the server rules thread have gone unanswered and I fear they are lost in the mix. Since its become a big problem we're hoping to get an answer soon. Here it is: Can we kick/ban players caught hacking in our servers, assuming we have proof? Can we kick/ban players exploiting i.e. disconnecting to avoid death, assuming we have proof via log + video? Can we kick/ban players using invalid character names (extended non-text ascii) which show up in game as blank/anonymous? And finally, if we cannot kick/ban, what is the recommended action when encountering such situations? Thank you!!!

Can you provide an example in the logs of this? It would be much appreciated. I haven't found anything that shows bullet hits/kills, maybe I am looking in the wrong place. And about this whole ordeal: Its a friggen mess. Basically you have too many players, too many servers, and an unpaid team in control who has basically no resources limited by an engine that is wide open for abuse. Until this is monetized I don't see anything changing for the better. Meanwhile I am losing access to my server and losing control over even basic admin functions. I try to see it from both sides.. I mean the devs are struggling to cope with the growth, there ARE lots of exploiting admins out there and there ARE lots of exploiting players. Instead of properly policing and taking care of the offenders (due to lack of resources) we get what we have here: a blanket assumption that everyone's bad and can't be trusted. IMO the devs have kind of given up on Arma2/DayZ project and are just babysitting it for marketing to the next paid offering that should be much better and come with the resources required to keep things in line. For now though things are just screwed. Planning on canceling my server at end of cycle too.

I've been using the M107 lately. Yes 1 shot kills, but they still disconnect and their bodies disappear immediately at the "player was killed" message. Maybe its a bug... but I doubt it, because when they are in groups their buddies are all disconnecting too. Well not all, but most.

Sorry, I had trouble finding it in that thread that server admins can ban users for this. Can you point me to it? Thanks! Obviously there is confusion as in the thread I posted indicates from staff that this is NOT something admins can ban for.

Somewhere around 75%... And about 25% server hop to teleport.

Hi, see here http://dayzmod.com/forum/index.php?/topic/32223-staff-need-clarification-on-ban-able-offenses/ In short, no, nothing you can do about this unfortunately :(

Thank you!

Agree with waiting until a restart before saving items in a tent. I like to test it first, i.e. throw a bandage or something low-value to make sure it saves a full 24 hours before I use it. Today however I had a strange issue on the new patch... Weapons got eaten (with plenty of room left in tent) as well as a hatchet, compass and GPS. Also had some (4) unrelated pistol ammo disappear when the primary weapon went away. But got 2 extra ammo of something else entirely. Something is strange, hadn't seen this with 1.7.1.5, but I am not trusting tents at all right now.

After about 20 NW airfield trips, I have yet to get any good loot from it (except from other players). For a loot mission not really worth the risk! But PVP is pretty fun there if you are looking for that (almost all are server hoppers and d/c cheaters though, be ready). Crashed heli loot is found far more often and much less risk. Heck even Stary and deerstands have better loot.

Ah, thanks. How long does this normally take? Still not getting an GUID verifies but I have seen in the log BE Master connection problems.

Thanks for the info. Any confirmations that this scripts.txt is working ok without booting legit players? Thanks again for creating/posting this!

It seems this file contain all the dayz-included vehicles/weapons so there will be many false-positives? And yes I believe the script restriction # is the line number of the scripts.txt file. I.e. 177 is ural which is included in dayz. Sorry if I'm wrong about this, just trying to make sure I understand it. Thanks for clarification.

Doing a great job HFB... loving our sever now almost 3 weeks old. Thanks! There is one problem that seems to be affecting us all in 1.7.2.3.... battleye is not working to verify GUID... I understand there needs to be a BE update on the server to get this working? Would be great if you can look into this...

Confirmed same problem with our HFB slotted server. I've never had to do a BE update before - there is a control panel update method that is supposed to take care of this. We usually get at least 5 or so global banned players trying to log on each day, so hopefully there is a resolution to get BE running again soon. We have enough problem with the random hackers that aren't banned.

Source? Last official server naming rule update I read (a few days ago) is very specific, and would prohibit such a naming format.