kicktd

I wear a Ghillie and don't have any inventory loss when I put it on as of 1.7.2.3 and don't have any inventory loss when I log out and back on either. So no problems with ghillie suit as far as inventory goes for me.

I wasn't camping the supermarket, I was gathering supplies when I noticed someone was in there with me WITH WEAPONS AND EQUIPMENT I planned on looting. I have a grand total of 2 murders now, so I guess that makes me so evil I've killed 2 people! I don't camp anywhere actually and the guy surprised me more than anything and for all I know was a server hopper as I had closed all the doors and none of them were open so chances are this was just some server hopper. So go back to your care bear fantasy land and alt+F4'ing every time you die because you can't handle being killed. If you don't like being killed go join an empty server and see how much fun you can have!

Non-PvP servers at this stage of the alpha would be useless honestly. It's WAY too easy right now to just loot towns without having to worry about the zeds, so what's the point of non-PvP servers? Yeah sure I mean I understand your point not everyone wants to die to other players but I mean come on, at this stage PvE is so easy it's like taking a stroll through the park with no risk invovled and nothing but reward. I don't even fear the zeds in their current state, I feared them more back in 1.7.1.5 and below than I do now. Right now I can crouch run through a town and aggro 3 maybe 4 zeds total the whole time I'm in the town. I fear other people more than I do the zeds, just like I would in a REAL zombie apocalypse situation. Yeah I'd worry about the zeds, but I'd be more worried about the other people roaming around gathering supplies who WILL kill for it.

rocket has said himself PvP IS PART OF THE GAME, get use to to it and don't force your "I'm gonna alt+F4 because you killed me and now I'm all sad" views on the rest of us. This person wasn't a starter n00b and was someone with a gun and loaded out. I don't kill people I see without weapons etc. and I'm not going to walk up to someone WITH a weapon hoping they won't shoot me first while I try and "steal" their stuff. Get use to it, in a world where things have gone to shit, people WILL kill other people for stuff, even if it's just "pain killers" etc. Disconnecting to avoid death/not allow anyone to loot your gear is to me an exploit and a bug and needs to be fixed. I'm decked out in gear but if I get shot and die, am I going to alt+F4 or rage quit to avoid the person who killed me from looting my body? NO. I'm going to take it like a man, respawn and start over. That's ALL PART OF THE GAME, force quitting so no one can loot your corpse is not part of the game and is an exploit/bug abuse. I've died to other bandits tons of times and I just accept it as part of the game. That's how it is. If you don't want to die to another player, well there is always single player or you can go play around in the editor/armory if you want to not die to another player.

Can we PLEASE PLEASE PLEASE get a fix for bodies disappearing if someone logs out/alt+F4's as soon as they die? I was in the main part of a market with NVGs at night, see a flashlight sweep the glass wall in front of me and I know someone is in the back room area, sneak back there and see someone looting, put 2 SD shots into their head, they drop down dead, murder count ticks up 1, dead player flies sound...body sinks immediately into the floor as the person alt+F4'ed out as soon as they died so no looting of that person for me! I thought this was suppose to be fixed already? Sucks to kill someone just for them to be able to alt+F4 out and not allow you to loot their body.

Dear rocket: Can we get a fix for the "I'm a sissy and scream or whimper like a girl every time I shoot a gun" sound almost every time you shoot a gun? It's annoying to hear my guy whimpering and sometimes moaning in pain just from shooting a gun. Also today something interesting: was going shopping at the local supermarket and took care of some zeds along the way and apparently one hit me enough to do some slight damage (like 400 worth of blood loss) and my guy kept going every now and again "f**k that hurts" or moaning out in pain etc. and then...some of the zeds started doing the same thing, at first I thought another player was injured in the small town I was in but combed the area and nope, as I was leaving I heard some zeds "speaking" in the field complaining about it hurts and speaking with a British accent. But yeah please fix the "I'm a sissy" sounds whenever you shoot a gun, it's annoying, distracting and quite frankly makes my character sound like a cry baby every time I shoot a weapon.

Ghillie suit is fixed as of 1.7.2.3 lost mine with the 1.7.2 update, .2.3 came out and put mine back on and all is well. It will show you have killed no zombies etc. after you put it on but just disconnect and reconnect and your stats should reappear, so feel free to wear one, just DO NOT go back and play on a 1.7.2 or .2.1 (not sure about the .2.1 version) server and you'll be good. But yeah I've had a UAZ get eat by the server I normally play on while my ATV was fine. It's just a current bug in the server side of the code and not much we can do about it until rocket nails down a fix sadly :(. So yeah 3 things not to get attached to in DayZ: Tents, Gear and Vehicles lol cause at some point either someone steals them, raids them or bug eats them.

I swear when I see someone running from a horde of zeds THIS is exactly what it looks like and reminds me of. I can't help but think of that song every single time I see it, and I see it more often now.

Same here. Looks like a bad beta patch or servers MUST be running the same patch version :(. Just reinstall 95054 and you'll be good. No need to delete the beta folder or anything, when you install a beta patch it overwrites whatever is in the beta folder no matter if it's an older version or a newer one.

Playing on the same server the cars are on? Cars are server dependent. Also explain what you mean by a couple of tests? Currently there is a few bugs with vehicles and tents, sometimes vehicles do magically vanish but usually it's a per server issue (don't know why) but are you sure you're saving them before disconnecting? I usually hit the Save Vehicle_name_here option a couple of times before I quit just to make sure.

Yeah if it ever asks for a password just keep refreshing and you'll get in eventually. It's a way to prevent the server from being over run and going down, but if you keep refreshing you'll get the download :).

Are you stuck on the loading screen? If so you might need to update your BattlEye files, link to download: http://www.battleye.com/download.html explains how to update them. Also if you're trying to join a server that is 1.7.1.5 or below it will no longer work. Has to be a server running 1.7.2 or above.

Beta Patch: ftp://downloads.bistudio.com/arma2.com/update/beta/ARMA2_OA_Build_95054.zip Latest BattlEye dll's needed to use with latest patch:http://www.battleye.com/download.html Also you can no longer play on any server that is running a version of DayZ that is 1.7.1.5 or below, it has to be 1.7.2 or above other wise you'll just get stuck on the loading screen no matter what patch or version of the BE dll's you use.

Click the more details or the "To see what this error report contains click here" and see if it mentions BEclient.dll anywhere, if it does you need to download and install the latest battlEye .dll files.

Yeah I've noticed this. I was shooting zeds with my M1911 with other zeds milling about 20m or closer (according to dayzdb.com the M1911 has an audible range of 59.4m) and they didn't react to the gunshots at all unlike previous versions where they'd uh..swarm if they were within "ear shot" of the gun, but now they only would react if they saw me. I haven't tried any "bigger" guns, well I have my M4A3 CCO but I use STANG SD ammo with it.

If you're trying to play on a 1.7.1.5 server (I was going to play on one just for the hell of it) and downloaded the correct BattlEye dll's and patch etc. etc. but guess what? Yup, stuck at "loading". Odd I say. So I go back to 1.7.2.3 and sure enough it loads fine any server running 1.7.2.3, so that got me thinking, I loaded up 1.7.2.1 and joined a 1.7.2.3 server to see what was up, loaded up fine and gave me the "You're running X version, server is running Y version" black screen BUT IT LOADED FINE. So conclusion: latest BattlEye update has borked any version of DayZ under 1.7.2 that means 1.7.1.5 and under no longer "work" properly and chances are you'll get stuck at the loading screen if you try to join one of the 1.7.1.5 servers for those not liking anything in 1.7.2.X at the moment. DEVS CAN YOU CHECK INTO THIS WITH BATTLEYE AND SEE WHAT IS GOING ON?

You're lucky yours disappeared. I went into a shack that was empty, started checking out loot, look up and a zed had spawned right in front of me and started attacking me. =\

Was really looking forward to some Bar-B-Q and shot a cow as it mooed at me and started walking away, soon as it hit the ground dead *poof* it disappeared. Are we back to animals despawning upon death again? :(

True, but was just posting this up for those who might be trying to play on a 1.7.1.5 and are getting "stuck". Just wanted to give 1.7.1.5 a try again to see what exactly has changed between it and 1.7.2.3 (liking the new zeds so far, so random) but yeah, just stating for some who might be getting stuck, could be they are using an older version of the mod or trying to join a server running an older version, which of course now doesn't work and I know absolutely why ;) . BTW just saying you guys on the staff/dev team are doing a good job so far and you have my :beans: .

Yes. Server hosters are being "forced" (and I use that word loosely here) now to use the latest beta patch(es) so best get to downloading the latest beta patch and that will fix your problems.

Was playing fine, logged out came back about 20 minutes later, and now I'm stuck on the "Loading" screen no matter what server I try to get into. I've tried the reinstall battleye trick, reinstall the latest beta patch etc. etc. still stuck on loading. I've noticed a lot of these threads and some type of official word on if this is a Battleye problem or what would be nice....sucks not being able to join ANY server at all. I tried rolling back my battleye for 94876 but the one on the battleye download page is wrong and crashes ArmA 2 when you use it *sigh* so I can't roll back to play on any "older" 94876 servers and I can't play on any new servers. WTF?

I'm running 1.7.2.3 and some servers will save my position where I log out but a lot of them for some reason don't so I always log back in at the same spot every time. A bit annoying especially if I'm far away from where I was at and want to continue in that area later. So far seems like only 1 server is saving my location properly, the rest don't and I don't want to server hop just to save my position. I don't know if this is a hive issue or what, but quite annoying non the less. I know it's not exactly the same as being sent back to another location as you're playing but it's pretty close as far as position saving goes *sigh*.

Yeah you're one of the very lucky few. I logged in with my ghillie, lost my ghillie, my inventory and guns. Tried to put another ghillie on and ended up in the ocean with broken bones and bleeding to an almost instant death...was not a pleasant experience in the least.

NO it's not safe until the hotfix is out. If you login with camo / ghillie still with 1.7.2 you'll lose inventory and gear, also rare chance of death.

I'd be down with that. If everyone had to start fresh hey that's fine by my book, but for people to have to start over again because of camo/ghillie suit bug is silly. Honestly I think EVERY major update everyone should start fresh again. This would eliminate the cries of people on here saying we just want out lootz back, when really we just want stability and if that comes with a database wipe of our chars every major update so be it I can be down with that, but I can't be down with losing my equipment right after installing the new update and just logging in for the first time and insta-death. I don't care about my loot, I care about the dev team practicing GOOD practices when it comes to these updates. Yes we are testers and yes the game is an open alpha and we should be glad for that, BUT that doesn't mean the dev team can't take time to have some good common sense practices as far as a plan for when a major update comes out, as it seems now it just seems like rocket does the coding maybe some general testing is done and the update is pushed out the door without any plan on what to do if things go sour. I know how databases work and how programming works and no it's not as easy as pressing a button, but it's also generally a good practice to keep backups IN CASE something happens. My argument IS valid no matter what stage the game is in, hell even making programs when you're alpha/beta testing you always make backups JUST IN CASE, same with websites and their databases. I fail to see why asking their team to make a backup of the database is not valid? To me from a programmers stand point it only makes sense. But hey, that's just me and yes I've already found what loot I lost again but like I said loot isn't the point. The point is this update was in closed testing for 2-3 weeks, was released with MAJOR bugs right from spawning in causing equipment loss and death (thus losing tents also) as well as statistics etc. which should not have happened for something that was in CLOSED TESTING for this long, especially something THAT obvious. Last minute code changes that weren't checked might be the cause, who knows but my point is still valid. Backups are essential. Why do you think rocket made one the Saturday BEFORE the update was suppose to be released 2-3 weeks ago? So again explain to me exactly why it's invalid to have a good practice of keeping a backup of the database before a major update to fall back on in case things go sour? Oh yeah that's right, the answer will always be "because it's alpha!", well sorry that's NOT an answer, just an excuse.