demine0

Rocket is the guy who made this game. Your banned because you used hacks. It's not a ban that we made, but a ban that BattlEye has enforced. You can contact them about it. http://www.battleye.com/support.html

He's only mad because mommy and daddy aren't going to buy him a new copy of ArmA2.

1. Dr pepper sucks. 2. Helicopters are having issues that cause the player to be desynced and dropped out of the sky. Anything that causes a player to die isn't cool, and it happens somewhat often. The devs are working on a solution to that plus a few other bugs as well. They won't be in the upcoming patch, but as soon as we know when they're coming we'll let you guys know.

Probably a troll, but if the server admin wants to, he can send us his logs and we'll review them. Tell him to send me a PM.

You can also put a ticket in with Steam, and have them remove ArmA II from your account. You can then re-buy it and get a new key that way.

Do you use hacks? Because only people who were mod-apping got banned. You didn't hack now... did ya?

We had to take the hive offline in order to implement a possible solution to the excessive hacking that has been going on within the last few days. I'll post back once I have an ETA. EDIT: Server is back up now.

Server should be back up now.

PM me your e-mail address and instance ID. I'll send you the info to get it.

As long as the time isn't being changed WHILE the server is running, it should be ok, Your also not suppose to change the day/night cycle to lengthen or shorten them either. A lot of people have been looking for a solution to running different time zones on the same box. I'll ask rocket the next time I talk to him about the specifics of exactly what you can and can't do with time, and get back to you guys(If rocket doesn't beat me too it first) with what he says.

I think we should create a new "Server Announcements" forum. non admins use the server general forum to report down server, and a bunch of other stuff too.

How did you steal all his gear without killing him? The MK 17 SD used to be in the game, but isn't anymore, so most of the MK 17's you'll see out there are hacked. Having this weapon on your character can cause your character profile to become corrupt, so I would drop it if you have it.

- Entirely new mocap'd attack and running animations ^^^ Damn, now that sounds awesome. Are they still going to have the insanely fast and jaged like run speed?

Was exploring in the north yesterday and came across a small tent camp with a bunch of Mk17 TWS SD's in the tents. We pulled them out, dropped them all on the ground and restarted the server. We had found MK17 ammo awhile back too(like a month ago), so I'm assuming that these guns we're spawned awhile back and stored there. Does anyone know the item codes that are used to spawn these's? I wanna search in the rdt log and script log and see who spawned them, as we think they may be the same people who users on our server have been complaining about.

They have. Not there fault other server admins are lazy and don't upgrade.I believe the Devs are planning on blocking access to the hive for older version servers soon.

And then in Tonic's sticky post: So' date=' I'm assuming all of our RDP Information was also stored in this account as well? When I sent my RDP information, I remember sending it to a gmail account, of which the address was publicly well known, and everyone who knew that address, knew that RDP information was being sent to it. That alone makes it an obvious hack target. So it's NOT just servers that were compromised then? It was essentially anyone who trusted dayz enough to download what they thought was an automatic updater for dayz. Why wasn't your US mirror running antivirus software on it? MS security essentials is free for servers, and finds that variant of malware. That should have been a REQUIREMENT on all dayz servers, as I had mentioned in the past. If the mirror was linux, clamav is free, and has realtime ftp upload plugins. So, not only did that account have FTP passwords, donor's RDP server details in it, but it also had login details for accounts you guys use for backup's and mirror's too? Why did an artist even have access to that account? What purpose does an Artist have with your backup location FTP, and your forums FTP? Why would you give them access to that account knowing RDP details,are being sent to that account? Why are you keeping PLAIN TEXT passwords in a GMAIL account? Even if you switched everything over to in house email hosting, why are you keeping passwords in an e-mail account at all? Especially Donor server RDP details? Those passwords should have been deleted from the e-mail as soon as they we're received, and placed into a secure database. Honestly e-mail shouldn't even be used. What would have been even quicker and more secure, is a VERY simple https page with a form for players to submit their details to an sql database. Something i'm capable of doing in less than an hours time. So time constraints really not an excuse in this case for a lack of basic security. I really hope your not downplaying it as much internally as you guys are publicly, because these are all really serious security issues that need to be dealt with. Do you have anyone who is in charge of your IT security? If not, you guys should probably find one. If you allready do have someone, then you need to fire them because they either have no clue how to do their job, or much like everyone else on your team, they're over worked. I've been managing an IT security and engineering firm for 6 years, and have seen my fair share of network admins and security consultants come and go. I would expect the greenest security consultant I hire to be able to take care of all of the above issues that I touched on. For everything above to slip through, was a MAJOR over sight. How is the DayZ staff going to handle server support now? I have atleast one new PM in my inbox every day from some poor server admin, begging me to help them because they've either been waiting weeks to get there server setup, or has had their server broken and abandoned by the dev team for some reason or another. I can't imagine these new restrictions your staff is going to have to deal with will help take the load off on these issues either. The one thing that really irks me about this entire situation as a server host myself, is that multiple hosts have made the DayZ team aware of many of the security issues and server hosting issues that are present. Myself and other respected server hosts had even come up with procedures and systems that could be put in place to make support more streamlined, and secure, I've talked to Lightfoot over skype about some of them, and he seemed excited about the idea's we all put together, but I never heard back from him.

FYI, for anyone who does not know how to install the beta client, please see http://dayz.sykotix.com/?page_id=11 for a very quick and easy guide and setting that up. I'll also be putting out a guide on how to install and configure the beta server as well later on today.

A lot of people will run there server a few hours behind. Most of the people who play on Dallas 13, work 9-5 jobs and rather have one or two more hours of playtime during the day, so we have the clocks set back to Pacific time on our server. A lot of servers actually have regularly scheduled restarts. They do this because the server and hive can become unstable and stop working after a few hours. I'm generally restarting mine every 4 hours or so. Most server owners restart between 4-8 hours. The other servers usually just crash after 12 hours and get manually restarted by the admin. You can actually change the time on your server whenever you want. The only thing you need to make sure of when you change the time, is that the server and the hive/hiveauth must BE TURNED OFF. Never change the time while the server and hive are running and your golden McFly.

It sounds like you might need an updated monitor script. I don't have the download link to the current one, but I can zip mine up for you tomorrow. You could also try using firedaemon instead. It works much better. Another Alternative, is Dizzymagoo's Server Monitor. He'll be releasing a new version with MUCH better crash handling *very* soon.

I've had mine set to 6hr restarts, and that seems to work fine. Might push it to eight.

Just an FYI, I've found that most of the server related files are stored at http://armafiles.info/dayzdev/. If a new hive is released. Chances are it will be listed there. Please don't post this link outside the hosters forum.

It sounds like the Development team is overloaded with all of the work that's been requested. I've been involved in a few server setups, and have helped countless people troubleshoot their servers, and from what I can see, 95% of the issues are common issues that I was able to either research and fix, or get the answers from someone who has fixed them before (Mojo). No offence to the development team, but the Devs have only fixed one issue for me in the past. This issue involved my server not being able to connect to the SQL database. 4 Developers looked at the issue. 3 of them spent over an hour on the box troubleshooting. Finally Vipeax looked at it, and withen 5 minutes of doing something on DAYZ's end (He only ran ipconfig on my server. I watched him through a hidden VNC session), everything was working. It took 3 days for this to get fixed. I also had a similar experience trying to launch the beta server of armaII. It was crashing with a windows Exception. One dev logged in, rebooted my server, and started JUST hive.exe. Thats all he did. He then sent me an e-mail saying it's Jay2ArmaLib's fault and that I was using the wrong version. He said he fixed it. I logged in, everything was now shut down, and my Hive wasn't even functioning correctly. So the dev left everything even more broken then before. Another dev logged in later that night, and said the same thing about the JayArma2lib. Neither dev bothered to link me to the correct version, even though I know I allready had the correct version. This problem was finally resolved when I picked Mojo's brain about this issue. It turned out that for some reason, the Beta installer puts a dsound.dll file in the expansions/beta directory. This needed to be deleted and everything started working. I e-mailed the devteam e-mail back saying that I resolved it. About 20 minutes later I noticed that someone logged on the server again with the dayz account, and stopped the server and hive services again, and attempted to relaunch them. They launched the hive and hiveauth, but not the server. At this point, I changed all my server passwords, as I don't trust the dayz dev team to not come back on unauthorized and screw something up... again. We've even had a developer who gave the host an excuse saying that the server wouldn't run because the host was running "Windows Server 2007". The developer looked at the copyright date of the operating system and thought that was the name of the OS? This is a perfect example of why you need professional Engineers on the team. I have several hosts (All of which account for a large majority of the DayZ Servers on the internet) which all claim to have similar stories. What I'm getting at here, is there is a group of people who have made it publicly known (Look at the Volunteer Server Admin group thread) that we're interested in helping get the server community sorted, and we're available to help troubleshoot. Judging by the amount of time it takes for the Development team to fix something, vs the mount of time it takes for us to fix something, I think we could burn through the troubleshooting e-mails, much quicker than the dev team can. Any issues we can't handle, we can escalate to the dev team. This should be a HUGE selling point on the idea, because time is important to everyone involved here. The developers really don't have the time to be troubleshooting these issues, AND developing a game at the same time, and players don't have time to be waiting a week for their server to be up. Every day that a players server is down, that's a day wasted in their monthly server bill. As DayZ gets more popular, this is only going to become a much bigger issue. We're all engineers by trade, so this is what we do for a living. We also don't need any type of secure access to do this type of work. Most of the server community allready trusts us and gives us access to their servers. All we would need to make our jobs easier is better documentation, and better communication with the development team. When a new hive is released, we should know about it right away. We shouldn't have to go hunting for a link to it. When a developer fixes something on the server, the developer should e-mail us exactly what they did to fix it. This proves to me that the developer actually did something. I've seen for myself, via hidden VNC that the devs will log in and do either very little or nothing, and then say they've fixed the issue, when nothings been fixed. I'm sure the developer just got sidetracked, and forgot, but this causes issues. Sending notes on what was done will avoid those issues, as well as help us create a knowledge base, so that the next time I setup a server (I do almost 7 setups a week now), I don't need to bother a dev to fix an issue that they've most likely fixed 100 times in the past. A new google group also ISN'T an answer to the fragmentation issue thats going on in the server community. Introducing a new group, instead of just fixing the current issue (I mean.. how hard is it to add people to a forum group? It's not very hard at all!), is just going to make more places for information to get spread out on and eventually lost. The google group has been up for about 2 or 3 days now I think, and it hasn't done anything to help us centralize documentation, downloads and any other resources. It's just become another website that I have to check now to make sure I don't miss anything. We're all engineers. Troubleshooting applications on Server OS's is what we do for a living. Put a group that lives and breaths server administration in place to help, and you'll have way less issues. The developers are busy with what they do best... Developing applications.