deren93@hotmail.com

Unless you can't read the last 4 posts, it's very clear that I am dealing with any and every appeal I get =/ Thanks for the offer though, but I'm the only pperson really able to deal with them currently

Hiya, I'm heavily overloaded with Uni work right now so I can't join any TS :( To sign up on opendayz.net you press login or singup in top right corner, change the option to "No, create an account now" put your email address in and hit "Sign Up". I check that forum the most often (currently every few days) so it's the fastest way to have a private conversation with me. Hopefully you can get it working, otherwise you will need to PM me on here (I rarely check this, you just got really lucky today lol).

Hi SCHNAEPFE, The server you were caught hacking on was actually my one. I recognised your name before I even looked up the ban in the logs as you were one of the first group of hackers we had on our server (UK 999 DayZ Police, but called SWAG YOLO BOATS at the time). I remember the event very clearly, there were about 4 or 5 of you that spawned in a lot of choppers on the coast - a big giveaway at the time as the only heli was our admin one. One of my admins banned all of you who kept appearing in these helicopters via the ingame admin panel which bans playeruid only. You all then rejoined with different player id's under the same respective guid and continued to massacre people spawning in choppers. It's possible that one of your crew was executing the code on all of you and I do have some code in the logs which is suggestive of hacking. Combined with your efforts to rejoin the server with different playeruids (only achievable through non-legitimate methods) I stand happy with my decision to add the ban (ban was added ~november 2012, perhaps december). However, I am open to any appeal from you and your friends. If you'd like to have a chat about this please visit the opendayz.net forums and PM me on there (username is Doc) and I will be more than happy to help us resolve this. Thanks Doc

BanZ has not died people, but sorry for the lack of updates. I am a university student and that has taken over my time at the moment, as well as work/volunteering etc (to the extent I have closed my DayZ server also). I will try and chase up BanZ members to sort out new bans being added and perhaps appoint someone with more time to oversee the project. I made BanZ with the best intentions but real life comes first, I hope you all understand.

Nobody is forcing you to participate in the discussion here Ingasmeeg and Private Evans. My insights here are almost solely for the benefit of JoeysLucky22, it is within my right as a member of the forum to post it. You will certainly not be the one to take that liberty, I'd appreciate it if you don't continue posting here as it's not directed at you. Thank you. 'nuff said Liquidmind - Reddit does seem to influence the decisions made here unfortunately.

I'll start this insight by saying I was one of the people that complained in the 1.7.6 patch notes. Why? Because 1.7.5.1 simply was a shambles, and the thing spamming the 1.7.6 patch notes was a list of vainly named can models of developers who the community was already upset with. We wanted something to moan at and took that opportunity. Boy, we were wrong. The models themselves are great. If you haven't seen them all, you can see them here. Why didn't we like them then? My thoughts are that it's how the release was worded. Seeing a list of random names in a model list isn't what we wanted to see, but perhaps the models should have been shown to us more directly and the names should have been more clearly stated as description only and not the object name. The community response then? Yes, our response to moan was too fast with too much prejudice. Equally, however, the response to completely remove the models in a hotfix almost solely for that reason was also too fast. If a decision was made by the next release, there would have been time for the heat to die down and to gain a true opinion from the community. What we are left with now is half a community moaning about the new models being added and the other half moaning about them being removed. But what now? There is a developer who has made some really sweet models but had his work torn to pieces by our peer-review community. We shouldn't let his hard work go amiss. The models should return, but the marketting should be different. I don't have an issue giving developers credit for their work, but after the shambles of 1.7.5.1, the naming should have been less vain and made less of a "one-shot glory attempt" and perhaps focussed more on the actual benefit here. New items, new models. The cans still exist for the same reasons, but they just add another shade of blue to the game. My opinion? Communtiy: Let's not rip this poor guys work up from our underlying fustration. Devs: Keep the models. Name them more subtly. Market them better. JoeysLucky22: I hope this gives some input as to why I think things went wrong. Don't stop modelling ;) -Doc

I withdraw the following comment. I have been chatting to R4Z0R49 on skype for the last half an hour and he's an alright guy. He hasn't killed the mod, but the system has. As a collective, all of the development team need to change the system if the community mod is to stay afloat! R4Z0R49 has killed this mod. People want updates to fix core issues and he adds crap like "(Soda) R4Z0R soda (R4Z0R)" This mod was great and I have been a loyal player since the beginning and helped develop private hives, but for me the mod is now dead. I said goodbye to my servers last night and I doubt I will be hosting any again for a long time until this mess is fixed. Your players all feel the same. Just ask all my hundreds of regulars that quit dayz to play wastelands and stuff.... EDIT: Another developer (to be unnamed) just gave me beans for this post, and R4Z0R bitched to him to take it back....

HAS FakeWeapon {}; KILLED PRIVATE HIVES? Since 1.7.5.1, something new and bad has appeared in dayz_anim\config.cpp. This file is where arma 2 classnames were banned, but since the update, something new has appeared.in the cfgWeapons class: class RifleCore; class FakeWeapon: RifleCore { scope = 1; stopThis = true; type = 0; cursor = ""; cursoraim = ""; sound[] = {}; magazines[] = {"FakeMagazine"}; }; This new class basically despawns any classname flagged as fake weapon. This is great... for public hive dayz. But in private hives we have prided ourselves in offering different lootspawns based on the classnames that were non-spawning by default, but still not banned. Here are some examples, to name a few: class BAF_AS50_TWS: FakeWeapon {}; class G36_C_SD_camo: FakeWeapon {}; class AK_107_GL_pso: FakeWeapon {}; These weapons will now be non-equipable in dayz, Try to equip it or spawn in with it and it despawns.Sorry devs, but this sucks balls. You have taken away one of the niches of private hives. We came to your rescue when players were getting bored of your overcrowded laggy servers and offered new map ports and less lag, whilst decreasing the lag on your servers. Now this is how you kill our servers. It's only something small, but there was no need. If you didn't want the weapon in the first place, you should of just banned it and not bothered with this FakeWeapon nonsense. /Doc

Those with issues regarding previous ban from other lists, do not let your past experiences cloud your judgement and have prejudice on your opinions. Every ban on banz follows our guidelines on being beyond any reasonable doubt that the individual executed the piece of code question. On the bans list you download, you only see a brief reason, but behind every ban is a comprehensive note which contains all the evidence that justifies the ban. The evidence for all bans is viewable by all union members for review, all of these admins have also been tested on their ability to justify bans. Even after all this process, I still check each ban individually. So, maintaining a good quality bans list is not easy, but rest assured that we have taken every step possible to make sure every ban is justified. If we are ever unsure, we do not ban. Hackers will always come back another day, so there is no need to risk putting potentially innocent players on banz. In the unlikely event where an innocent player is banned, they can appeal whereby the notes and evidence are reviewed again. This has not yet happened and I hope it does not. I personally have a private bans list for the occasions where I know someone is hacking but cannot gather enough evidence for banz. So, next time you see a ban added to banz, you can understand the effort and input behind that ban. It is not a 'for the hell of it' type of affair. ;)

Ofcourse, time is the most important factor. I use some basic math (pythagoras) to work out changes in linear distance between each incremental point, use the timestamps in some mechanics/SUVAT equeations with it to get a rough speed in m/s then compare the speeds.

Hi Ander, With the availability of bypassers these days, catching script execution by using an anticheat script is increasingly difficult, you'll be lucky to catch the odd copy/paste script kid. Even then, anything caught by that can also be detected by analysis of your script logs. One programme i use is pyBEscanner created by torndeco. It relies on scanning your script logs and parsing them for known cheats with the ability of automatically banning the individual, this is one of my favourite tools. Other detection methods I use initially rely on database analysis to begin with. I use a method created by Peep to insert any character data updated into a history log. When you need to analyse data, it's handy to see the history of individuals as large changes in coordinates / changes in equipment can flag somebody for further investigation. Ontop of that, I run a simple SQL query I created to manage vehicles in the database. Any illegitimate vehicle is tracked to show details of nearby players and their actions every given interval and is automatically despawned on server restart. As extras I also use dayzmapper, gcam and other admin tools to allow myself and other admins to investigate incidents better. If you are looking for a complete server-side script that will ban every script kiddie, then I am afraid one simply doesn't exist and probably never will. There are,however, variations of scripts created by a popular cheat-script creator who shall remain nameless. These are bypassable to anyone with some coding knowledge, but if you want the link to them, please sent me a PM, as I do not feel comfortable posting what is essentially a hack on here. Doc

That looks great. If the length is still a big issue, I think maybe "banzunion.com (ID:123)" would work, but it is nice seeing the whole thing. I can set up a seperate URL for you that only has it in that format if you want.

Great stuff, that's perfectly fine. My only issue is the lack of the original BanZ ban reason. Is there any way you can keep the original reason as well as your DaRTBans tag? Main problem is the Ban ID for appeals.

You can message me on the OpenDayZ.net forums (my name is Doc) or you can message me on here, but I may be slower to respond as I don't check this often Oppa is completely correct (he is one of the union members). The public release doesn't actually have the DayZ community banlist oppa, only the version you generate from the admin panel has the option of the dayz banlist :)

Just set one up for you http://www.banzunion.com/files/latest.txt I couldn't test the code because there are no bans to update, but I am sure it will update itself :) If it doesn't update then let me know