rocket

Poor "hive reputation", which will come to include many factors - including alt-f4 behavior, will result in a database ban. This means your playerID will not be accepted on DayZ servers, and you cannot play DayZ.

Each time they login and logout of a server, it will be logged. Once we ensure we are not catching false-positives, we will start issuing warnings to players and allow them to check their reputation on the website with the central server. Those that continue to conduct the behavior, will receive database bans.

They will leave a trail, once we have the algorithms sorted and can issue warnings/punishment... those who continue to do it will receive database level bans,

Firstly, we will do what DayZ always does... we will collect data. At the same time, initially, login cooldown will be applied (and grow) where you transfer to another server, and cooldown will be applied significantly if you try and reconnect to the same server (with an alive character). Once we have enough data, we will use that to determine algorithms that detect a players behavior over a period of time. This will allow us to then start applying warnings > punishments > database bans; to those players who continue the behavior.

Yes it would, and this would be a valid point. I'm not sure what the answer is here.

The mechanics are being tested, but it will put a "timeout" if you successfully connect too many times within a period of time.

Please do not post messages of support or abuse. Please only post your feedback from having tried the update, or any serious issues. The ideal place to load bugs is at the community bug tracker: https://dev-heaven.net/projects/dayz Please make sure they are listed to the DayZ project. Feature requests can also be made through this system. Torrent File (Full Install) Use Beta patch 94444 or above Download from http://dayzmod.com/b...Build_94876.zip if having trouble with BI site due to demand (thanks Vipeax!) NOTE: 1.7.2.2 WILL APPEAR TO BE SKIPPED. THIS WAS BECAUSE THERE WAS AN ERROR WITH THE BUILD, SO IT JUMPED TO 1.7.2.3 Build Notes UPDATE : 13 JULY 2012 Affected addons: * dayz_code 1.7.2.3 * dayz_anim 0.4 * dayz_server (server admins only) Developer's Note: * Make sure you run ArmA2 Beta build 94759 or above Changelog: * [FIXED] Ghillie and skin removal on login ( https://dev-heaven.net/issues/36666 ) * [FIXED] Arma X stuck on loading screen ( https://dev-heaven.net/issues/36647 ) * [FIXED] AKS_74_kobra classname incorrectly named ( https://dev-heaven.net/issues/36680 ) * [NEW] Server side performance tweaks and improvments * [FIXED] Infected detect players from too far away (reduced by about 20%) * [FIXED] Disconnect updates not being correctly applied (caused inventory issues) * [FIXED] Bear traps not appearing for spawn (low spawn)

Locked, new thread. http://dayzmod.com/f...ate-build-1724/

I did not make WarZ. Regarding DayZ I won't tell you anything until I actually have something: 1. Confirmed. 2. Worthwhile. 3. Backed-up with results.

Working on 1.7.2.4 Includes a first cast attempt at fixing ALT-F4. Will put up a Pending Update thread when I have an eta for release

I was just trying to lighten the mood :) The OP's opinion has long since been lost with general craziness.

Okay, how about this:

It could be worse:

Its certainly not allowed. It will become less of a problem with some of the planned updates, as the move to string updates means your chances of rebooting before a change is applied is, well, very unlikely. It is tied in with some disconnection and respawn abuse fixes that I am working on as we speak. So, it is something we need to keep an eye on and keep doing as much as we can.

I voted: I don't think Day Z needs supernatural horror but needs to be creepier (see the 'I found a radio' thread)

I don't know why, but people are assuming that I think this is part of the game. It's not. I posted in a thread that was talking about that, that META-GAMING is explicitly allowed. I.e. infiltrating teamspeak servers and groups etc... Disconnecting to avoid death IS an exploit. It will be patched out, very easily, in a future update. The update is ready to go and will be released when the Beta patch for ArmA2 is out.

Appears to be some cleanup related desync issues causing some stuttering and long initial load in times (similar to previous patches). Will look into this for a hotfix. Please keep the feedback coming guys.

Incompetence has nothing to do with the state of the build, but the state and progress of the project. It's no personal slight against me, well from my perspective, that things go wrong that shouldn't. I just hope I and others involved can learn fast enough to not make the same mistake more than once. That is the absolute best we can hope to achieve. I don't think anyone could prepare themselves for this, no matter how much money, people, or experience even. I.e. Blizzard and Diablo 3. If I was competent at this, I would already be a multi-millionare driving around in a lambo doing my best to get herpies.

I'm dealing with the pure act of coping and getting people to login right now. Exploits and other stuff is priority 2. Lets just have the mod survive the performance nightmare scenario of the next 24 hours first.

If you play 1.7.2.2, you're gonna have a bad time....

41177 characters were affected by this and have been transferred.

Those who "lost" your characters. They weren't lost, they weren't transferred due to the change in PlayerID and PlayerUID. Vipeax is going to run the transfer query for me now... this will move those old characters who weren't listed with a playerUID (string) for those who "lost" their characters.

Well, to be fair. I am incompetent when faced with the current issues. But, there are few people in the world who have had to deal with such a rapid explosion of a mod, that is part MMO and part shooter. Minecraft struggled and their central server only handled authentication. So yes, the team and I are incompetent at this. But we're learning, sometimes fast, sometimes slow. But we're breaking new ground. Not even counter-strike or DOTA had to deal with the issues we are. Minecraft hit 500k users in a year, we hit that in under 3 months. So yeah, its something of a miracle that the mod even works every minute you are playing it.

The fault of 1.7.2.2 was noone else but mine. I provided Sickboy the incorrect files. He was at the airport and he did me a favor by putting the files out, I realized too late there was an issue and then there was a delay pulling the files. So Six didn't hurt anyone, it was my fault. I'm really sorry about that, it was one of those silly little mistakes that shouldnt happen but does.

Whatever you do, if you managed to get your hands on 1.7.2.2. DO NOT USE IT. There is good reason it was not released (we started seeding it)