Uncle Gapey

These issues are due to Arma2's shit code. DayZ isn't at fault.

It probably isn't the admins doing it. Everyone connected to the game has the power to teleport and kill everyone else. It's the Arma2 engine.

Oh, and here's a guide: http://www.overclock.net/t/804451/guide-stripping-w7-install-disc-for-benching

You'd likely have to upgrade that PSU first. I'd look at an OS reinstall on your laptop, tweak settings on it, and you should definitely be able to achieve 30+ FPS. Make sure vsync and "post-process effects" (or whatever it's labeled) are turned off. OS setup and tweaking can drastically improve gaming performance. Go here to learn more (the product is free): http://www.rt7lite.com/

Save it each time you change its contents. I have tents that I put down over a month ago that still have all the gear in them. They persist through countless deaths.

That's reactive and requires action from multiple people. Need to mend the broken parts, not just bandage them and take morphine (her her).

Many of the ideas we are discussing would only require a text log file. I think you're likely correct. Thing is, Rocket is currently the #1 reason people are buying this old game. DayZ might've sold more copies of the game than the original content did - I have no idea. The point I'm getting at is Rocket has constant interaction with the Arma team (according to his interviews, etc.). I would (perhaps erroneously) assume that his opinion and requests carry a certain amount of weight. The Radio Chatter is constantly full of hax reports. You can see where I'm going with this. Can't wait to hear the final word on Rocket's engine choice.

BobaFett's trainer. It is what absolutely ruined Diablo I and then Diablo II when he released an updated version for that. I quit playing D2 after my lvl 80-something hardcore sorc (if you die, you die - no tents or vehicles to save your gear) was killed by a lvl 7 Druid right outside of town. His lvl 7 raven hit me once. Ironically, the Arma2 engine fucks up in the exact same way the Diablo engines did years and years ago - the code trusts the client. Really, really stupid. Hax will happen anyway, but when this associate-in-game-design mistake is made it really opens the door for the shit storm. Arma2 took it a step further and allows any client to run scripts that affect the entire connected populus of a server. Who thought that would be a good idea? Honestly? Please don't say the attachment line. Pretty please. It's such a cop-out excuse for problems that aren't being addressed. To me, "let go of any attachment" means, "nobody gives a shit about trying to fix these game-breaking issues." It's the same as saying, "dude, this is an alpha". I understand this isn't a finished product. I've got unfinished coding projects of my own, but believe you me if one of them had a flaw that fucked people out of hours and hours of their time, I'd be fixing that issue first. I'd at least acknowledge the presence of the issue and give status updates on getting it fixed. Ermagerd, another reddit/4chan child. Your signature clearly defines the motivation for your "just ignore the hax or go away" stance. Making oneself heard doesn't solve anything, but one combined with many others will at the very least command additional attention to the issue. Complaints can definitely be constructive, especially in the Cheat Reporting forum, where we are now. Posts such as yours quoted above define worthless.

Teleport/demigod hacks in US123 today. Was with a group of 3. They teleported and killed my GF, then teleported to me (I GTFO'ed), then teleported to my friend. My friend unloaded an AK on him, which did nothing. He then started talking in direct to my pal, saying, "LOL, what're you shooting at bro?" My friend left immediately. So then we went to US125. Found a tent set-up just north of Kamenka near the western border. GF was raiding it while my friend and I ran toward her. Someone teleported to her and killed her. She made note of where she was. The 3 of us met up and ran to the camp (got there ~45m after her death). All was gravy. Raided the tents, then flattened the bastards. 3-5 minutes later we are running to Stary from said camp when a jeep literally spawns 2 feet away from us with 2 people in it. There were tents full of AS50's (aforementioned flattened tents), so we were armed to the teeth. I personally unloaded an entire magazing (10 rounds of .50 BMG) into the driver-side window, watching blood spray out of the driver's head. Altogether we probably put 20-25 rounds into the jeep. The two passengers got out as we were reloading. We confirmed at least 7 hits on one of them. Nothing. Didn't die, didn't run, just stood there and started to return fire. As he was returning fire, dozens of loud explosions started happening around us (strangely, none of them hit us). We all left immediately. Managed to all escape alive from that one. Don't feel like playing anymore tonight. 90% or more of my deaths come from this bullshit. Thankfully I can dupe a copy of my current gear into a tent so that I'm not absolutely fucked when some kid hax my face off. Well, until said kid uses his tent-locator hax and flattens it. The banwaves just aren't enough. The vulnerabilities themselves must be fixed. I'm beginning to doubt that Rocket/devs have any amount of control over the Arma2 resources that need to be fixed. Properly-written standalone DayZ now, please! Such an incredible idea/mod. Such a pile of shit for an engine.

The better question might be, "How long has someone gone without getting teleported or nuked/carpetbombed?"

Good ideas. Also need a distance check on kills. [snip] OnPlayerKilled (vars) { if (calcDistance(killer.Location, victim.Location) > questionableDistance) { haxWatch(killer.PlayerName) } [snip] haxWatch can then keep track of how many times this happens in a pre-defined interval. A 3rd-party anti-cheat that I somewhat helped to create for BFBC2/MoH/BF3 calculated shot angles and analysed them against time between kills and kill distance. It's a super effective method with the right tweaking. All is for naught if Rocket/devs don't have access to the proper resources though.

MP5A5 is the quieter gun there. 9x19mm vs. 7.62x39mm is the comparison - I'd definitely stick with the AKS-74 Kobra though. It's more powerful and I really like the Kobra sight.

"Yeah, Kent is narcoleptic, but he was a CareFlight pilot for 20 years prior to the outbreak. We keep a bottle of No-Doze handy for the longer trips. Oy, Kent, you take a pill before we lifted off?" "Whassat!?" "DID YOU TAKE A PILL BEFORE WE LIFTED OFF?" "Ah, 'course mate. Here, you need one?" "Nah, I... well, yeah. Why not." ... "Kent, these are antibiotics. Are you fuckin' with me!?" "..."

This made me >: That's a fantastic idea. Just give folks some sort of debuff when they take any kind of damage. If you log with that debuff, you come back to gender select. In fact, if the "takes damage" and "disconnects" events are currently logged to the server log, I could write a simple parser that would read this info then issue any server-side command. This is how all BFBC2/BF3 server tools work.

It's safest to kill everyone not in VoIP. Kinda fun too...

This!

Hatchets, wood, and cans are going to be common items to find in farm-type buildings. You guys might want to check out residences and whatnot. You might already know all of this, but there are also many third-party maps that show loot/vehicle spawn points, the %chance for certain items to drop, etc. http://dayzdb.com/map The above is for folks claiming they can only find cans/hatchets/wood. OP's issue seems to be different entirely.

If you've been treading water for that long, everything but your sidearm and toolbelt is gone anyway.

It's honestly just my preference. There are strong arguments for both sides of the debate on this topic. In my opinion, nobody should be banned for using available functionality in a game (that's in a game, excluding third-party software and hax, scripts, etc.). To me, dupers should not be banned, nor should griefers. If it isn't an intentional part of the game then I feel it should be handled properly via hard-coded restrictions and abilities (inabilities?). I think that telling players "don't use this in-game functionality to your advantage - we'll fix it eventually... maybe... go away" is more immoral than the people duping gear in tents. I personally make one copy of my gear (most of it anyway) in the same tent each time I upgrade a piece. If the teleportation/nuke/etc. exploits weren't the #1 cause of my death, I wouldn't do this. Back to the exploits and hax. According to the admins of the servers I play on, there is no way for them to tell who killed who. They don't have restricted access to their servers either - they literally remote-desktop into their server instance and have full access to all files. A step in the right direction would be to allow admins to see death logs. How else will they know who to ban when 45 people all die at once? There is much info that, if presented to admins, would potentially cut down on hax use. Sudden location changes (the teleport hack being the worst one)? Servers are already keeping track of player locations somehow. So something like this might help immensely: The above would need refinement (what's the current server-side player-location polling rate versus how long it typically takes you to die when a haxfag teleports you?), but it's better than nothing. It ultimately comes down to how much control Rocket/devs have over the server<->client code. Again, just being able to browse death messages would point a very obvious finger at who's screwing around. A full 50-slot server is teleported to the NW airfiend and everyone who isn't quick enough with Alt+F4 gets killed. One person is alive and perfectly fine, and he joined 5 minutes prior to the teleport? Bingo. Sandbox games like this are my favorite. I love APB, EvE, etc. Killing nubs on the beach, especially now that respawn was taken out (which was a super terrible idea to implement pre-exploit-patching) is certainly an asshole thing to do though. I agree with ya there. That said, from a realism/RP perspective your character has no idea what that nub is carrying in their pack (this is a pretty lame justification, but think about it for a moment). Also, that beach nub is my direct competition - I'll be damned if he gets to the supermarket and grabs the tent before I do! Again, these aren't great justifications. I just don't think anyone should be banned for poor sportsmanship. I also feel that it adds a level of "oh shit!" when you fear for your life from the get-go. Let's face it, the zombies are difficult to shoot given their crazy chase-pathing, lag, and other bugs, but they are by no means threatening. Just run and you'll never get touched? I like the extra threat of players. In the end, hax/scripts/3rd-party shit needs to be fixed before anything else is done. Then, in-game exploits need to be fixed. Then, after the integrity of the game experience has been solidified, new features can be added/tweaked. My guess is that Rocket/devs complete lack of noticeable action regarding hax is due to one of the following: 1) They just don't have access to the code that needs to be modified. 2) DayZ is simply being fleshed-out as a concept for now, using the Arma2 engine as it's currently the best/easiest choice. No resources are being put into the war against hax, as DayZ will ultimately be a standalone, or a mod for another game/engine that will have its own unique set of vulnerabilities/exploits/hax. Said resources would thus be "wasted". 3) They honestly feel that game-ruining hax are a rare occurrence (which would be complete ignorance, and I like to think Rocket/devs are intelligent fellows) and not worth the time nor effort. Thing is, there's no guarantee that DayZ will ever be anything but a great Arma2 mod. I want my current favorite game to be nice and playable now though!

Just click respawn. Oh, they took that out before the teleportation exploits were fixed. Guess they didn't think that out very well. Starvation/dehydration is sadly your best option.

As I understand it, you need to physically approach a city/building for loot to spawn there. This helps to negate the advantage of, say, running to the back of a supermarket then hopping server-to-server to check loot. If you server hop and load in to see loot and zombies then another survivor is likely nearby.

This isn't a proactive solution, or really a solution at all, but definitely a step in the right direction! At the very least let the effin admins see kill data. I strongly disagree on this one. Again, definitely a step in the right direction. I think the exploits/hax should just be patched out of the game. I don't know enough about the Arma2 engine though - Arma2 could have absolute shit client<->server code that was slapped together that would have to be completely rewritten to get rid of the 'sploits. Eventually someone will read and acknowledge one of the thousands of hax posts (right?).

This has got to be the worst hack out there. Just loaded into US61 NY2 and didn't even load all textures before I, along with everyone else on the server, was killed. This has happened to me twice before - this is the third time for me to see this specific hack happen. Exploits like this will be the death of this wonderful mod. All available resources should be put into fixing the exploit/hax issues. It doesn't matter how polished and wonderful DayZ becomes if kids can join a server and instantly (NTM permanently) kill everyone there.

They should be able to take a look at the database(s) and confirm that it happened. That would take effort, of course, but given the large amount of people affected (it was a full 50-slot server) I'd hope to see some form of action. Hell, I'd rather see the kid who did it have his GUID globally banned than get my gear back. Such a shame that hax like this are even possible. This engine/mod (not sure if Rocket/DayZ devteam can even do anything about this) needs to have this shit patched out. There's no excuse for this to even be possible.

I was in there with ya, Jimmy. Here's my thread: http://dayzmod.com/forum/index.php?/topic/51202-us61-ny2-45-players-killed-instantly/ As you said, it happened much too quickly to get a screenshot of anything.