semipr0

Well I'd restart mission but I don't want to wipe legitimate camps out too. I got no problems with people playing legitimately but this was like a freaking DayZ Wal-Mart. I thought flattening tents with explosives destroyed the tent contents?

BattlEye can be completely bypassed so, it can check your prostate for all the good its going to do.

Welcome to the club. GUID bans can help, ensuring your Scripts.txt and BE are updated from the files provided by your host are also helpful. But even that doesn't guarantee any level of fair play. Its something a lot of server admins are dealing with right now.

Depends on the server settings.

Getting BattlEye kicks when server admins are attempting to access server control from within game. This is after installing the latest scripts.txt update today on 7/23.

Did not see anything in the update logs that reflected it was changed for that purpose. Course trying to keep track of all the change logs is just about a job.

I'm on our CP and FTP for HA atm with no problems. Though we've taken our server down at this time because we've been dealing with hackers for 48 hours now and we're just tired of it. Latest guy was randomizing his GUID and IP, we couldn't keep him out regardless of what we did. Godmoding, teleporting player groups, setting shit on fire. Just about tired of paying to deal with this shit.

I don't really care that I don't need to use it, the interface shouldn't be kicking people that are trying to access it at all. Thats a pretty bad bug.

This is a usual assumption when a hack wave is predominately bad. That the developers are somehow behind the unknown individuals that are selling the cheats. Its pretty much 100% unfounded. Rocket has a better potential profit on this entire idea if he protects it, not if he exploits it in the short term, any developer would be smart enough to see that. But its not uncommon for people to start believing that the hacks are a product of the developers selling the hacks simply to make money, then more return profit on new unit sales when they go through and ban the hackers. I doubt the hack suites have made more than a few thousand dollars at best, and to be honest Rocket's intellectual property here is worth quite a bit more than that.

Was gonna post our servers Sunday rampage that we had to deal with but it pretty much looks just like this so you got it covered. Hacking is completely out of control and it sucks paying for servers that we can't defend because of the dumbass hosting agreement policies.

I've been killed on my own server plenty. Thats part of the fun really. Only time I start banning people is when they're raining A-10's out of the sky, teleporting all over the map, or I find hacked weapons on their corpses...then I go get their GUID's and ban them. Cheaters being banned is definitely fine in my book. But people playing straight shouldn't have anything to worry about.

Still no resolution to this issue with the latest Arma betas I am getting support feedback from BIS on a daily basis about it as we run various tests trying to find the issue. But we can't even run just straight up Arma II OA and join an Arma II OA server together without the same problem.

Same problem for my wife and I here, have had a thread going for about a week on it http://dayzmod.com/forum/index.php?/topic/36739-two-computers-different-ips-same-house-cannot-connect-to-same-server/page__st__40#entry409924

Sorry didn't mean to rub your face in it, I'm just raw as hell and tired from a whole day of having to continually shut down my server simply to ban yet another handful of GUID's yesterday and all night tonight. So when it comes to hacking I guess you could say I've had it up to my eyeballs with injection hacks and the stupid Arma Server allowing client side script commands to be executed. Thats absolute idiocy in any multiplayer environment. And its even stupider when the Arma beta process is constantly pushing out updates and no one at BIS has thought to go "Yanno, maybe we should have the beta server reject client script execution."

I'm not sure why we're bothering to pay for servers. The game is fantastic. The inability to protect the server you're paying for is not. I do not like the fact that I have to prove beyond a reasonable doubt that the guy dropping A-10's everywhere on my server was definitely doing so. Its bullshit. I pay for the fucking server, if some jackass is script fucking my play time, then I shouldn't have to explain my decision to ban the fucker to anyone. Period.

Or, conversely, forum moderators could delete them before anyone has time to reply to them. I dunno, just a thought.

All server hosts need to do is run a cron job which collates all bans.txt from their server networks, compiles a new copy removing duplicates and installs the new bans.txt file daily. It won't get all the hackers but it raises a much higher network level defense level.

I've sent a technical request to Host Altitude with some examples of how to create a network cron job which collects all bans.txt files, collates the data, removes duplicates and replaces the bans.txt file on the server. Its not that hard a cron job to write and if all server hosts use something similar to it, they're at least protecting their servers from all banned hackers on their server network...which saves their clients problems. Basically using the hosting network as the dragnet which can then do mass server denials to all GUID bans placed on a server list, simply by pooling their collected data.

Just to add we just had to shut our server down for the third time today when a flight of A-10 Warthogs made their way across Chernogorosk. Seems like we're going to spend more time banning GUID's than playing.

This is a direct and imminent problem. With DayZ's intended purpose, there is NO reason the server should be accepting custom script commands from clients.

Thats why I'm asking about a centralized server admin collaboration for GUID's. I'm not expecting Rocket or BattlEye to ever be able to address this situation effectively. But a server admin collaborative document on Google Docs or something where you could basically pull the days GUID bans and add them to your own list would be good.

95208 worked for us this morning for about 20 minutes, then we started getting red text spam about BattlEye update failures, BE kicked me off the server, I reinstalled BE from Steam, logged back on, and it kicked her back off. This situation is freaking annoying.

Yes I actually attempted running both our computers using different Arma Ports specifically assigned in the _runOAbeta command file string. Even in that situation, connecting to the same server via the internal server browser we still cannot play on the same server. I've also added the -port commands to our additional launch parameters for Steam with no luck there, and even tried the flags on the executables themselves with no luck. Our clan runs a server the only thing in server.cfg that allows you to attempt to allow multiple connections from the same person is allowDuplicateIDs, which does not apply to network addresses it applies to CD key registry values.

Seems like 95168 has more problems than it fixes, and the change log for it is fairly ambiguous in regards to whether it actually fixes it or not. BIS Support has recommended downgrading to 94444 and sticking with it til there is a fix, god knows if there is a fix at all.

We'll have to see once we get our server upgraded to 95170 if this addresses the issue. I hope it does cause its been an annoying week.