Sanadorn

Yes please remove it. If it stays in game it NEEDS a decay timer to go away (rust) in the weather naturally because right now it doesn't stop zombies and is purely a griefing tool.

Pretty awesome sounds like a great initiative :) My group used to be all bandits except for me but the longer we've been running our own server the more I've managed to get them towards friendlier rules of engagement. They've really enjoyed it because honestly the *rush* of killing a player is about half of that associated with making non-hostile contact and discerning the threat level and all the nuance that goes with it... It's amazing fun. I'll PM you the server name if you guys want to check it out. We don't usually have major skiddie problems but they do appear once in a while before being logged and banned.

Just configured it, giving it a shot... Might want to send people to http://ibattle.org/i...-and-configure/ before they start the server with it installed because it needs to be set up first! :) One question I did have was setting up the scheduler... How do we know the server's local time? I'm assuming it's set up by the time selection under server config but just want to confirm. Our server is offset slightly (just 3 hours) so that we get a good spread of daytime and night time which means the scheduler has to be set up with the offset as well unless the server is using Central time or something else. And for the record you guys are awesome... Excellent host, great performance even with a full server no lagging whatsoever.

You're welcome to take a look at US 2133 Server timezone is currently set to UTC-10 (Hawaii) We get the occasional skiddie but an admin is almost always online to do a halt so the damage is mitigated as much as DayZ's rules currently allow. The server is located in Texas. We get sub 160ms pings to japan and 140s to the UK. The NA continent sees sub 70ms latency. Our TS3 server is available if you want to join the regulars I can PM you the details.

Just a bug on the parsing; Players with ASCII characters in their name are causing the reporting component to die... e.g. ™ ♥ ♫ etc etc

It means Justin is a bad pilot. He crashed.

Your sir are a gentleman and a scholar, my :beans: , they are yours

So I've posted about this issue a few times because it was very negatively effecting my server and the players that frequented it. HFB and Vilayer and I assume many of the other VPS hosts do not allow regularCheck to be enabled. This is an ArmA II server script that requests a hash value of the pbo files from each client that is connected and at various intervals. Many VPS hosts have jumped on checkFiles[] = { "AddOns\plants2_Bush.pbo"; "AddOns\plants2_Clutter.pbo"; "AddOns\plants2_misc.pbo"; "AddOns\plants2_Plant.pbo"; "Expansion\AddOns\plants_e.pbo" }; As a solution and this is why you're seeing those items in your log files. These are UNSIGNED so they show up in the logs as modified data files. They can be completely missing and you will still get the same log entries for the client connecting. The function itself was replaced by verifySignatures and isn't doing anything useful for you according to Bohemia's knowledge-base. The proper way to fix the no plants and other file modification issues is to; 1 - Enable verifysignatures = 2 2 - Enable regularCheck = "" or remove it from your .cfg entirely. This is DEFAULT ENABLED in the ArmA II server it's that important. (in your server.cfg you'll see it as regularCheck = "{}" which means "disabled, don't check anything." verifysignatures will make sure all of the signed client files are unmodified and in place. regularCheck will make sure all of the unsigned files (like plants) are unmodified and in place and match. This feature uses a bit more disk I/O which is likely the economic factor behind overloaded VPS hosts not enabling it. If you cram 6+ DayZ servers onto a single box and have it on I imagine that causes problems... well rampant cheating is a pretty big problem too... Get a better host is the only solution you have right now, sorry :(

Is it allowed to use your server hardware to host, for free, a mod and a variant on a mod? Sure?

Just a quick no drama notice to anyone that is a regular. Grab the stuff you want to take before the 15th as the server will be closed. The MOTD will be updated to reflect this as well. (We will still be supporting DayZ in other ways, just not with this server. Have fun guys!)

Tested this with a bus we couldn't get to go away... shot it, drowned it, burned it and blew it up.. then went nuclear option and parked it outside the map for a few days.. it's still there... watching us.

That function is deprecated. Stop using it because it doesn't do anything with unsigned files. You're looking for regularCheck = ""; See http://community.bis...wiki/server.cfg -edit- Just thought I'd expand a little. Bushes, trees, rocks and a few other things aren't part of the current signed package from BIS. This is why regularCheck is currently the only option to catch folks that manipulate these files. Yeah it causes more I/O but it stops them cold until BIS adds foliage to the signed package. VerifySignatures = 2 is important to have on because it catches other file modifications but it does not currently catch what the OP was asking about..

AFAIK you don't want to log in as administrator in the game itself any longer. The admin scripts are *easily* hijacked so have been disabled in many instances. You need to use BERcon or something similar. BERcon details and download can be found @ http://community.bis...i/BattlEye#RCon Details about why you don't want to use in-game rcon @ http://forums.bistud...rver-Read-here!

No it's doing something with that performance... It's keeping .pbo modding cheaters off the server, full stop. Also if a host is stuffing 5 or 6 instances on a node I can see it causing issues but then again why doesn't DayZ server pricing just incorporate fewer instances per node for those of us that want a better product and experience? I'm willing to pay more for the option... not being unreasonable here :)

Who is your host? I know for a fact that HFBservers and Vilayer don't allow this to be enabled which is insane. Don't pack as many on a node fellas and charge a bit more for a more secure gaming experience.

Re: invisible trees, rocks, buildings Editing the .pbo files doesn't just make these things invisible to the client it makes them able to travel and shoot as if they weren't there. That means through trees, through walls, rocks and all the rest. From http://community.bis...wiki/server.cfg Yet the reality is it seems all slot/managed hosts STILL have this disabled outright.

HFB doesn't allow it to be turned on because it causes server lag. BattlEye is apparently working on a fix that is less resource intensive... no idea when that might appear.

It doesn't.

Most of the time my group only plays when I'm either on the server's TS3 or playing myself so I can halt the server when a hacker pops on. Tonight for example we had a guy jump on in a zombie skin with an AK shooting at people, we killed him kind of by accident (he popped himself into the supermarket we were in and was noticed). He came back showing up on thermals for a bit then went invisible shooting green, red and yellow smoke grenades and a M107 at us as we were fixing up a bus. Funny stuff but... "save the bus, server shutdown" and wait the 4 seconds required for script kiddie #191238 to lose interest and latch onto the next shiny server. We've done this only in cases where it's obvious. In this instance the guy was rapid firing smoke... about 20 or so rounds of it, looked kinda cool.. he did kill one of our group before it became obvious it was a hacker. I'm loathe to restart or halt in any circumstance but that crap, Thunderdome, A-10s, etc etc... yeah server halt time and we go play a round of a mech game or a tank game or whatever then restart and the server fills back to 30+ within seconds and we go on enjoying the game. We've had vehicles and tents wiped out a number of times through hacker activity when none of us are on so that's probably the only instance where I'd prefer a password or an effective anti-cheating mechanism.

This is also my understanding of the quoted script excerpt. No ban required.

Where did you find a more recent copy of bans.txt?

First one is usually when a guy crashed and/or blows up a vehicle. Second one looks like the guy broke his legs and picked up "trauma" debuff. Someone more knowledgeable feel free to correct me but I've seen these a few times and that's what it looks like.

Sooo I don't know who your host is but if it's HFB or another host that allows file creation what you need to do is go into File Manager and create a new file at \cfgdayz\BattlEye\ called scripts.txt and the file must begin with //NEW. This file is what tells your server's BattlEye instance what to look for. DayZ distributed a standard one that catches lazy script kiddies pretty well. Better ones just use a BattlEye bypass completely which we can do nothing about. But at least do yourself the favor and get your server's BattlEye working...

The simple answer right now is no. Battleye has some serious problems even when it is working and it is entirely circumvented on the client side quite easily and automatically by most of the scripts and "trainers" that are being distributed these days. US 809 just had a squad of guys join up and within minutes they were raiding camps all over the map. It's incredibly likely they were using ESP or a similar script hack but without logs to prove it I'm more likely to get my server blacklisted by DayZ by banning them with only circumstantial evidence no matter how fishy it looks and smells.

Stop the server and edit BEServer_active.cfg and add or edit the line; Maxping 180 If you want BE to kick everyone with above 180ms ping.