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.

The package you guys had for 1.7.2.3 had a hive issue they released a fix for this a few days after the original package was released.

Just keep in mind that you have to get the latest one, don't update it with the original files that came with the release of 1.7.2.3.

No no no no. The version numbers are the exact same than the hotfix, you have to REDOWNLOAD the hive files. The hotfixed hive has the same version name as the broken one.

All they have to do is replace the @hive with the new one. We are seriously considering moving our hosting to a different provider at this point. We are playing on random servers while paying for multiple HFB ones...

I have been trying to get them to realize the hive they are running is the one they got before the hotfix was released. I have been trying since the fix was released, but the one time I managed to get them on teamspeak they pretty much said they had gotten the right files. The files they have at the moment are the ones from 1.7.2.3 release. The hive files were updated 2-3 days after. The names and versions are the same on the hotfix, but the files are fixed.

The hive they are running is from before the hotfix was released. The 1.7.2.3 files they have are from 2-3 days before the hive was hotfixed, since the name of the hotfixed hive is the same as the other one they are assuming is the same thing. What they have to do is just redownload the 1.7.2.3 server package and this includes the new hive files.

We have contacted them but they insist that they are running the latest Hive. Asked them when they downloaded it and they said with the release of 1.7.2.3 (the hotfix for the hive was released after this).

Ghillie/Camo are working on servers running the correct hive. I have tested camo in well over 10 servers so far running the right hive with 95099 and have had 0 problems. Some servers are still running the wrong hive hotfix, if you go on these after wearing camo/ghillie in a correct server you might A: Get stuck loading or B: Lose all your progress back to when you put it on.

Tested and I am almost 100% certain that HFB Servers are still running the wrong hive. I wear camo on the server and it will always revert back to when I put it on. Tested it in 8 different servers running correct hive. Camo worked fine. Jumped back into HFB server, game does not load in (12 tries with all 12 stuck at loading).

Could someone please answer this. I am wondering about it myself. Haven't found a ghillie/camo in a while but it would be good to know if working.