ersan

There are basically 3 different lines of support. If the first line can't answer the question they will wait for the second line to try, and if they can't it will get to either me or Cellkill. The first line wouldn't really know anything about fixing lag issues (if they can even be fixed). The second line will know to take a look at the server console and examine the battleye filters for anything that does too much logging, since that is the primary cause of lag on our servers. It's a difficult issue to diagnose.

We are behind on e-mails because one of our support reps is MIA and it was just the weekend. They are being caught up on now. Nobody is intentionally ignoring you.

My colleague tells me that the tent/vehicle/object bug fix has been applied to all servers. It has not been thoroughly tested, so if there are still problems e-mail [email protected] - if you are using a custom server pbo it needs to be reset to default before the tent fix will be applied. It is spawning in most areas, some areas do not get loot or zombies - it's a bug with the map itself. The author (Vilayer) botched the update and we are trying to do what we can to get it back to normal. Takistan also spawns all players in the same location, which we are working on fixing as well. Both of them are problems with the mission file. You'd have to contact PayPal about this - I've only seen this error when someone tries to use a prepaid temporary credit card to setup a subscription, which they don't allow for obvious reasons.

Just so you guys know, we attempted to come up with a good fix for the tents tonight and did not succeed. We have them mostly working right up until a server restart, then they break again. We will be making another attempt tomorrow.

No, problems in Seattle would not affect London - send an e-mail to [email protected] and someone will assist you.

That was about DayZ+, if you aren't running DayZ+ helicopter crashes work properly.

We didn't make the map, vilayer did... And this is the first I'm hearing about this bug. I play tested the map for 30 minutes before I added it to the upgrade list and it worked fine during testing, we don't have the resources to extensively play test a map - that is supposed to be the responsibility of the maps' author. If we don't upgrade to the latest version of every map we get hundreds of e-mails a day with people asking why they can't connect to their server that is running the wrong version and when will it be fixed... Upgrading and trying to sort any bugs we encounter later is the best way unfortunately. I don't know what this means.

We will be looking into tents soon, complain all you want it isn't going to get it done any faster. They have been inconsistent (not broken, and they still aren't completely broken) since 1.7.5.1 was released. DayZ itself is losing players regardless of whether tents are working properly or not.

We have said several times we are looking into the tent saving issues. We are not developers, it has nothing to do with the database it has to do with DayZ itself and HiveExt (the library that DayZ uses to interface with a database). We are working with Bliss as a backend which is an abandoned project. Reality is the replacement for bliss but it has its own set of problems. The problem did not exist until the 1.7.5.1 update and almost every other host is having the same problems, we just have significantly more servers so we get the most complaints about it. We will post any updates we have on the subject on twitter and our news page.

We will be looking into tents soon.

We somehow missed the update on Los Angeles 03 (192.31.185.202) so we are doing it now, shouldn't be down too long. Pretty sure he was making a negative comment about Vilayer. We will be working on Skaronator Lingor and i44 soon.

The company you bought a server with does not appear to support private hives then, and they don't know what they are doing because the DayZ team doesn't approve new instances any more, hasn't for months.

The following updates are finished: ArmA 2 Beta 102591 DayZ 1.7.6.1 Celle 1.9 Fallujah 1.5 Lingor 1.3 Panthera 1.8 (with fixed loot and zombie spawns) Takistan 1.7 Utes 1.3 Zargabad 1.5 None of the new maps support Wrecks, Care Packages, or Kill Messages currently, so the options have all been disabled. If you have custom mission or server pbo's and are running these maps you must reset them for your server to work properly. And as always we will not be able to offer you any support until they are reset.

Several months, the official hive is deprecated and the recommendation is to switch to private hives.

Jesus guys, we don't get paid to host maps - if anything the mod developers ask us to pay THEM To the guy complaining about custom file sizes send us an e-mail [email protected], we have to manually change them for you. Most people don't want them enabled so they are disabled by default. Multiple mods using the same map means that for the other versions we have to create a database specifically for that map and use that as the base because bliss's database structure does not allow you to host the same map on multiple mods. 2017 and DayZ+ were a huge pain in the ass, I didn't say we weren't going to host it I said it will take longer. The tavianas use the same base database, dayzland.eu uses the base vehicles and database from dayztaviana.com. The Vilayer maps (fallujah, lingor, zargabad, panthera, takistan, utes) were updated to use the 1.7.5.1 base code instead of 1.7.4.4, the same way Vilayer maps are always updated. We are going to be updating dayz, celle, fallujah, lingor, zargabad, panthera, takistan, and utes to their latest versions and add the framework to run skaro lingor, dayzero, redux and invasion 1944 (they will come later) in about an hour and a half (8:30PM EST) - they will require rolling restarts.

Skaronator Lingor isn't really a priority right now because any mods that use the same base map require a lot more work for us to host, that's why we don't have dayzero or dayz redux. We intend to push all of the updates tomorrow, also there will be new servers in Amsterdam, Washington DC, and possibly Salt Lake City tomorrow.

Going to try to do all the map updates later today: (pushed back to tomorrow, sorry) DayZ 1.7.6.1, Celle 1.9, Fallujah 1.4, Lingor 1.3, Panthera 1.8, Takistan 1.7, Utes 1.3, Zargabad 1.5, and we will take a stab at i44 but no guarantees. Slots often free up around 8AM EST, but there are only 3 cancellations at Los Angeles in the next 3 days so it's unlikely you'll find any. When we get more LA servers is still kind of up in the air, we are doing a big transition sometime around March 20 but we will try to get a couple more servers over there before then (probably a week from now). We will have more Salt Lake City servers sometime this week, and possibly more Seattle servers as well.

Yes, sorry, SLC is actually our least reliable datacenter, anytime there is a DDoS (not even necessarily directed at us) every server at the datacenter experiences connection problems. And yes IP's will change, ports will be the same, we will post a list once we lock in some dates.

We are testing the new Vilayer maps and Celle and hope to have them pushed out tomorrow. Also we removed the 'best for Australia' moniker for the singapore location - as it turns out Los Angeles is significantly better for Australian users, we believe Softlayer removed a very important bandwidth provider that had low AU pings before: Melbourne, AU SNG: 346.0ms LAX: 174.0ms Sydney, AU SNG: 357.8ms LAX: 178.3ms Singapore is now only recommended for Asian customers in Singapore, Hong Kong, India, Malaysia, Japan and Thailand. All other Asian countries actually get better pings to Los Angeles or Amsterdam. Also we are going to be moving all Salt Lake City and Seattle servers into Los Angeles and removing those locations in late March (probably around the 20th), more details will be posted when we have them. We conducted quite a few tests and LA looks to ping better than both other locations on average - you can see the results of the tests here: https://dl.dropbox.com/u/1956377/LAX.xlsx Los Angeles has DDoS protection and we have far more control over the network as well. http://opendayz.net/index.php?threads/dayz-1-7-5-1.7592/#post-16773

Slots usually free up around 8AM EST (I think midnight in Sydney) - it's best to check around that time. We are planning a large installation in LA but it won't be done for at least 2 weeks.

Los Angeles should get 150-170ms, best we can do.

It's always something isn't it... We'll take a look and update the filters soon - you can always update the filters yourself via FTP.

All servers updated to 1.7.6/ArmA 102285 - you must reset your SERVER pbo to defaults for your server to work (if you have a custom pbo, if you don't know what that means it doesn't affect you), mission files were not changed. We also re-enabled the 'messaging' feature for bliss (recurring messages). Care packages, wrecks, and kill messages still do not work. (This only applies to Chernarus) EDIT: We just fixed one of the tent saving issues that was a problem back when 1.7.5.1 came out, and 1.7.6 brought the problem back - restart your server to apply the fix (it will modify your server pbo, so custom one will not have the fix until you restore defaults). This still does not completely fix tents, they will probably still have the cross-saving problem, we haven't had an opportunity to fix this yet.

We haven't found any private hives that support 1.7.6 yet - once something is available we will adapt an update. We have rolled our own 1.7.6 update and thevisad has also updated reality it seems - we are pushing the update to servers shortly, there will be rolling restarts.

We use the same paypal account for many different websites because the more volume you do the more discount you get on fees - you can always contact us at [email protected] Also we are extremely liberal with refunds (full refunds within the first 48 hours), as anyone who has used our service knows, so if you need one let us know. We intend to host standalone when it is available to host, and we will allow you to change your mod server to standalone when it becomes available. Our default scripts work on every map, the only way the above poster would be kicked for firing a weapon on taviana is if they modified the filter themselves. Kill messages do not work on any map as far as I know, definitely not consistently.