(OCN)Vortech

2012/09/09, 9:17:53 "STARTING LOGIN: ["52538822",B 1-1-A:21 (rawrerz) REMOTE]" 2012/09/09, 9:17:53 "LOGIN ATTEMPT: "52538822" rawrerz" 2012/09/09, 9:17:54 "Locality Event" 2012/09/09, 9:17:54 "Locality Event" 2012/09/09, 9:17:54 "READ/WRITE: ['PASS',false,'31842277',[135,[6849.7,2499.87,0.754579]],[["FN_FAL","glock17_EP1","ItemFlashlight","ItemKnife","ItemHatchet","ItemRadio"],["FoodCanFrankBeans","ItemSodaCoke",["20Rnd_762x51_FNFAL",19],"20Rnd_762x51_FNFAL","20Rnd_762x51_FNFAL","20Rnd_762x51_FNFAL","PipeBomb","PipeBomb","PipeBomb","17Rnd_9x19_glock17","17Rnd_9x19_glock17","ItemBandage","ItemBandage","ItemBandage","ItemBandage"]],["DZ_Backpack_EP1",[[],[]],[["PipeBomb"],[12]]],[22,51,51],Camo1_DZ,0.96]" 2012/09/09, 9:17:54 "LOGIN LOADED: B 1-1-A:21 (rawrerz) REMOTE Type: Survivor1_DZ" 2012/09/09, 9:17:54 "Locality Event" 2012/09/09, 9:17:54 "WRITE: ['PASS']" 2012/09/09, 9:17:54 Server: Object 44:6 not found (message 94) 2012/09/09, 9:17:54 "READ/WRITE: ['PASS',[false,false,false,false,false,false,false,12000,[],[0.0659969,0],0,[614.969,554.162]],[0,0,0,0],["glock17_EP1","amovppnemstpsraswpstdnon",42],[135,[6849.7,2499.87,0.754579]],-70593]" 2012/09/09, 9:17:54 "LOGIN PUBLISHING: B 1-3-K:1 (rawrerz) REMOTE Type: Camo1_DZ" 2012/09/09, 9:18:14 "STARTING LOGIN: ["68493062",B 1-1-A:22 (WAGGSS) REMOTE]" 2012/09/09, 9:18:14 "LOGIN ATTEMPT: "68493062" WAGGSS" 2012/09/09, 9:18:15 "READ/WRITE: ['PASS',false,'31840751',[335,[6865.24,2485.85,0.747494]],[["FN_FAL","NVGoggles","Binocular_Vector","ItemFlashlight","ItemMatchbox","ItemRadio","ItemToolbox","ItemMap","ItemGPS","ItemEtool"],["ItemPainkiller",["20Rnd_762x51_FNFAL",19],"20Rnd_762x51_FNFAL",["20Rnd_762x51_FNFAL",19],"20Rnd_762x51_FNFAL","20Rnd_762x51_FNFAL","PipeBomb","PipeBomb","PipeBomb","ItemBandage"]],["DZ_Backpack_EP1",[[],[]],[["PipeBomb"],[6]]],[45,75,75],Soldier1_DZ,0.96]" 2012/09/09, 9:18:15 "LOGIN LOADED: B 1-1-A:22 (WAGGSS) REMOTE Type: Survivor1_DZ" 2012/09/09, 9:18:15 "WRITE: ['PASS']" 2012/09/09, 9:18:15 "WRITE: ['PASS']" 2012/09/09, 9:18:16 "READ/WRITE: ['PASS',[false,false,false,false,false,false,false,12000,[],[0,0],0,[658.467,488.749]],[0,0,0,1],["FN_FAL","amovppnemstpsraswrfldnon",42],[335,[6865.24,2485.85,0.747494]],-24821]" 2012/09/09, 9:18:16 "LOGIN PUBLISHING: B 1-3-L:1 (WAGGSS) REMOTE Type: Soldier1_DZ" I'm not interested in discussing this any further, pretty self explanatory.

To clarify you were not banned for destroying anything. Also worth mentioning these entries would have tripped an automated ban by Anti-hax if Object Flood Protection were enabled.

Thanks, I'll wait for an appeal from Moe. Unfortunately you and WAGGS won't be returning to our servers but you're free to appeal the listing to the CBL at the links I provided.

I was banned therefore admin abuse? :rolleyes: I noticed you and WAGGS earlier but decided to just take a mental note rather then ban given the limited log entries. https://code.google.com/p/dayz-community-banlist/issues/detail?id=956 https://code.google.com/p/dayz-community-banlist/issues/detail?id=957 as soon as you two got banned players started dropping this guy popped up https://code.google.com/p/dayz-community-banlist/issues/detail?id=958. Normally I look for more entries but it was too much of a coincidence to let it slide. After you three were banned everything returned to normal including VOIP. Sincerely, - Vortech @ OCN

Submit (https://code.google.com/p/dayz-community-banlist/issues/entry) your findings to the Community Ban List (CBL) https://code.google.com/p/dayz-community-banlist/. They track the number of these occurrences reported on a player by player basis and commit names if necessary. At this point I'm sure it takes many but still worth submitting as if every server submits eventually they'll get the cheater. I'd recommend you ban local in the meantime and submit to the CBL, if they appeal then you can sort it out but that has never happened to us and we've been at it a long time now.

I didn't notice it earlier but dwarden from BIS posted a ban list including some of his bans to the CBL (https://code.google.com/p/dayz-community-banlist/). I'm not sure if any are dupes to the CBL but it's 128 cheater GUIDs so add it to your bans.txt and profit. Thanks dwarden! :) Source: https://code.google.com/p/dayz-community-banlist/source/browse/bans/dwbans.txt?spec=svncc48507bc9f9a2107c4733fc119cb94f49fb75c6&r=cc48507bc9f9a2107c4733fc119cb94f49fb75c6 This is not my list, I'm just simply making sure people see it.

Search for posts by me including BEC for the specifics but the scheduler is what you want (http://ibattle.org/install-and-configure/setting-up-the-scheduler/). As for FDPro there are some basic details on it, just look through the tabs though and you should be able to figure it out. I hope this was helpful.

Sure just add them to your bans.txt, we ban all submissions locally to protect ourselves then submit to the CBL so everyone can benefit. The CBL doesn't instatly commit GUIDs, there are some violations they allow cheaters to rack up. For this reason and the sake of your players you should always ban local first as they've already found their way to your server once. Welcome back, you're doing great already btw. :)

Need more info, show us more of the logs. The variables _whatIsThis and fap_fnExec are often seen when cheaters remote execute on players in your scripts.log if you're running the vanilla CBL filters. Here are some examples (http://dayzmod.com/forum/index.php?/topic/80719-psa-false-remote-execution-on-players-whatisthis-long-weekend-incoming/).

Please be sure to post (https://code.google.com/p/dayz-community-banlist/issues/entry) your findings to the Community Ban List (CBL) so more admins can benefit (https://code.google.com/p/dayz-community-banlist/). Nice job btw. :)

Try updating to beta patch 96751 (http://www.arma2.com/beta-patch.php) source: (http://forums.bistud...t-1-62-release))

Update to beta patch 96751 (http://www.arma2.com/beta-patch.php) source: (http://forums.bistud...t-1-62-release))

We're pleased that so many players call 1992 home, I'm personally not so pleased duping was so rampant but 1.7.2.6 is doing wonders already. If you're looking to take your time on the server to the next level make sure to hop on our VOIP and join in. The server is provided to the community by Overclock.net and we've got a great bunch of friendly gamers on all the time.

You're already off to a great start, your players are lucky. Here is an older post I made updated to include the new publicvariable.

Thanks for the report, our players rock. A few others also posted about the incident so I've got a reply ready made :) Sincerely, [OCN]Vortech of Overclock.net

Thanks for the report and the story, I reviewed the chat logs, and he did offer quite a few people gear throughout the night. I've flagged his info and passed it on to our staff members. We'll be watching him closely if he returns just to make sure. Thanks again, [OCN]Vortech of Overclock.net

You guys are shameless, lmao.. Better late then never.

I'm sorry you were effected by a cheater while on our server but like I said: This server for example is currently in the Top 10 ranked US servers on GameTrackers.. Until BIS or BE find a way to combat mass-teleport killings there is nothing admins can do. It's your choice to play on a lower-pop server but if traffic picks up I assure you a cheater will visit and attempt to ruin the day. If it is any consolation we submitted 8 solid bans to the CBL (https://code.google....munity-banlist/) from last night as well as listed a few more locals for suspect activity. We are currently utilizing a custom publicvariable filter and effectively stopping that many more griefing attempts then any other server at this time. The CBL is only logging publicvar entries, we are both logging, and kicking/stopping executions in real-time. Sincerely, [OCN]Vortech of Overclock.net

GUID: 1af9e3d4cd91bd3f953f51982b9c1772 Username(s): GrimReaperBitches101, Jean Server: Not going to make it easy. Time: 22:20 Proof: Description: This baddie logged on to the wrong server, went invincible, and got in a fire fight with two of our staff. While speaking with our staff the user gives away his identity, confirms he is cheating, and has a functional bypass. We kick the user pending a ban and he had come back on another user name as if it would hide his identity. Functional bypass means no proof, which means no post to the CBL, but we can still share the story and GUID here for other admins to profit. Enjoy!

Ok thanks for the clarification, in all seriousness you should read up on the functionality of the different bypasses.

If you have logs on this user please make sure to submit (https://code.google.com/p/dayz-community-banlist/issues/entry) it to the Community Ban List (CBL) so more admins can benefit. https://code.google.com/p/dayz-community-banlist/

>.> I can't tell if you're trolling or not.. *sigh

Functional bypass, no entries. This user for example never appeared in the createvehicle, and had a skin that should have been listed on login.

Yes they are, you sir picked the wrong thread to spread misinformation. The staff gave in to a few cry babies about IPs but GUIDs are fair game. Yes that public list is the Community Ban List (CBL) in my signature https://code.google.com/p/dayz-community-banlist/. We normally don't make threads like this but this player made it too easy and was confirmed a cheat by two staff members in VOIP in real time, and the player foolishly gloated in direct chat. More admins to to submit bans to the CBL and more admins need to share bans in general. Oh yeah, I'd post all his info if I could.. Unfortunately the DayZMod staff here got bullied.

Exactly.