(OCN)Vortech

Ninja filter release (keep up the good work Dwarden)! :beans: https://code.google....30ccdf8ec7cb78d Also worth mentioning: ARMA 2: OA beta build 97239 (1.62 MP compatible build, post 1.62 release): http://forums.bistud...t-1-62-release)

Currently there is no way for a vanilla hive server, you'd need to request a new ID from BIS to get a fresh start.

Like I replied to your CBL issue (https://code.google....munity-banlist/): I assumed you were a grandfathered ban as searching your GUID doesn't show any submissions. I decided to stop being lazy and run it against the bans.txt and it isn't listed. If you are CBL banned then your GUID is wrong. To find your GUID connect to a non-cbl server and type: #beclient guid Search the output against the CBL 'All issues' and the bans.txt filter to see if you're on it.

Stop typing for a second and try what I suggested: Now that you've corrected your uninformed point of view we can move forward. I imagine you're not an administrator so it's OK that you don't get it OR support the cause. Trust that informed administrators are working as hard as they can to keep your servers safe for you to play on. If the basis of my position continues to pass over your head then I'll stop wasting my time responding. :thumbsup:

Good stuff, please make sure to submit https://code.google.com/p/dayz-community-banlist/issues/entry your findings to the Community Ban List https://code.google.com/p/dayz-community-banlist/ so that everyone can benefit, :beans:

As an update the CBL committed this user to the ban list :beans: 5a7e8fec7f59a2557afe4c4875fc5753 -1 W 4d9b2182 0x0f44d938 Only a troll like you would waste your time to do something like that.. Much like your posts. I find it hilarious you're still at it, the CBL is going strong and protecting servers. We see about 10-14 cheaters denied access to each of our servers per day THANKS TO THE CBL and the admins that contribute to it :D. People have lives, they don't have time to falsify multiple submissions to get a single GUID committed to the list.. lol! Stop embarrassing yourself, familiarize yourself with the CBL https://code.google....munity-banlist/, and let this thread go because the cheater got what he deserved.

Your issues is you were caught TWICE by two different administrators. While the OP may not have gone about making this thread the right way, he still identified you. The value in this is you posted some garbage in my CBL submission and I was able to find another report on you thanks to the OP. Your time with BE will come, until that day comes the CBL acts as a bridge allowing admins to protect the DayZ community and share reports. I am not connected with the OP, the submission I linked above is from one of our servers. OP, make sure to collect your logs and submit proof to the CBL https://code.google.com/p/dayz-community-banlist/issues/entry.

More of him here https://code.google.com/p/dayz-community-banlist/issues/detail?id=1404, I can't find info on that server admin.

Reach out to the admin Jagmas http://dayzmod.com/forum/index.php?/user/15233-jagmas/ or http://dayzmod.com/forum/index.php?/topic/40603-us-77-dayz-server-thread/ and ask him to submit the proof to the CBL (https://code.google.com/p/dayz-community-banlist/issues/entry) so we can all benefit from it.

Here's some more for you guys https://code.google.com/p/dayz-community-banlist/issues/detail?id=1041

Why didn't you just say that in the first place? Oh that's right.. You first connected to our server 09:04:59 09:04:59 : Player #8 ash (IP) connected 09:04:59 : Player #8 ash - GUID: 29078a6f88f7cdad8ac9edc895c20e6a (unverified) 09:04:59 : Verified GUID (29078a6f88f7cdad8ac9edc895c20e6a) of player #8 ash With 2012/09/20, 9:05:47 "STARTING LOGIN: ["60307142",B 1-1-A:20 (ash) REMOTE]" 2012/09/20, 9:05:47 "LOGIN ATTEMPT: "60307142" ash" 2012/09/20, 9:05:48 "READ/WRITE: ['PASS',false,'33178029',[43,[9700.71,1708.79,0.00194979]],[["ItemFlashlight"],["ItemPainkiller","1470Rnd_127x108_YakB","1470Rnd_127x108_YakB","1470Rnd_127x108_YakB","1470Rnd_127x108_YakB"]],["DZ_Patrol_Pack_EP1",[[],[]],[[],[]]],[25,33,33],Survivor3_DZ,0.96]" 2012/09/20, 9:05:48 "LOGIN LOADED: B 1-1-A:20 (ash) REMOTE Type: Survivor1_DZ" Your first kick was at 09:06:07 09:06:07 : Player #8 ash (29078a6f88f7cdad8ac9edc895c20e6a) has been kicked by BattlEye: PublicVariable Value Restriction #37 Logs reviewed and ban issued at 10:51:27 10:51:27 : Player #3 ash (29078a6f88f7cdad8ac9edc895c20e6a) has been kicked by BattlEye: Admin Ban (Nope. Ban submitted to DayZ CBL.) You were not taken control of on our server, you joined with it.

We noticed this too, I'm maintaining a LOOSE list of what we perceive as confirmed cheaters. We decided to share our list with the participants of the CBL (USE AT YOUR OWN RISK) until the CBL pushes a formal update. https://code.google.com/p/dayz-community-banlist/issues/detail?id=1368 https://code.google.com/p/dayz-community-banlist/issues/detail?id=1399 https://code.google.com/r/dayz-overclocked/source/list

+1 for Bliss

https://code.google.com/p/dayz-community-banlist/issues/detail?id=1380

I like the direction you're going, I haven't personally seen any examples of cid#2:oid#1 but hopefully these can help you (https://code.google....ter:overclocked). So far we've been spot on, my only doubts are the single line executions and if a costume change or something glitchy can cause it. All testing we've done says no but I've still reversed a single line execution setpos ban, at least until we get more info from BIS.

I replied to your post over at OCN by way of PM. :huh: http://dayzmod.com/f...gs/#entry841350 http://dayzmod.com/f...gs/#entry841400 http://dayzmod.com/f...gs/#entry841442 http://dayzmod.com/f..._20#entry842102

I replied to your post over at OCN by way of PM.

Custom filters stopped him early, confirmed cheater. https://code.google.com/p/dayz-community-banlist/issues/detail?id=1020

Thanks for your report and details, I had a feeling when I reviewing the logs a few people were working together. I assure you we got as many as we could (as many as BIS allows us), considering 32 suspected cheaters submitted to the CBL in the last 22hrs <_< It can always be better and faster but we do what we can. If you do encounter anything suspicious hop on our VOIP give a report to someone, post in the respective US 1992 thread (http://www.overclock.net/t/1290323/us-1992-v1-7-2-4-beta-95417-3dp-on-ch-on-np-off-gmt-6), or PM a DayZ admin on OCN. None of these recommendations are required of our players, but it allows us to respond quickly. I do hope you choose to continue joining us on US 1992, we're about to bring our inverse servers online, after we finish load testing our Lingor instance US 1442 and US 1992 Lingor :thumbsup: . Sincerely, [OCN]Vortech of Overclock.net

This thread was just brought to my attention.. I've already indulged this user once so if you'd like to read everything in the proper context be sure to see my posts here (http://dayzmod.com/forum/index.php?/topic/89573-us-1992-admin-abuse-banned-w-submission-to-cbl-for-blowing-up-buildings/). I applaud the user for his new found theory and poor attempt to twist my words out of context. Maybe they'll be some new excuse in the next thread when he dreams it up :lol:. In all seriousness though, we try to run things as professionally as possible on our servers. The lengths this user is going to slander me personally,OCN, and the inconsistency he is displaying while doing it is a bit concerning. Please if anyone wishes to comment in this thread be sure to read over my replies in the original thread. :beans:

Thanks for the report and the story, we banned a number of teleporters and submitted them to the CBL (https://code.google.com/p/dayz-community-banlist/issues/list?can=1&q=pos&sort=-id&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary&cells=tiles). To clarify the server DID NOT "get hacked", based on your report a cheater mass-teleported the players. Sincerely, [OCN]Vortech of Overclock.net Once again, this server is secure and US 1992 HAS NOT "been hacked".

Don't forget to share your bans (https://code.google.com/p/dayz-community-banlist/issues/entry) with other admins by submitting them to the Community Ban List (CBL) https://code.google.com/p/dayz-community-banlist/. If you ever doubt any entires search the CBL submissions (select all issues) and see what pops up. You're off to a great start.

lol, you're clearly not getting it. Good luck with your witch hunt.

lol, dude there are many other servers to play on. Like I said earlier, our servers however you're just not welcome on. I've banned you locally which protects our players and I submitted your ban to the CBL so that others may benefit. Certain types of submissions require multiple admins to report them before the GUID is committed, the point here is you need to appeal at those links I posted not here. I have no idea why you're still going on about this here, your bans meet the requirements of the current DayZ server administration rules (ie. log supported) so that's it. As far as specifics I'll spell it out for you one time: We can see here you logged in with 4x PipeBomb not the 12 you said (which btw wouldn't fit for all intensive purposes). While nobody bans solely on *.RPT logs, reviewing them afterwards can be helpful as it was in this situation. Also worth noting the suspect gear you both have and the fact that your combined charges do not equal both your claimed 12 or the total charges we see in the other logs. 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" WAGGSS has 4x, so our total is 8x between you both. 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" You're responsible for 16x, and WAGGSS has 12x for a combined total of 28x. Not to mention the additional 4x entries ten minutes later. 09.09.2012 09:18:28: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:25 44:4 [6850,2499,6] [0,0,0] 09.09.2012 09:18:39: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:26 44:4 [6851,2508,6] [0,0,0] 09.09.2012 09:18:50: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:35 44:4 [6862,2498,6] [0,0,0] 09.09.2012 09:19:03: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:45 44:4 [6869,2503,6] [0,0,0] 09.09.2012 09:19:09: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:46 44:4 [6872,2493,6] [0,0,0] 09.09.2012 09:19:20: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:47 44:4 [6864,2485,6] [0,0,0] 09.09.2012 09:19:37: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:49 44:4 [6863,2496,6] [0,0,0] 09.09.2012 09:21:27: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:51 44:4 [6902,2492,10] [0,0,0] 09.09.2012 09:24:27: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:52 44:4 [6671,2305,6] [0,0,0] 09.09.2012 09:24:34: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:54 44:4 [6688,2304,6] [0,0,0] 09.09.2012 09:25:17: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:59 44:4 [6549,2309,6] [0,0,0] 09.09.2012 09:26:11: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:66 44:4 [6587,2385,6] [0,0,0] 09.09.2012 09:26:18: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:67 44:4 [6596,2394,6] [0,0,0] 09.09.2012 09:26:52: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:71 44:4 [6563,2414,6] [0,0,0] 09.09.2012 09:27:11: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:73 44:4 [6577,2411,6] [0,0,0] 09.09.2012 09:27:17: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:74 44:4 [6568,2418,6] [0,0,0] During this ten minute gap there were VOIP reports of two players teleporting and killing players. Coincidentally once the three bans were added all suspect activity on the server stopped. 09.09.2012 09:37:08: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:147 44:4 [6504,2530,6] [0,0,0] 09.09.2012 09:37:29: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:149 44:4 [6512,2523,9] [0,0,0] 09.09.2012 09:37:40: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:153 44:4 [6509,2528,14] [0,0,0] 09.09.2012 09:39:40: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 44:155 44:4 [6812,2707,6] [0,0,0] 09.09.2012 09:21:32: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:11 43:4 [6896,2486,6] [0,0,0] 09.09.2012 09:21:38: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:12 43:4 [6896,2480,6] [0,0,0] 09.09.2012 09:21:44: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:13 43:4 [6903,2478,6] [0,0,0] 09.09.2012 09:26:33: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:31 43:4 [6575,2401,6] [0,0,0] 09.09.2012 09:26:40: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:32 43:4 [6568,2408,6] [0,0,0] 09.09.2012 09:26:46: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:33 43:4 [6565,2415,6] [0,0,0] 09.09.2012 09:27:22: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:34 43:4 [6584,2406,6] [0,0,0] 09.09.2012 09:27:27: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:35 43:4 [6587,2405,6] [0,0,0] 09.09.2012 09:27:36: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:36 43:4 [6585,2406,10] [0,0,0] 09.09.2012 09:28:46: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:38 43:4 [6581,2383,6] [0,0,0] 09.09.2012 09:28:51: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:39 43:4 [6576,2389,6] [0,0,0] 09.09.2012 09:28:57: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 43:40 43:4 [6572,2397,6] [0,0,0] Also lets not forget the earlier visit (you 7x + WAGGSS 3x more) that put you on my radar. 09.09.2012 06:55:34: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 245:20 245:5 [6545,2313,6] [0,0,0] 09.09.2012 06:55:42: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "G_40mm_HE" 245:21 245:5 [6517,2332,7] [47,-64,0] 09.09.2012 06:56:03: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 245:23 245:5 [6528,2347,6] [0,0,0] 09.09.2012 06:56:42: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 245:25 245:5 [6523,2359,6] [0,0,0] 09.09.2012 06:57:29: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 245:65 245:5 [6582,2383,6] [0,0,0] 09.09.2012 06:57:37: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 245:80 245:5 [6593,2400,6] [0,0,0] 09.09.2012 06:57:47: rawrerz (72.204.112.18:2324) 062ed693052c291dd98e7b6500d6c6f1 - #0 "PipeBomb" 245:87 245:5 [6569,2413,6] [0,0,0] 09.09.2012 06:53:20: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 247:15 247:6 [6679,2293,6] [0,0,0] 09.09.2012 06:53:29: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 247:16 247:6 [6674,2308,6] [0,0,0] 09.09.2012 06:53:36: WAGGSS (142.165.94.60:2324) f9b71e72e991a794ed12006d10bc4b70 - #0 "PipeBomb" 247:17 247:6 [6687,2307,6] [0,0,0] Like XAM said: Not for nothing we've got over 272 bans submitted to the CBL (https://code.google....ter:overclocked) with only a single appeal which we provided logs for and was committed. Also worth mentioning the server you were banned from is ranked in the top 40 on GameTrackers, and is the 8th in respect to US servers including private servers. The point here is we see lots of logs, I personally spend time reviewing all of our submissions to the CBL:. Nobody is right all the time BUT given the state of this game (alpha) and how hacked to all hell it is as Admins need to do everything we can to protect the players that choose to play on our servers. When you add everything up, createvehicle entries, the *RPT entries, timestamps, the chatter in VOIP, your attitude here, and our experience reviewing logs it becomes more obvious. In the end the logs tell the story so like I suggested appeal the CBL submissions if you believe the ban is somehow erroneous as it will effect you much more then being locally banned from our servers. The CBL sees even more log entries then we do, so they'll be an even better judge of them then us. We are satisfied with our position on these bans and as such, they will stand.

lol, you're missing the whole thread. Start from the OP and work your way down next time ;)