jwiechers

Heh, trying my best. I'm very sorry the updating was a bit erratic and sadly, there isn't a lot I can do against most of the bugs, other than try to provide as much information as possible. I'm still trying to figure out a good way to inform players of shutdowns, sadly, that isn't all that easy to achieve automatically. Automatic server restarts are synched each morning to occur at the stated times, but of course, sometimes you don't watch the clock and get caught up (it has happened and I've lost vehicles because of it as well).

Hello everyone, sorry, the last few days were a bit difficult with updates and issues with the server hardware. It should now run properly.

There is nothing wrong with the code files that were made available to server admins and servers which were properly updated to 1.7.2.2 before it was pulled work. That does not change, that it shouldn't have been updated, however and that there appear to be many servers which were inexpertly updated.

You will have to download the old 0.4.1 hive extension and get the files from it.

The servers are currently down again due to a continued dDoS. We're already filtering at the entrypoints to the DC, but it has proven rather difficult to block the botnets from getting enough through to overwhelm our uplink -- and I can fully sympathize with our ISP blackholing us because it interferes with their larger infrastructure. Will keep you guys updated.

Sadly, the way the hackers bypass BattlEye prevents any meaningful output from turning up in your logs -- so that will not help. I also doubt, that the hackers will use the same names crossing servers. I am not entirely sure if GUID Spoofing still works. If it does not, one possible means of identifying GUIDs of Nukers would be comparing GUIDs of all players online on nuked servers prior to the nuke taking place. If someone nuked multiple servers, he would turn up several times. There isn't really that much admins can do right now. We'll have to wait for a BE update that fixes this vulnerability.

@Cush Only saw this today, had a lot of trouble the last couple of days. Yes, automatic restarts have not worked properly and so the time got desynchronized. I've elaborated on the issues here. Hm, I have been thinking about this. My thinking was leaning more towards UTC-10/UTC+2, actually, because that would mean it is an exact inverse of CET. When it gets dark in Europe, it's sunrise on the UTC-10 server -- when it gets dark there, it's sunrise on the UTC+2 server. This is slightly off for CET people (and more correct for UTC people in UK) right now. On the other hand, my idea was that you could enjoy some "dusk" and "dawn" play on either server at CET peak time, those times being bright enough to see without augmentation but dark enough to make it a part of overall tactics. I somewhat agree, although it is more immersive this way, I've often wished for global/side or at least a substantially expanded direct chat (maybe 1km). It is official policy not to have these channels and I cannot change this, though. That is *very* odd. I'll have to check asap. I did receive a couple of emails to that address, though, so could you tell me the exact error? :-) @yeff Yes, the server was being dDoSed by a hacker since Thursday. My ISP has managed to get things under control -- only for the BE bypass to emerge and most servers getting nuked. In the interest of the players, I locked the servers and would like to keep them locked until there is a viable solution to the current situation (i. e. a BE update, most likely). I hope this is in the interest of everyone who has vehicles, tents, etc. on the server, but it's a damn shame. :-/ Jens

Yeah, that is what some people do. Others have been using FireDaemon Pro. Hopefully, 1.7.2's improvements to performance will allow the intervals to grow.

My thoughts on the matter, perhaps others can weigh in to get some more hard data: The major causes are, according to Dwarden and my own experience, desynchronization and simply "waiting" for the hive as well as low server FPS. I've been experimenting with that for a little bit and keeping an eye on my watch. My experience with the current version is that synchronicity or reasonable synchronicity is maintained for about four hours, followed by a substantial increase of desynchronisation afterwards. In the first four hours, synchronized in-game watch time among several players does not deviate too much, typically (only tried this a couple of times when we could arrange this) less than five minutes. However, synchronicity with people who spawn in after a couple of hours is bad -- and gets worse quickly after four hours. At five hours, typical desynchronisation on my servers is about 30 minutes, after six hours, it's about 45 minutes. As for what you can do: yeah, regular restarts are the only way. BEC is currently being modified to allow for proper information of players on your servers and I hope it gets it right soon. Some people use scripts and RCon. I advertise it as part of the MOTD (i.e. tell people that the servers may restart at 0600, 1200, 1800 and 2400 UTC) and generally get on five minutes prior to the restart, tell them to log-off and lock the server so no one can join and be disappointed. Jens

Hello Butcher, I switched the servers off yesterday because it was being dDoSed by Russians and then subsequently left it in a password protected state when that blew off to prevent it from getting nuked like several servers due to BE being bypassed. I switched the server off (as in shutdown) sometime around yesterday evening, UTC. I used the time I then had to do a clean reinstall of both ARMA and Arrowhead after I restarted the server this morning. The OS hasn't been booted for 10-12 hours and ARMA hasn't been installed for seven or so. So 10-12 hours is simply untrue. We were then on DE65, intermittently, from ~ 0858 UTC to ~ 1126 UTC this morning (start time of the ARMA2OA server according to the log file and time of final disconnect). I had talked to R4Z0R49 of the server admin team because we wanted to analyze script logs and wireshark logs of the connections in order to see if we could use wireshark to better detect anomalies in BE Client-Server communication or client-side script execution and provide more information to BattlEye and BIS. For the most part, while on the server, we simply ran around. We did not steal vehicles and deliberately kept changes to a minimum. As for the Clones, I used my other copy of ARMA (which donates the CD key to the servers) to have multiple clients connected. I am sorry this caused confusion.

Fenrix: If I am not very much mistaken: it does, not comprehensively, but to some degree

The TWS AM rifle has been removed from the loot tables back in 1.6; back then, there were about three legitimate TWS AM rifles if memory serves. It is relatively likely that the weapon is, sadly, illegitimate.

The developers cannot do anything about "cracked" servers that do not run off the central database. They're a shame but they're impossible to prevent. Servers with lowered player count or servers that remain permanently locked will generally be looked into. The devs are setting up a new system to deal with the large amount of servers. I've reported the two Seattle servers as well as a couple of others, too.

Sort of. I would not try to get off of the ladder at the top, but to peer into the stand and take off the gear while still climbing. Then climb back down.

DE 65, 76 and 77 . :-D Although it is a bit of padding my own shoulder, I've made a rule out of informing people -- it's just incredibly rude when that doesn't happen. There have been a few crashes, but other than that, I generally get onto Global to inform people at least five to ten minutes before it's going down, even if it is planned. MOTD "______ ______", "| _ \ |___ /", "| | | |__ _ _ _ / / ", "| | | / _` | | | | / / ", "| |/ / (_| | |_| |./ /___", "|___/ \__,_|\__, |\_____/", " __/ | ", " |___/ ", "","","","","","","","","","", "______ _____ ____ _____ ", "| _ \ ___|/ ___|| ___|", "| | | | |__ / /___ |___ \ ", "| | | | __|| ___ \ \ \", "| |/ /| |___| \_/ |/\__/ /", "|___/ \____/\_____/\____/ ", "","","","","","","","","","", "Welcome to the DE65 DayZ Server", "", "RULES", "1. Survive.", "","","","","", "", "-", "This is DE65", "Admin Contact: Jens (contact@wiechers.ws)", "Official DayZ IRC Channel: #DayZ on irc.gamesurge.net", "Our IRC Channel: #DayZ.DE65 on irc.gamesurge.net", "WebIRC: http://j.mp/DayZ-DE65", "Please report performance issues, cheaters and other things to us. We also welcome any comments!", "-", "", "Please note: This server will generally run both the most current ARMA2 OA Beta and DayZ Alpha.", "It may restart frequently during patch times, but will otherwise follow a predictable schedule.", "If restarts are required, they will always happen on the hour.", "Planned clean-up restarts may occur at 0600 1200 or 1800 UTC.", "There will be a restart at 2400 UTC.", "Unplanned restarts will be announced via Global.",

Yay! ... and I am sincere, despite the fact that I was just blown up by a hacker on EU25 :-(

rocket, thank you for keeping us updated. These things happen.

It works. The character is tied to your GUID which is tied to your CD-Key. ARMA stores the CD-Key in the registry. Steam automatically updates your registry whenever it is launched, so all you need to do is export the registry keys when you just installed from disc and restore them whenever you want to play with that character. Using two Steam-Accounts works as well. As said, Steam overwrites the registry for you.

I've been thinking about something similar with a couple of friends, most of us have at least two ARMA keys because we got the Steam version for convenience but had the original disc version, too. This means we have been able to sort-of mule a bit of stuff around, especially tools (you can collect multiple tools in your alice, you just can't put them in the main inventory) so we've been making nice trades with newbies as well as experienced players who needed something. We've basically been using our secondary characters and a tent in the woods between Lopatino and Pustoshka. Vybor is a pretty neat base of operations. There's a school and a supermarket next to each other, there are a few auxiliary buildings and easily accessible wells where you can fill water bottles safely. Another nice retreat is Myshkino, although there are few buildings there. We've also holed up in Devil's Castle, nice place, easy to defend, a number of good loot spots and you may be able to get a heli down close-by to shuttle loot in for trade. I honestly would not setup at the Airfield(s), though. There really is no good reason to, especially if you want to help new players. It's much more sensible to move into hot zones and loot zones to grab what you need and annihilate aggressors and move back out, collect the stuff in tents setup in the outskirt woods and move them around on a regular basis. Shuttle stuff to two or three "shop" locations at opposite ends of the map, some locations catering to newbies, some to experienced people who want good stuff. Just my two cents and I'm generally happy to establish any semblance of human trading and civilization to see people rise above the animals (;-)). Steam ID is identical to username.