anonymous83

Game is probably running on a private hive but they should thunderdome everyone every 35 min just for kicks and giggles, and for that authentic DayZ feel :P

We are having a problem on our server with vehicles saving right on the spot they are destroyed not back at their spawn spot, basically after a server restart the vehicle is right back where it blew up. Also the heli, if destroyed, spawns back on the spot it took off from not on any of it's other spawn points.

Any idea if this shows up and if it does what it might look like on the logs?

Just happened today on our server. Some guy spawned a bunch of AI female survivors and killed 3 of us.

Found 3 different camps not 3000m from each other on the north western part of the map. Found our V3S that had been stolen earlier last month sitting up there in one of the camps. Found the Ural in another one and a dirtbike and atv on another. (atvs are pretty easy to find)

DayZ first world problems. Now that we got a heli repaired, it was too easy to find and hoard most of the vehicles in the game......now what?

We had one almost fully fixed last night on our server. About to put the finishing touches on it. Hacker comes in, kills all the people on the area by the heli, kills all our snipers that were in 3 different spots about 300m apart gets on the heli, goes up in the air, nosedives it blows it up and walks away without a scratch....

So we have stockedpiles of guns gathered from countless NW AF raids and Heli crash sites. All these guns are basically sitting on our Ural and V3S collecting dust. We have tons of amo for almost every gun as well. Right now we are really looking for ghillie suits, and dragonov sniper rifles. For these pretty much name your price.

I would love this.

Just curious if this would also address the issue with tents appearing even when taken down/blown up/ran over after a server restarts?

This is not addressing the current issue. The problem at the moment is that there was a @hive files hotfix with the same name after the 1.7.2.3 was released. The simple way to fix this is to just redownload the full 1.7.2.3 package (this was suggested by Ander on his post). I am sure when 1.7.2.4 package is released by the devs all these issues will be moot but as it stands the bulk of your costumer complaints and server issues are coming from this one folder that needs to be updated on MOST of your servers.

Just quoting myself just in case it got lost in the wild.

You need to redownload the package that includes the @hive folder and replace that.

Choo choo, all aboard the derail train!

Not to nitpick here but it's been over a week I have not been able to play on a server I am paying for, this for an issue that I have been trying to get them to acknowledge and fix for said amount of time.