Skydive (DayZ)

There was a Defiant on my server who was banned for illegal weapons.

Does your buddy Defiant also go by CSADefiant or [CSA]Defiant?

Running a successful Epoch server is not as simple as putting it up and waiting for it to populate. I ran a private hive Epoch server to which I made a lot of customizations and additions. We had a number of admins preset on the server to keep any scripters at bay and for a while, we did have a popular server. The problem now is there is literally thousands of Epoch servers out there, many of which have also taken the route of customizing to attract more players. Unless you (or a few of you) have some coding skills and a lot of extra time, it's tough to run a server and keep it populated. I'm not trying to deter you, but it's something to give some thought before venturing into running a private hive server.

Sad to hear that the 1.8.1 update is not coming. I just accepted an offer on my house and will be moving to DC June 2nd, so it looks like the end of my public hive server is rapidly approaching. Sad news indeed. R4Z0R49 was the one to get me set up on the public hive so long ago now. Thanks for the help and support all along!

Since I have been running Windows Server 2012 and Server 2012 R2 since they were released on many of my servers, naturally I upgraded my DayZ public hive server to it as well. Since then, every once in a while I have had players report being banned on my server when I have not issued a Admin Ban and they did not receive a Global Ban message. The message they receive simply comes up in a box in ArmA 2 OA and reads, "You were banned". Recently, this has been occurring more often and has been a real frustration for myself as well as regular players on my server. In desperation to eliminate the possibility of having corrupt files, I have reloaded the OS and all of the ArmA 2 files and DayZ server files countless times. I have also replaced and upgraded the server hardware a number of times now to ensure no failing parts. Still the problem has persisted... until last night / today. Out of curiosity, I wanted to switch the OS back to Server 2008 R2 and see if the problem existed there with ArmA 2 OA possibly having a conflict with some changes in Server 2012 / R2. Sure enough, players that were getting the "You were banned" message are now able to join the server again. This is something I hope the devs will take notice of since it would not surprise me if it has also made it into ArmA 3 and could also be a problem. Okay, this has been my public service announcement for a while. I hope this information will find it's way to others experiencing this problem or are considering using Server 2012 or 2012 R2 for a server platform.

Thanks for the heads-up, SaintMerc. I'll look into that as well and clear it if it is populated with any IDs.

Cleaning up vehicles is not a problem as long as you run a simple cleanup script at each restart. What you're really going to be up against is the huge amount of Epoch servers that are already out there. Use DayZ Commander or Six and filter out servers by Epoch. You'll find that MOST of the DayZ servers out there now are Epoch servers (thousands) so getting anyone to populate your server over all of the others out there will be very difficult.

This problem has surfaced again. It's to the point now that I cannot get my server to start at all. Get this error on every single restart.

I thought about that too, but I tested running the server with a clean install of Server 2012 R2 and changed the onHackedData = kicked to test this, but the players were still not able to connect. Now with Server 2008 R2 running, I can still have onHackedData = ban and the players that could not get on before are all able to get on the server now and play. So my config for those looks like this: // SIGNATURE VERIFICATIONonUnsignedData = "kick (_this select 0)"; // unsigned data detectedonHackedData = "ban (_this select 0)"; //"ban (_this select 0)"; // tampering of the signature detectedonDifferentData = "kick (_this select 0)"; // data with a valid signature, but different version than the one present on server detected

I changed nothing. I backed up all of my .bat files, configs, battleye files, etc and just copy/pasted them back in when I switched to Server 2008 R2. This also included my @Hive directory, MPMissions and Keys directories. No changes to ANY server side files. I always use DayZ Commander to load the @DayZ directory back on.

Since I have been running Windows Server 2012 and Server 2012 R2 since they were released on many of my servers, naturally I upgraded my DayZ public hive server to it as well. Since then, every once in a while I have had players report being banned on my server when I have not issued a Admin Ban and they did not receive a Global Ban message. The message they receive simply comes up in a box in ArmA 2 OA and reads, "You were banned". Recently, this has been occurring more often and has been a real frustration for myself as well as regular players on my server. In desperation to eliminate the possibility of having corrupt files, I have reloaded the OS and all of the ArmA 2 files and DayZ server files countless times. I have also replaced and upgraded the server hardware a number of times now to ensure no failing parts. Still the problem has persisted... until last night / today. Out of curiosity, I wanted to switch the OS back to Server 2008 R2 and see if the problem existed there with ArmA 2 OA possibly having a conflict with some changes in Server 2012 / R2. Sure enough, players that were getting the "You were banned" message are now able to join the server again. This is something I hope the devs will take notice of since it would not surprise me if it has also made it into ArmA 3 and could also be a problem. Okay, this has been my public service announcement for a while. I hope this information will find it's way to others experiencing this problem or are considering using Server 2012 or 2012 R2 for a server platform.

Moderators: This thread can be deleted. I have posted it in the Server Ownders and Admins area so it will not get lost. Thank you!

Can a moderator please move this thread into the Server Owners and Admins area? I don't want to see this thread lost in all of the server advertisement spam. Then you can delete this post. Thank you!

CONFIRMED! Switching back to running Server 2008 R2 has cured the erroneous "You were banned" message! For anyone else that is thinking of running ArmA 2 OA on a server running Windows Server 2012 or Server 2012 R2; Don't Do It!

Changing the server to Server 2008 R2 has made some noticeable performance increases. I think ArmA 2 and Server 2012 R2 just don't get along that well. Any of you there were receiving the "You were banned" message please try the server now and see if it still happens. Hopefully switching the OS has remedied the problem.

Did another full server reload tonight. This time I loaded Windows Server 2008 R2 instead of Windows Server 2012 R2 to see if maybe ArmA 2 OA is having issues with WS2012R2 for any reason. Server is back online now running on ArmA 2 Beta patch 103718 like before.

This is frustrating. Okay, I made a couple changes to settings for the server so try logging on again and let me know if it is still giving the generic "You were banned" message. If so, I have found some mention of the beta patch version possibly causing issues so I could try reverting to an earlier beta version.

If any of you are still following this: I recently did more upgrades to the server so now it is faster than ever. In addition to this, because I put in a new, larger and faster SSD, EVERYTHING was loaded fresh for the server again. (OS, ArmA 2 CO, DayZ files, etc) If this problem still pops up, I have no idea what the source of it could be.

Wow. This is certainly a slap in the face for me and anyone else running a public hive server. I guess this would be a good time to shutter the doors on it, but maybe that's what this change what meant to do.

Splinter_2K nailed it. This particular server thread is constantly bombarded with server advertisement spam. There is no way that anyone will find useful message threads among the constant bombardment of server hosting companies and server operators trying to populate their servers. I say break off the sub forums Splinter_2K recommended so that we can still have an area to share valuable information.

I don't like this change for the specific reason that the thread for server operators is now gone. One of the problems that still remains unanswered is that with the recent changes to battleye that basically breaks everyone's filters from working with no good explanation or examples of how to set them up correctly. And now, this has basically been "swept under the rug" still leaving the problem unsolved for the majority of us who are server operators.

Unfortunately, no tutorial. Here or on the BI web site. The developers have just assumed that we all have the same level of intimate knowledge as they do.

Will the BE filters be updated to the new REGEX format soon? This change seems to have been thrown at us out of no where and not all of us know how to use regular expressions and convert our BE filters over to it. It's a bit unsettling that this took place leaving what is likely all DayZ servers (public and private) unprotected.

I just discovered this as well. A little disappointed since this seems to have had so little discussion or lack of it being announced to server operators. It's great for those who are programmers / coders and know how to change their BE filters to use the regular expressions, but for those of us who are not, we are left with servers no longer protected by BattlEye. This was a poorly implemented change and even the BE filters linked in the forums are still in the old format.

R4Z0R - It would be great if the public hive server operators knew who "the guys" were so we could submit problems directly to them and get them resolved faster.