ersan

Read above, remove the amphibious gyrocopters from the map and there will be no more crashes. Gender selection was removed from Bliss several versions ago and has not been re-added.

Yep that's what I witnessed before, my recommendation for now is to just remove the amphibious gyrocopter (it doesnt float very well anyway) - alternatively you can e-mail us to stop logging setpos and setdamage.

I've heard of this happening one other time on 2017, it may be a 2017 bug in which case we can't fix it. If the whole server locks up and people can't connect then it's probably got to do with the setpos log and when someone tries to use the 'rotate' function on a vehicle in 2017 - had to fix this for someone else awhile ago but nobody else has reported it since then.

New servers up in Washington DC and London now.

Then send us an e-mail and we can reduce it, the price is the same though. We do not send confirmation emails, if you had followed the Paypal signup process it would have signed you in at http://dayz.st/control - where you can most likely sign in now.

We posted on twitter/news feed twice, but we now have servers in Amsterdam, San Jose, Dallas, and Singapore will be up in about 15 minutes if it isn't by the time you read this. Washington DC will likely be here tomorrow and London is anyone's guess, possibly tomorrow as well. We don't have any orders in progress for Seattle or Salt Lake at the moment, so don't wait up for those.

Bliss does not support gender selection since a few versions ago, it was removed for some reason. I really wouldn't know how to go about adding it back, or if it would break everything. Theoretically there should be some way to add it back by modifying your server pbo, but I haven't the slightest idea how.

I'm actually going through the flagged e-mails right now, but thanks for being patronizing. Makes my job that much more enjoyable.

Thanks, that's very revelatory. I wasn't aware there was one that is. Adding bikey's to "your" server means that anyone on the same machine gets them added too because of how arma2's directory structure is - we either already told you no or haven't decided to allow it yet.

No other customers have complained about passwords working intermittently, the tech support rep told you to try switching ports because the only conceivable reason that could occur (aside from PEBKAC) is if you were being redirected to another server with a different password (which is still quite uncommon). My only advice would be to try simplifying your password and only use alphanumerics and to tell whoever's connecting to double check that the password is correct when they are typing it in. We do not store customers' e-mails for privacy reasons so we do not send e-mails to anyone, ever - it is customers' responsibility to follow our twitter or news feed to receive updates, and we posted the port redirection solution on twitter and on these forums several times.

I don't personally answer the e-mails unless it gets past the first two lines of support (as in they can't figure out how to answer the question). As far as I know the inbox is being kept up with quite well, your e-mails may have been marked as spam. WE didn't force anyone to change IP addresses, BI did when they introduced a moronic bug into ArmA2 code for no reason. I'll inform the support reps to check the spam box and see if there are any e-mails asking about gotcha logging. Informing your players ahead of time that you would be moving your IP/port is probably a better way to go than just doing it and expecting them to find the server again. Indeed, we now have 4 times as many dayz servers as the next largest host but we have been doing pretty well at keeping up with the support requests. See this post about createvehicle restriction #1. And no I don't believe bliss addons are being maintained anymore so it is unlikely that they will ever be fixed.

We've had some plans to do this for awhile but we have to write our own whitelist software because none of the ones out there are good or reliable enough. Another issue is that hackers can bypass BattlEye making them invisible to the whitelister, we would have to add logic to compare Gamespy with the BattlEye player lists and kick people that don't show up (which you can't do over battleye because they are invisible). And it has to be 100% reliable without crashing ever - so it's a fairly complex program to write. We have a few things we want to do before it (DayZ+, Thirsk, Isladuala, FTP access) but it's fairly high up on the priority list.

Just added support for DayZ 2017 mod, it is an option underneath the map in your control panel when Chernarus is selected. (from the release thread) DayZ 2017 is set 5 years into the future and everything is more rare and the gameplay is more based on survivalism due to the low amount of high powered weapons. Players are known to trade often in 2017 and tend to work together more due to the harsh nature of the mod. That is not to say banditry does not exist, no, people can get quite ruthless, but they are likely to kill you for food then anything else (and that might be the food you carry, or you yourself as the food). I'm sure there is some way to accomplish it through the mission/server file, but I don't have any information on that.

Send an e-mail to admin@dayz.st

There is no other solution. If your port is under 3000 it was never changed.

This is very old news and has been addressed quite a few times - one of the ArmA beta's (somewhere around 9981x) introduced a bug where when connecting to a server it will attempt to connect to that ip/port + 12, 24, 36, 48, etc. ports ahead of it. We adjusted the port structure since then so that any new servers would be on a port that does not conflict with this bug. So to fix it you have to change your port - to do this you must change to a different datacenter location and back to the old one. This will change your port and probably your IP address, so anyone who connects to your server via favorites will have to update the favorite entry. I asked my support team if they noticed any e-mails asking about lag or slow loot spawns but they said they didn't think so - they answer hundreds of e-mails a day so it's possible that they just don't remember. The node you are on (salt lake 02) has extremely low load so there should be no problems whatsoever with loot spawning (which is handled by the client most of the time, not the server, so we have no control over that anyway). I've run line tests between Salt Lake and the datacenter and everything looks OK and no other customers on that node (or any other salt lake node) has complained about any similar problems. If you are below 30 or so players when it lags the only thing I can attribute it to would be hackers or too much logging from RCon, which we can disable if you send us an e-mail (but gotcha antihack will not work, if you use that) See http://ersan.us/src/munin/dayz.st/slc02.dayz.st/processor-day.png for CPU load

Sometimes this is caused by BattlEye not starting up properly, sometimes it's caused by a hacker injecting a script on the server that runs on everyone's arma2 when they join which will get them kicked by BattlEye, either way it can generally be fixed with a server restart.

Correct, we're having quite a few problems at the moment due to the rapid growth (we have over 1700 customers now) if I'm honest. 1. We are going to have to yet again expand our database infrastructure to cope with the load, we are going to have two database points of presence, one in WDC and one in Amsterdam, which should help anyone on AMS/London/Singapore that is seeing any kind of desync regularly. 2. We are setting up a new 10gbit CDN origin node for dayzcommander because the current one (1gbit) cannot handle all of the traffic bursts when a new map is released - which josh is doing DayZ2017 right now. Josh told me today that DayZ has more active players today than it has ever had since it began and is in a rapid state of growth. 3. We also have 8 new servers coming in tomorrow to setup so we don't sell out again. And (pre-emptively) the 'well then stop selling new servers' argument is invalid because when we're sold out we constantly get emails asking when we will have more in stock, causing a bigger support backlog. 4. We are trying to hire new people to handle the massive influx of support requests, but good, competent, trustworthy people are extremely difficult to find. 5. I am personally going to talk to Prolexic tomorrow about purchasing blanket DDoS mitigation for our entire network (which will easily cut our profits in half, but I'm hoping it will be worth it, as basically the entire day yesterday was spent trying to fight ddos attacks). If it really is out of our price range then we have some ideas that will also take time to implement to reduce the number of affected servers when there is an attack. This is especially important in preparing for standalone hosting because I'm sure attacks will only increase. I've personally never had to deal with running a company that is such a magnet for DDoS attacks, and we never got them when we were first starting out, so I'm doing my best to hire people that are more knowledgeable about the subject (Prolexic) as soon as I can. 6. The current temporary DDoS mitigation solution we had to have setup is too aggressive and is causing some problems with the website communicating with the game servers, which needs to be fixed immediately. 7. The server manager software I wrote (that the website control panel talks to when you access your server) has become a little bit flakey and I need to debug some of the problems with it. 8. There are 4 maps out (DayZ2017, DayZ+, Thirsk, and Isla Duala) that we want to get supported before we work on new CP features. Once all of these problems are sorted out I seriously hope I'll be able to get back to coming out with new features every 3 or 4 days like I did when the company started, until then we are mostly at a feature freeze. It sucks that you can't download/upload your bans.txt for sure, but if you are really serious about it then I'm sure you can find a coder who will write something using RCon to import/export your banlist to text files - the tools are available to you. We've come a very very long way since we started and I am trying my best to expand to suit our popularity, but this started as a hobby and it hasn't been very easy turning it into such a large company. We are doing our best, trust me, and once we resolve the above problems I have faith that things will return to normal.

Today it's possible, we just got one in Washington DC and nowhere else, but it is resolved now and the node is now behind DDoS protection. We're definitely going to be working on it today if we stop getting DDoS'ed.

Whoever it is has been after us for 18+ hours now, so probably unrelated.

We managed to get some network-level DDoS protection installed for all of the servers but it looks like there may be some problems in Seattle and Singapore switching over to the ddos-protected network and they aren't reachable at the moment. We are trying to get it fixed.

Went to sleep about 5 hours ago and woke up to more DDoS attacks, these are currently down: Amsterdam 04 (5.153.13.115) Amsterdam 02 (159.253.131.97) Washington DC 04 (173.193.202.109) Seattle 04 (173.192.170.85) Amsterdam 07 (159.253.145.175) Talking with the datacenter to try and get the attacks mitigated. All other servers should be up. Someone has it out for us, don't know who or why. We will occasionally get 1 server attacked every couple days just because we are a very large provider and people will attack servers because they get antagonized in chat or something, but this is someone who is actively targetting and attacking our network, one server at a time, using the same attack method on each server, and has been doing it for the last 10 hours straight and managed to take down 14 of our 86 servers, most only temporarily.

Someone appears to be DDoS'ing our servers one by one now, at this moment here is the status: San Jose 01 (50.23.115.101) is OFFLINE Dallas 07 (173.192.70.135) is OFFLINE Washington DC 03 (173.192.200.74) is OFFLINE Seattle 04 (173.192.170.85) is OFFLINE Dallas 05 (208.43.33.119) is OFFLINE Dallas 13 (67.228.177.32) is OFFLINE Amsterdam 01 (159.253.143.16) is OFFLINE I'm sure there will be others. Sigh. EDIT: Our datacenter is actively mitigating and monitoring the attacks now, there will likely be intermittent problems but they should start coming back online.

There is no price difference between windows and linux on the servers we use. The base price of a windows 2008 R2 vlk is like $2 a month, which is negligible.

Out of our hands at the moment.