Gogster (DayZ)

Nice work - oh we're not allowed to ban... Whatever shall I do?

With 300+ hours you'd have thought you'd seen enough topics on the subject of hacking and alt-f4.

Exactly - without proof it's just your word against theirs.

Re-install.

Well at least you got a reply. He's confirming what we already know - there's very little they can about it.

With that weapon why not just go and get the items you need? :huh:

There's 17 yes's for server admins and 4 yes's for players who want to play on server running a group ban list. It's not a resounding "let's do it", but it's early days. Given the impetus appears to be towards the standalone version of the game and little is going to be done with the mod I wonder if any effort is worth it? I guess the full version of the game will have anti-cheat (please Lord not BattlEye!) I suppose we just carry on as normal for the moment. Just alt-f4 if you get thunderdomed, godmode, teleported, polymorphed etc...

What a knob.

I've not tried your tool (so too speak - lol) firstly the reason I think this differs is because you require a reporting scenario which some people just won't have that level of access to their server. This system would require no installation and would be open to the server admin community not a locked hidden database. I would like this to be by admins for admins.

You may have noticed, from a few posts today, that I'm parsing my log files for cheats. I've now compiled a list of people using cheats. Is it as simple as adding them to the bans.txt file? Or is there a special process?

Aside from the fact there's a glaring contradiction in the server rules for DayZ mod, they significantly out of date. When they were written there was very little scripting going on on servers.

Would you feel the same way if he'd have spawned in a helicopter?

Not sure what you are on about mate - part of adding to the master ban list is providing the log file entry.

We can only go on what we see, during discussions we also talked about extending this to video reviews, but lets see if there's enough interest to set this up in the first place and get everything in motion, before we look at that.

Everything is logged - this is about server admins having somewhere to add the cheats they find in their log files. BE will never detect as the script for all intents and purposes are allowed in the normal scenario. Cheats are exploiting them for their own purposes.

You can't get to your logs?

This is about detected cheats in the log files - not bans added in a moment of passion.

I think the majority of the comments are suggestions - it all depends on how you interpret them. Remember without the community there would be no DayZ either.

Ok.

createVehicle ['UH1H_DZ' ?

Probably do it via GUID. We're currently looking at ways to share a ban list across server admins. If anyone is interested drop either Inch or me a line.

It's a good point. Inch has made a topic about creating a ban list for server admins and this is where we are struggling for information, if someone in the know (dev's, BattlEye, mods) could give us an insight as to whether this is a worthwhile project or just to leave it to BE. There just seems to be a dearth of information at the moment.

I'm keen on this too, I have some ideas about how to make it work too, but could do with some guidance from the dev's as to whether they would prefer we didn't, reasons etc...

Cheers mate - I'm used to other server logs, Arma is a little new to me. Do you know about manually banning at all? I've asked another question about how now to add them into the bans, it's here: http://dayzmod.com/forum/index.php?/topic/61898-manually-ban-someone/

I, personally, have not problem with that. I'm just cautious about posting names, IP's & GUID's in a public forum. I'm a veteran of the PunksBusted system and we used to have a rule that player information for bans should only be available to admins. Do you have any information about adding them to the bans.txt file? I don't want to go through this process for them to be overwritten by BattlEye on the next update.