Vipeax

Uh... curious where you found that ID. And yes, slowly digging through in reverse.

It's fine if it just has the normal scope.

Magic.

There is no ETA at all for now. Till you hear otherwise, pretend they don't exist.

First. Once it's out of Alpha everything that's not needed can be taken out, what is needed can be optimized for DayZ and the DayZ code itself gets a good cleaning obviously.

If* beta allows.... No plans so far for that.

http://dayzdb.com/map If you want a more... funky one.

Only 1.

All the mails that have been sent were quite... uninformative, but I will see upon it that this will be dealt with within 24 hours.

I never played ARMA or ARMA2, if you are generally speaking someone who is above average to good in a lot of video games, you will manage without. Otherwise, tutorials... yeah.

Yes.

He doesn't say: ban everyone who you don't like. If it really makes you feel happy I can see about locking threads that aren't helping when it comes to this.

The problem with this situation is that neither side can really prove they are right or innocent. To keep this a bit simple I will tag Admin as A and 1 player as X, another as Z, Z is a friend of A. Y is a random event that can be anything. I will first start with the cheesy one: A fires upon X, X disconnects, A kicks (or bans? :/) him. Z fires upon X, X disconnects, A kicks (or bans? :/) him. Now the other possibilities: X fires upon A, A is a lamer and disconnects. X can't proof a thing. X steals stuff from the camp of A, A crashes the server and will say: was just a crash man! X steals stuff from the camp of A, A kicks X saying he disconnected. X sees A, A kicks X saying he disconnected. X fires upon A, A kicks X saying he disconnected. X does Y and A kicks X saying he disconnected. Now say A is not actually playing, but contactable: X fires upon Z, Z is a lamer and disconnects. X can't proof a thing, A ignores it as he trusts Z. X steals stuff from the camp of Z, Z says to A that the server is unstable. A restarts and X has to deal with it. X steals stuff from the camp of Z, Z tells A that he was saying racistic comments and A kicks X. X fires upon Z, Z asks A to kick X, saying he disconnected. X does Y and Z asks a to kick X saying he disconnected. So, all in all both sides can be abused. And it actually means an admin has to be really reliable to trust him on not abusing his abilities. A few days ago I had a character that was really old with plenty of murders (and can be found on multiple leaderbords still) etc. Now some drama happened so I had to fix some stuff. I disconnected and told my friends to just go ahead. I log back in and a random guy with a winchester was now like 20 meters from where I logged in. I got shot at and could have disconnected or whatever, but obviously didn't (even had plenty of time to do so, say 8 seconds at the least). My friends saw him and fired upon him, he disconnected and toke my stuff with him. Now I could have done a shit load of stuff, set my gear back, ban him, reset his gear, set is character as death so he respawns etcetcetc. All of this was recorded, so proof was not an issue, so in theory I could decide whatever happened in this situation. In the end I just said said to myself: deal with it... All in all the biggest problem with this is that admins are abusive (not all are, not saying the people in this thread are, but trust me: they bloody damn are), it's unfair for others as they don't get the same treatment for disconnecters and proving it is a bitch. Personally I don't recommend it, but I also don't see a server randomly being blacklisted for it. Normally I can make the call on these myself, but due to the possible impact I will be "kind enough" (whehe) to ask the person with the final call on DayZ as a whole, but I just woke up, so that's something for later as I want breakfast before dealing with evil himself. And Disgraced, till it's possible to physically lock out people at say 3 to 5 slots remaining, that is just not going to happen. I've said it before: kicking people now, whatever kind of check you implement to decide on who is getting kicked, can ruin their characters badly. This is not BF3 where you spawn again with the same gear at a safe place. Here you spawn in the middle of the airfield if you are unlucky.

I will quickly add that BEC is supported as it makes servers a lot more stable. It's quite obvious when a server is manually locking or when BEC does it, and whoever complained (quite a boring thread, sorry), you are wrong. Have a nice day.

There is less than 9 spawn location for fixable heli's and they are not spawning at all at this time.

The AS50 does everything the M107 does, but better.

DMR at night (with NVGs), AS50 during the day.

Kinda cruel as you don't have to do any effort to determine the range. M107 + distance on hover = D:

300 is probably beyond what you should expect, but going stand-alone with an optimized (stripped) binary it will certainly be able to run more than it does now, as it has less work to do.

No, your RAM handles "content" changing a LOT better than a harddisk or SSD.

Running C++ code to do that isn't really an issue, but you should know this is as good as spyware and would go beyond Blizzard's Warden --> legal drama.

I'm sure the title and the content of the first post promote having a look at it... And nope, whitelisted just fine. What does telnet show?

Aren't they open? They lock themselves to throttle spam, but it should be unpassworded... I had them passworded while trying to fix them as you don't want to enter a server to get stuck in loading.