Alfie (DayZ)

This. It's all very straight forward though. Only real thing you can do in preparation is download the Arma 2 and Arma 2 operation arrowhead files to your server if you haven't already. Don't worry too much about setting it up as they'll give you a default set of config files to use. Other then that you're stuck waiting.

No issues with 95054 here. Just had to update the BE on the server.

People have waited weeks in the past but that was before the ticket system. The new ticket system makes it a much more stream lined process for everyone, but there are still plenty of people applying to get through. You just have to be patient with them. I would wait at least a week before you try and kick up a real fuss. Sure that's not the reply you wanted, but you've just got to wait till a staff member gets to it. I would guess the amount of time it takes depends on how backlogged they are with requests.

If you have FTP directly to the actual game server executable's etc, then you could just run the beta patch on your own computer, then take the entire expansion folder (minus the Addons folder) from your Arma 2 operation arrowhead installation directory and upload it to the server. Should work. Won't swear to it though. Honestly though, if you're renting a DayZ/Arma 2 OA game server then put a support ticket in and get them to do it for you.

I'm assuming you mean the server Hive specific files. You need to join the server ticket support system.. .

Once you've done it, it's done. Well worth it.

No idea. We've had no issues. Only thing I can suggest is try downloading the Hive files again if you have't. Sorry I can't offer anything else. Hopefully Ander or another staff member spots this.

Have you updated to the latest Hive version? There was a Hive update when 1.7.2.3 released. I've had no issues with 94876 so far.

And that's on a good day.. :D

Change the IP to the external IP

If the spam kicking thing is true, then they obviously deserve to get blacklisted. However I don't see why an Admin/Owner of a server should be less inclined to shoot on sight because they run the server. They are players just like you and should be treated like you would any other player (they're just paying the bill). When you run a DayZ server, you're providing slots, that's it. You don't get special abilities to do squat. You get basic functionality to help moderate where required. The idea is you're helping the project while having somewhere guaranteed to call home (when I say guaranteed to call home, I mean if you host a server, you're not going to be losing your tents next week or w/e when the owner doesn't want to pay anymore). I run 3 servers, but I am just a normal player. I kill on sight where I see necessary. It's part of the game. Owner/Admin or not. If you're still not getting the picture, the idea is that Admins play like normal. You aren't suddenly special for it. If the spam kicking is true, you could of helped your case a lot by getting some screenshots. You may not of wanted this to go any further, but if this shit had happened to you, it's better to do whatever you can to help prevent it in the future, so those Admins don't get the chance to abuse the power they've got against other players. Is that not the idea behind reporting it? Admins can't teleport vehicles. If they restarted the server then the vehicles warped back because that's the last position they were saved by the server in. The server doesn't update players, vehicles, or tents every 0.1 seconds, it's more on the par of 30 - 120 seconds if not more sometimes. I also highly doubt they have aim bots either, just because they shot the wheels out while you were driving. I accidentally shot my car while putting fuel in before and the wheels blew up (I shot the god dam windscreen), so to be honest they could of shot anywhere. It's buggy. To add to this, if you were desynced like Vehicles tend to get, it would of made it even easier to shoot out the wheels as you were desynced sliding in a straight line off the road.

We run 3 servers off one box (2x50, 1x55). Just to give you an idea, we use on average 1.3TB a week. The servers are generally full during the day and drop off during the night time till Dawn.

You could try uninstalling the files, redownloading and then patching with an older version on a clean install. Only thing I can think of doing at the moment.

You can use BEC scheduler to deliver a message before a restart. You can also have it execute a restart after a certain time too. The only issue is you need a way to catch a crash. BEC won't catch a crash, but a simple .bat file could. So if you get BEC to execute a shut down command, then the server would automatically be restarted with your other measure in place. That's a simple way to do it. If it's the best way, well that's down to opinion tbh.

Assuming you've got the ports forwarded properly on the server (please tell me you haven't overlooked that), there's a few things I can suggest as starters. Remove the IP parameter from the launch. As quote from Kelly Heroes set up guide: Doubt it will make jack all difference, but you should specify -name=cfgdayz after specifying the port, before the rest. I'd also revert to the 93965 beta. To revert you literally need to just install that version. Nothing else needs to be done (other then the change in the server.cfg required build). Though I don't see why that would really cause an issue, but I have heard there have been some problems. It's worth trying just to be sure. I'd also switch the player count from 80 to 50, or a max of 64. I seriously doubt you've got the CPU power to support 80 people on a stable server. Even if you do it'll degrade very quickly. Fact is a dedicated Arma server is not multi threaded very well. As far as I'm aware it's something they added later in development so it's pretty half arsed. To add to this the more people you've got on regularly (and longer it's been up) dramatically alters the footprint the server uses. The larger the memory footprint, the faster it will reach its crash point. You'll seriously be surprised just how crippling the engine limitations are. It doesn't even matter if the OA server has the box entirely to itself (and that box is a mega-beefy rig), it's happy to act like it's being run on a single-processor server from four years ago. "Engine limitations". Learn that phrase well, because it will become the bane of your Arma 2 hosting existence. You should set your exThreads to 1 as well. That won't be the issue with the connection issues, but seriously it shouldn't be higher. An explanation on that from Mojo: exThreads is a mask for a parameter table, not an incremental count. That is, setting it to 7 doesn't create seven additional threads for better threading. The options are 0, 1, 3, 5, and 7: 0: No additional threading. 1: Threading for file operations only 3: Threading for file operations and textures 5: Threading for file operations and geometry 7: Threading for file operations, geometry, and textures The reason you don't set it to 7 (and I don't know why the DevTeam defaults it to this, it absolutely perplexes me) is because A2/OA are single-threaded applications with basic multithreading functionality added, they don't properly create parallel threads native to the application, they basically rely on OS scheduling. That means that when you launch the server with -exThreads=7, you're telling the server to prepare core scheduling for geometry and texture processing on a render loop that will never, ever come on the server. You're creating overhead for absolutely no reason, and zero gains. exThreads 1, however, uses only file operations. File operations are *mostly* used to handle the other two threads (geo and tex), but only because those are the most-called file operations. It handles all file operations. If you have the overhead to spare, you will notice marginal performance and stability gains as it offloads the file operations process from the main process. If, on the other hand, you don't have the overhead, it will destabilize the server. In other words, never use anything but -exThreads=0 or -exThreads=1 for the server. You also actually do need to specify this, because the .exe WILL use auto-detection to try to determine the exThreads number based on your core count. If none of the above has resolved the issue, can you guys get the server up and going, try to get in and fail, and connect via six updater successfully. Then after that, stop the server, go to your cfgdayz folder, open up arma2oaserver.RPT in a text editor and dump everything that's on there on pastebin.

What is the server launch command line? What beta build version is installed? Copy + Paste the server.cfg either onto pastebin.com or within code tags on here. Then I can help :P

There are a few things which can cause this. The most likely cause as mentioned by someone above is you're not forcing the beta build for the clients joining. This actually means that players who don't have the beta patch with the feature of disabling channels (it's still relatively new), can just use chat like normal. To be frank, there's a fuck ton worst things this causes if you're not forcing the beta build and having non beta build players joining. You can force this in your server.cfg. Look for this: requiredBuild = 93965; Make sure you uncomment the line and ensure you've changed it to the appropriate build number. If you've already done the above, the other usual cause is due to a bug/exploit which allows players talk in the side channels even though they're disabled. Not exactly sure how to replicate it but it's been mentioned enough times. The last cause is an old mission file. The Mission generator has been updated several times to include fixes / additions. The channels are disabled within the mission file, so if you haven't updated your mission file for a while then it's likely that the side chat simply isn't disabled on your server.

Same issues here.

As much as I love the publicity can this thread just be locked and burnt now :P

I thought as long as you went back to a tent after you died, then you could save it from despawning by simply saving it again. Can't swear to it but that's how it worked to my understanding, or least that's what I was told when I was new to the game.

Well your timings slightly off as 11.19 GMT + 1 the server had hit a scheduled reboot. You weren't fighting Admins, or even AQ members. UK9 is actually what we call our "home" server. I don't even think anyone in AQ has even played on UK5. It's solely there to support DayZ. If you still don't believe me: Server rebooted exactly 6 hours later again.

Hence why on second thoughts, I edited the suggestion out of my post :P

Going to warn you straight off the bat, there's a high chance that because it's a VPS you'll be denied as a host. Just giving you a heads up before you part with the money (the below is taken from the Server Hosts FAQ). Probably a good idea to find out if you'd be good to go before renting. Not 100% sure on your issue though. Mainly wanted to bring the below to your attention. http://dayzmod.com/forum/showthread.php?tid=9427

Fyi, ProfileName is based on your launch parameters (-profiles). Default is usually CfgDayZ if you haven't changed it. C:\servers\arma\arma2oa\ProfileName\Users\ProfileName ProfileName.Arma2OAProfile Under Veteran , change the following from 1: FriendlyTag=0; If you're changing Regular, then you will also want to turn EnemyTag=0; Keep in mind, in your Server.cfg, the difficulty you specify in your Missions class is the settings that will be applied. class Missions { class DayZ { template = dayz_xxx.Chernarus; difficulty = "Veteran"; }; };