ChernoPTA

Yeah to be honest some of this stuff is good stuff, too bad its a troll. Oh well back to waiting for the game to be playable again.

Wait, is this for real? Seems too good to be true.

I ban Combat Loggers....cause if I have to take my lumps, so should everyone else. Problem is the "Server Hosting Rules" don't specifically address this issue, leaving it an area of potential argument and contention. Rocket specifically says, right here, that this is not a feature of the game, that it is an exploit and he intends to "patch it out"...which has yet to occur. Until it is impossible to force disconnect to avoid death, I feel it is in the best interest of the DayZ Team to add the right to ban combat loggers to the official "Server Hosting Rules". Otherwise its a complete gray area that leads to potential dispute over the topic of "meta-gaming" when its irrelevent, Rocket has spoken, so....etch it in stone so players know they can be banned for it and MAYBE they'll stop doing it. (Maybe being a very subjective and overly optimistic term). Thank you.

Sorry but for Global Bans thats all BattlEye. To report the issue to the Community Banlist Project you'd need log evidence to support the call for an addition of the perpetrators GUID to the CBL. Reporting the issue here with no logs won't get much of anything done. To be honest as a server admin, reporting cheats here WITH logs doesn't get much done either. But at least I'm covering my own ass.

I restart my server twice a day. I also just shut it down cause I'm tired of the constant "hacker" based mass disruptions I've been dealing with all night long. I might turn it back on in a day or two, once the summer break is over and the kids go back to school.

You cannot see who killed who in the RPT file. You can correlate player ID's with times of death, but not who killed them. Positional data can be sort of eyeballed in the RPT file but its really not easy to determine teleportation events by tracking it and some folks that are real abusers of the system will show no positional data at all....like this guy here: 19:39:43 "LOGIN ATTEMPT: "3383808" (MAS) lulz" 19:39:43 "Locality Event" 19:39:43 "READ/WRITE: ['PASS',false,'29048617',[],[["ItemFlashlight"],["ItemBandage","ItemPainkiller"]],["DZ_Patrol_Pack_EP1",[],[]],[0,15,15],"Survivor2_DZ",0.94]" 19:39:43 "LOGIN LOADED: B 1-1-A:41 ((MAS) lulz) REMOTE Type: Survivor1_DZ" 19:39:44 "Locality Event" 19:39:44 "READ/WRITE: ['PASS',[],[0,0,0,0],[],[],-83020]" 19:39:44 "LOGIN PUBLISHING: B 1-1-F:1 ((MAS) lulz) REMOTE Type: Survivor2_DZ" The READ/WRITE at 19:39:44 should have locational data where the 0,0,0,0 is...but it doesn't, but this very same individual was able to destroy the entire area of Berezino and its surrounding industrial spawns with some kind of hack that was allowing him to shoot off around 2300 rounds of G_40mm_HE in the space of a minute. So overall locational data is pretty hard to use to track teleporting because even if someone does have locational data, there is no legal to use applications that can translate it into how much distance was actually traveled in how much time and unless the differences in the shift in numerical position is extremely vast between two very close time stamps its nearly impossible to be sure.

Lucas and the Heli spawn is a definite. We've got him banned for similar offenses. Same GUID. The script for Dan and Simmons does appear to read as an attempt at hiding their player model. But I won't commit to a 100% reliability on my answer for those two.

Was raining fire and explosions, the attached file is obviously why. Mass creation and usage of G_40mm_HE rounds over a wide area from this player. Also had a report that he teleported to someones location before I pulled the logs and banned him. Feel free to review the attached file for the createvehicle.log data, as its too long to add to a single post. And the amount of entries for the G_40mm_HE spawns were so large that I can't even add ALL of them to a single text file to upload because it exceeds 500KB just with his entries alone.maslulzhacks2008242012.txt Heres his RPT entry, he doesn't even have a weapon at all. Then somehow has an automatic grenade launcher that can spit 1000 HE rounds a minute at 19:41, as the report shows. 19:39:43 "LOGIN ATTEMPT: "3383808" (MAS) lulz" 19:39:43 "Locality Event" 19:39:43 "READ/WRITE: ['PASS',false,'29048617',[],[["ItemFlashlight"],["ItemBandage","ItemPainkiller"]],["DZ_Patrol_Pack_EP1",[],[]],[0,15,15],"Survivor2_DZ",0.94]" 19:39:43 "LOGIN LOADED: B 1-1-A:41 ((MAS) lulz) REMOTE Type: Survivor1_DZ" 19:39:44 "Locality Event" 19:39:44 "READ/WRITE: ['PASS',[],[0,0,0,0],[],[],-83020]" 19:39:44 "LOGIN PUBLISHING: B 1-1-F:1 ((MAS) lulz) REMOTE Type: Survivor2_DZ"

Add another: 24.08.2012 19:57:11: Alphaone (71.243.218.201:2324) aeb259c1cea8723229da541fb9292480 - #0 " if (isServer) then { _object = createVehicle ['M1030', [3066.49, 7969.16, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 10636, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objectUID" 24.08.2012 19:57:11: Alphaone (71.243.218.201:2324) aeb259c1cea8723229da541fb9292480 - #3 " if (isServer) then { _object = createVehicle ['M1030', [3066.49, 7969.16, 0], [], 0, 'CAN_COLLIDE']; _object setVariable ['ObjectID', 10636, true]; dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object]; _uid = _object call dayz_objectUID" Also: 24.08.2012 20:11:40: Alphaone (71.243.218.201:2324) aeb259c1cea8723229da541fb9292480 - #0 "RUVehicleBox" 83:295 [5631,14659,408] Had another guy show up at the site of the mass HE nuke that occurred with nothing but an 1866 showing in his inventory in the RPT, but was obviously shooting AS50 NATO rounds and killed four people as they tried to recover. The ban filters and new scripts.txt were nice while the lasted. Cross posted and submitted to the Community Ban List project.

The BattlEye 1.169 update went through. Some people got dropped due to failed update attempts. After updating to BattlEye 1.169 update on a 1.7.2.5/96061 server, everyone that is connecting to the server is getting globally banned within minutes of connecting. I am the primary admin of the server and other than flagging my Arma2oa exe to make it Large Address Aware I've never hacked or modified a single part of my installation. Many of the people on my server I happen to know and I know they aren't hacking either, but there were tons of people on the server I didn't know and they all got hit with global bans too. Everyone I know has sent the requisite support email but I have NEVER seen an entire server get hit with global bans like this ever in my entire experience with DayZ and BattlEye.

Deathmatchers get tired of walking back down to Cherno.

Why not ask all hosts to mirror a Hive replication slave? I mean.....wouldn't that be more efficient than depending on one provider? Seems to me its more about getting some strong SQL devs into the process than getting different hardware into the process. Table and subtable data is loading from the Hive, its just not updating its records as its supposed to. Far as Hive hosting goes, I'd have a lot more faith in my provider to maintain a hive replication slave than I would in Vilayer or Host Altitude to be hosting a primary database cluster alone. In my opinion, BIS should be hosting the primary Hive at this time, and all host service providers should be required to host a replication slave which is linked to that primary and updates in real time along with the primary. That way you have a distributed SQL network where if a connection gets refused at one address it simply reroutes to the next available and writes there, and the data is then propagated throughout the slave network, and back to the master Hive server. But again thats hardware, and all the hardware in the world isn't going to help if the SQL is having its defined limitations exceeded.

They need to fix Hive 0.7.3, its a serious bug fest. But everyone chant after me "Alpha, alpha, alpha, YAY!"

This company has gone above and beyond the standards of service so far in my association with them. I generally don't shill for anyone, but every issue I have had, no matter how major or minor has been addressed by a support ticket response within minutes of me filing it. And usually the issue at hand is sorted out within an hour. Elpishost definitely makes the time to ensure they retain their customers. And that to me is what convinced me to switch my services from my previous host to a host that is far more customer focused. And Elpishost definitely seems to be that hosting company. I wish them all the success in the world, they're working for their money, unlike some other companies I could mention but will refrain from doing so.

Yes, Hive does seem to be down, again.

He was in createvehicle and scripts log. Both files were showing completely typical entries for the individual....this is why I am reporting it Jwiechers, not because I'm an idiot that doesn't know what I'm looking at. I mentioned remoteexec simply because it was obvious that nothing was logging any remote script executions. And the logs he did appear in....he wasn't doing anything unnatural. Createvehicle has an entry for his Backpack and Camo_Suit but everyone that logs in gets that info written to our createvehicle regardless of it supposedly being filtered. Scripts log was the same thing everyone else was generating, absolutely nothing stood out as atypical. I appreciate being told I'm an idiot though when I'm simply trying to use the tools we have to report a fact that someone did some rather incredible things and none of the tools we do have saw any of it, just 4 players. Have a nice day.

Our server has an instance ID above 8000, vehicles spawn, but on every server reset they all respawn back at their original points unrepaired. Also tents are not saving their inventories accurately either. Its not making the server very fun for our players.

Thank you for your advice but I assure you that his name is no where in our remoteexec.log. At all. Period. He does not appear there. He does appear in our RPT, Server_Console and Scripts.log, and in createvehicle.log, but everything there is completely typical entries that do not in any way support or report what we saw him doing while he was having a civil conversation with us after having three magazines from various weapons emptied into his torso. I'm quite competent at reading my logs, and Dwarden has made a great effort in making the new additions very easy to discern. Far as there being no "THE" Bypass, I would agree that is "technically" correct, but there is one that is most often used and it is currently back online and currently undetectable, its not that hard to go find that kind of thing out for yourself if you simply use Google. And no, unfortunately at the time no one was capping, it had been an uneventful few days other than normal server activity, thus the slightly relaxed attitude and people not paying attention to additional individuals showing up (its so hard to tell people apart after all, everyone sort of looks the same regardless of what they wear, hey its ghillie guy, camo man, suvivor dude, hero dude, towel face guy.) It only really dawned on them something was wrong when someone checked his nameplate and suddenly everyone opened up on him cause we knew he wasn't one of ours. Far as PMing the info to you, I technically cannot do that, I have no evidence to support what we saw, and passing you his data would be a violation of data security and his privacy, for all intents and purposes. And believe me, I'd like to ban him, I don't like hacks, but if the server couldn't see this guy doing anything at all, I can't do anything at all other than post a warning about it.