DeathJester76

The game's gonna be in Alpha for another 12 months at least, if you're upset about bugs now you better stop playing ASAP...if you don't you won't be able to play the Beta...because your head would have already exploded. So day/night time cycles got screwed up, I'm sure it's an easy fix...patience.

.

Yeah my money is on Poop as the culprit, ban him straight away.

Hey mate, Yeah this a combination of things, one someone has spawned random choppers all over the map that despite my best efforts I have not been able to manually remove. Secondly DayZ Anti Hax needs to scan for the type of effects that get logged when a heli crashes as similar events are actually hacks. This has meant that an abnormal amount of people have been banned by DayZ Anti Hax recently. Please be assured that I'm reversing the bans as quickly as I can (once I have confirmed that the ban is a false positive) which unless I'm really busy is <24 hrs. Your ban has surely been lifted by now so you should be free to play again...thanks for crashing the heli tho...that's one less on the server ;)

It's possible to put a hacked in SUV on top of another vehicle? Well then that's totally legit...oh wait...

Yep it sure is, add his/her GUID to your servers ban.txt and go here: http://code.google.com/p/dayz-community-banlist/issues/list Start a new issue and report them. Thanks

Double post

Your best bet is to try to contact the server owners of DE 2417 as basically the 'proof' you have given is not really proof I'm afraid. Having hacked items isn't proof of hacking, it's entirely possible that those two players killed a hacker themselves and got their items, there's no proof that they hacked those items in personally. Only the server admin will have a chance to tell if they are hacking by looking through logs

Hey MissBehave, Your servers bans.txt will take IP Addresses as well as GUID's In the space where you'd normally put a players GUID instead put the IP Address similar to: <IP Address> -1 Die in a chemical fire hacking scum Problem solved :)

Hey again Nevdawg, Yeah looking through the logs mate I can see all the shenannigans of last night plus the heli crash, looking at the remoteexec.log I can see a bunch of heli crash events with your's being the only one that DayZ Anti Hax took any notice of: 11/9/2012 11:23:14 AM - Banned 1252c3b3aa17becc64b7379a2a90ccb7 on pass #352 for Remote Code Execution (08.11.2012 17:59:27: remoteexec.log) I've since removed you from the servers ban list and you should be good to play again. PS it was Hero Medic, that was the guys name

Hey Nevdawg, Got your PM mate, will check what's happening in a few hours when I get home from work (I'm in Australia) and see what happened (I can't admin my server from work unfortunately) DayZ Anti Hax is running on our server however it shouldn't be banning you for the events that are logged during a heli crash. I've seen plenty of them in the logs before but no bans coming from them...most strange. I remember your name from my log checking session last night, the usual round of retarded pay-for-hacks kiddies bragging about how awesome their hacks were in direct chat (that i can see every word of)...now what were their names...ELIAS and something underscore 'Medic' were two of them...if I didn't have to ban and report to the comminity ban list 7 other people yesterday I'd probably remember their names in full. I saw that you weren't hacking but still asking for stuff to be spawned in for you/taking items from the hackers...tsk tsk. Silly, yes...bannable, hmm not really I guess. I'll check it out tonight as i said and see what's happening, if there's nothing new in the logs (like you decided that those boys hacks were way cool and you had to get your hands on your own) then you'll be unbanned pretty quick, else the ban stays!

You accidentallied the whole server?

HI Loque, As per my reply in your other cheat reporting post can you please go here: http://code.google.com/p/dayz-community-banlist/issues/list Start a new issue and add the details to the report, if enough reports are submitted then he will be Community Ban List banned and will be unable to play on all DayZ Anti Hax enabled servers. The more reports given the quicker this guys GUID will be banned. Thanks mate.

Hi UmadBro, Thanks for the cheat report, even if you don't use DayZ Anti Hax on your server can you please go to: http://code.google.com/p/dayz-community-banlist/issues/list Start a new issue and report that user so that he/she can be added to the Community Ban List, once enough reports from that GUID have been submitted and their hacking proven across several servers then they will be added to the Comminity Ban List and will be unable to play on servers who use DayZ Anti Hax. If everyone could do this it would really help out with hacking on DayZ. Thanks mate.

1. Ban them from your server. 2. Go here: http://code.google.com/p/dayz-community-banlist/issues/list 3. Create a new Issue and add the GUID and Log excerpt and report them

You're right, all the fixes in the patches should be tuned to accomodate for hackers

Log in, run around for 10 minutes (without getting killed), log out, log back in, get yourself killed, see what happens? Dying Solo: 1. Dump gear in tent 2. Take a few zed hits till bleeding, go somewhere secluded and die, run back to corpse Dying with a buddy: 1. Give him your gear so he can run to you and you to him if you get a shitty spawn 2. Have him guard your body/gear till you run back to it

lol, i assume he meant talking about hax being discussed in chat...I've banned plenty for it myself. 'hey check how cool I am cause I can do all this stuff cause i bought these scripts from someone way smarter than me' I'm sure whoever wrote those scripts is smart enuff not to talk about it in an open chat channel anyways.

Yeah I'm sure the only thing he bought/acquired some hacks for is to give himself a new skin...hmm yeah no, although it may not be in the logs I'm sure he did a bunch of other hacking as well...banhammer!

What LVG said, Rocket never envisioned that the mod would be so huge and was never designed to take more than 40-50 people per map. With the Server-client model that the Stand Alone will be there'll be maps with 150+ people on them

Hi All, Well after a few days downtime I'd like to announce that US2979 is back online! The server is back to it's old self, connected to the Public Hive so Tent's and Vehicles are where they were before the server went offline. DayZ Anti Hax is still installed and if it banned you before the downtime then...you're still banned. There's one small problem with the Max Ping setting being a bit low (200ms) and not wanting to be set higher but I'll sort that shortly.

Hey guys, getting rid of hacker spawned buildings/vehicles is a relativly easy process...if you have the tools and the know how of course! Here's a post I made in another thread in these forums about buildings being spawned all over the map, the same fix applied for the buildings will also fix any spawned vehicles on the map, I've copied and pasted my original post below. Good luck, any questions feel free to send me a PM :) Hi guys same thing happened to my server a while back and it's surprisingly easy to fix, the instructions to fix it are: Note: you have to be running a server by your own (non managed) that is you can FTP to your server and upload files (Public/Private doesn't matter) 1. Download the following modified dayz_server.pbo file (what it does is shown on the download page): https://docs.google....Sjl0VmxoX2pTRms 2. Rename the file 'dayz_server.pbo' 3. Stop your server 4. FTP to your server 5. Navigate to @hive\addons IMPORTAINT! 6. Copy your exisitng dayz_server.pbo file from your server to your local hard drive first (keep it safe, you need to put this one back after you're done) 7. Copy the modified dayz_server.pbo file (the one you just downloaded and renamed) over the top (overwrite) of the dayz_server.pbo on your server 8. Start your server (it might take you a few stop/starts of your server before it will let you log on, keep trying) 9. Join your server and start playing on it (Battleye may kick you with 'Script Restriction #65, don't worry its just a kick not a ban) 10. Log off of your server 11. Stop your server 12. Copy the old/original dayz_server.pbo file back over the top of the modified dayz_server.pbo 13. Start your server 14. Problem solved! 15. Hang on to the modified dayz_server.pbo file in case some tool decides to do it again

Tents are safe 100% checked and confirmed personally...as to vehicles not sure as I don't have one on my server atm. Depends on how 'hacked' your server is, in my case there were buildings every 100-200 meters...ALL over the map, cities, forrest area's...middle of lakes...so in my case a few reset vehicles were the least of my worries The page you download the modified pbo file from says that it only resets vehicles that have been hacked in to unplayable area's (debug plains/middle of ocean), I assume they are safe but cannot personally tell you yes or no I'm afraid

Hi guys same thing happened to my server a while back and it's surprisingly easy to fix, the instructions to fix it are: Note: you have to be running a server by your own (non managed) that is you can FTP to your server and upload files (Public/Private doesn't matter) 1. Download the following modified dayz_server.pbo file (what it does is shown on the download page): https://docs.google....Sjl0VmxoX2pTRms 2. Rename the file 'dayz_server.pbo' 3. Stop your server 4. FTP to your server 5. Navigate to @hive\addons IMPORTAINT! 6. Copy your exisitng dayz_server.pbo file from your server to your local hard drive first (keep it safe, you need to put this one back after you're done) 7. Copy the modified dayz_server.pbo file (the one you just downloaded and renamed) over the top (overwrite) of the dayz_server.pbo on your server 8. Start your server (it might take you a few stop/starts of your server before it will let you log on, keep trying) 9. Join your server and start playing on it (Battleye may kick you with 'Script Restriction #65, don't worry its just a kick not a ban) 10. Log off of your server 11. Stop your server 12. Copy the old/original dayz_server.pbo file back over the top of the modified dayz_server.pbo 13. Start your server 14. Problem solved! 15. Hang on to the modified dayz_server.pbo file in case some tool decides to do it again

Hey guys n gals, just letting everyone know that US2979 is down at the moment and we are working with Survival Servers to bring it back online. We haven't stopped paying for hosting, it's just having some difficulties at the moment, should be back up in the next day or so