rocket

Its the dynamic weather. it will have been foggy.

You don't die. But you will spawn starving and dehydrated if you havent had enough food on you.

Fuel tanks, they are the big cylinder things usually near the fuel pumps. The pumps don't work as there is no electricity. If you find a generator however..... :P

To be fair, we haven't released any sort of "terms and conditions" for hosting - so I think any comments from me on what I think is acceptable or not would probably be the first time many people heard it. The expansion happened so fast, caution was thrown to the wind and we simply setup servers with a gentleman's agreement (going both ways, they were giving us root access!). Once we get our breath back from the expansion, such terms and conditions will be agreed upon with the hosters so everyone knows what to expect. My current thoughts on it, we tried out having passworded clan servers. The experience is different and the support effort much higher for the DayZ team - for less benefit. We simply don't have the resources to provide that kind of niche experience when we have servers jam-packed full. The DayZ team will not kick anyone from a server, even if we really need to get on for testing. I have only kicked someone once, so that a rather important person could play DayZ on a full public server. We encourage our current hosters to adopt the same principle, and I know that the EU, NY, and Tonic's US servers do not kick people even though the hosters THEMSELVES cannot get in to play. However, like I said, there has currently been no agreed code of conduct or terms and conditions for hosters. That said, we've made it clear than a passworded server (beyond initial testing or bugfixing), is a no-go. tl;dr I take a pretty dim view of people being kicked from a server to make way from priority members but we have not developed a code of conduct/toc beyond the requirement not to password the server.

Sorry mate, life is a bit... uh... interesting for me and the lads helping me at the moment. Could you send a chaseup email to [email protected]? Unfortunately, testing new servers takes a back seat to actually setting up confirmed new servers. And then theres the updates... rolling out said updates... raging on the forums... etc...

Could you guys email you ArmA2OA.RPT file to [email protected]? It is probably a server needing restarted, but it could be something else. This report file contains a lot of debug information that is useful for me to tell you why this is happening.

Just as an aside, I prefer the term "authentic". It's more relevant to talk about what is authentic, than what is real. Because you end up in this crazy philosophical loop talking about what is real or not when playing a computer game. So perhaps, it might be best to consider replacing "realistic" with "authentic" whenever someone uses the term, because I think - generally speaking - that's what they mean. I.e. "I can't suspend my disbelief on this point because its not authentic enough." Everyone has a different tolerance for varying levels of authenticity. A classic example, the Winchester is a shotgun in game. Which, of course, is complete bollocks. I haven't had the time to change and 99% of people don't give a shit. Those that notice don't seem to mind its lack of "authenticity" because it doesn't effect their suspension of disbelief.

We're getting about an email every five minutes at the moment. Sam or Matt will try and get back to you. Unfortunately, I barely have time to hop on teamspeak with them for the moment. The easiest thing for all hosters is to email us and list any issues there - as Matt and Sam are, like me, completely overwhelmed at the moment.

Currently saving is triggered upon exit of vehicle, upon damage to vehicle. Repair saving is bugged (although in theory damage to a repaired vehicle will save it). However, there is a bug (there is always a bug). I have recoded 1.5.4 but I'm not releasing it tonight to allow for more testing to confirm it is fixed. In 1.5.4 the mechanic will work as follows: Get out triggers a position save Changing your inventory around vehicle/tent triggers vehicle/tent inventory save Damage triggers damage save Repair triggers repair save Disconnecting (back to lobby) triggers save for any vehicle/tent around you These are forced saves, as opposed to the previous method of batched saves (batching was prone to never happening due to the server getting bogged down). However, the pipe for saving is not checked for confirmation, to allow speed (think of it as UDP versus TCP). Basically ArmA2 just sends the write and assumes that it has been written. That means on a very busy server running multiple instances (NY is a classic example), it is possible (although I have been unable to verify it) that your save doesn't get processed. Hence why I've added the disconnection save as a backup.

Tail Rotor assemblies will be in before the weekend, 1.5.4ish. Vehicles are still pretty fucked at the moment, so keep your valuables on you until they are more stable.

I've found the legion guys great to deal with, although my dealing have been limited. I love their spirit of organization that is for sure. I am sure that if you take the issue up with them, they will deal with it. I'll give a general reply that my intention is that there is no tolerance for admin abuse, hence why there are no admin tools in game. Sometimes you may see, on the rare occasion, folks knocking about in soldier uniforms. Its either me or one of a couple of other people doing some testing. I often end up knocking about with just a Makarov as I tend to die quite a lot, so even I don't end up with great kit. We HAVE restarted/kicked people due to testing, or for example to provide a slot for the russian interviewers a while back. We'll always work through issues with any hoster, but where those issues can't be resolved (such as poor server performance, passwording the server, etc...) we turn off their connection to HIVE. This is too provide the best service we can so that people will, eventually, know that getting on a DayZ server is a standard experience. As I said above, perhaps its a coincidence, BattlEye still needs some configuration tweaks and it has been kicking for plenty of false positives. If you can't sort out any issues with hosters, get in touch at [email protected] (but please try resolve it locally first, we get ALOT of email).

Much of the sound will be replaced, however all updates currently are for stability and bugfixing of game-breaking bugs, people stuck at loading etc.... I suspect the sounds, except for the zombie which are being replaced with newly generated ones, will remain largely as they until Beta.

Persistent fortifications are being trialed in 1.5.4

PVP Penalty. It is activated if you disconnect after receiving player or self damage and you disconnect.

TurkeyBurgers, why are you here? posting sarcastic comments? I'm genuinely baffled as to why I seem to have caused you such an affront that you feel the need to reply to my carefully considered posts with sarcasm? If this project offends you so much, why not go do something else?

The technical term is that "tents are fucked". Its difficult balancing it all, 1.5.4 will be out soon which should address alot of the tent/vehicle database sync issues... hang in there guys. Anything important, always keep in your PERSONAL inventory!!!!

Well thats why I am asking if you can walk around on it :D

Confirmed bug. 1.5.4 has changes to attempt to address this.

If there is EVER a misquote, it is the above. You missed the /* and */ above and below. That means the entire section is commented out. I.e. it does not run.

Can you actually walk around on the shipwreck?

Just because I did not script rules, doesn't stop anyone from making their own in game. Are people so used to games shoving rules, tasks, stories down their throats that they can't handle it when something doesn't? Or would you like a world where the players actually get to do this? Not a structured and controlled environment that is "dressed up" as post-apocalyptic? I hear what everyone is saying, and yes - its cruel and unsporting when you get killed 10 seconds into the game. But that's what this is, it is brutal, it is cruel. This is not fair. Maybe you will hate this game. Maybe you already do. It is an unforgiving environment with no structure. It is up to you to decide what to do next. I would rather let the project die (and maybe it will, I accept that) than take over the role of establishing rules and punishments and structure. Instead I am going to work on the world's framework. It is up to the inhabitants of that world, you guys, to decide what kind of world you want it to be. Is this actually possible? Fuck knows. But I really want to find out, and I've got nothing at all to loose. And to be honest, neither have you because you haven't paid me a cent and I haven't been paid a single cent for any of this. So here's the challenge - just take a moment and think about what you are asking me for, with alot of these requests. Balancing, structure, rules, protection. These are what the game industry has shoved in your face for the last twenty years. Even the game industry itself can't escape it. EVE-Online tried briefly but caved in. Why? Money. They needed subscribers. I don't. This is going all the way, to whatever end that is.

As I've said before, it's always been my intention for side missions, faction development - more end game stuff that would be extremely hard to do without being grouped. However, the mod is two weeks old. While I have done some work on this, and could put something roughly in - I learned my lesson with humanity implementation. I won't put it in until its complete and ready for the inevitable bugs that a full capacity server will throw. To be honest, right now the last thing we need is more players and more publicity. If people don't enjoy the mod but maybe see the potential, why don't they take a break? Other people are enjoying it and the servers are full. Please don't take up the slots of those that are enjoying the current, barely started, state. Each weekend, I am trying to include something new and exciting, but they will be small things, small steps, so that nothing breaks too badly.

You are running the development release candidate of 1.5.3 the full release of 1.5.3 does not have diag_tickTime Server hosters need to be careful they are not pulling builds off the dev files, as these will generally only work on development boxes. Redownload dayz_code from the main box.