Brainling

That would be somewhat disappointing, as it makes it even harder to track down hackers that are killing people. Especially on veteran servers with no tags.

One of my servers regulars seems to have been killed by a hacker (he sent me a pretty convincing video of what was doing on), and I'm trying to figure out the guys name from the logs. I can see the PDEATH line in our server log for my player, but where in the log does it give an indication of who killed him, if it does at all? Should I be looking somewhere else? I also glanced at the script.log, but there wasn't anything out of whack that I could see.

Yep, this was my response as well.

TeamSpeak 3 info thrown in the OP. We had an issue getting Mumble going, so we're going to use a TS3 server at least for now. We may go mumble at a later time.

Again, that's all great theory. In practice, I've never seen anyone actually kicked above that ping value, on my server (and yes, I know it's using the correct cfg, no strange active issues). So YMMV with that method. Be prepared to manually kick obnoxious pings if you see them.

Theoretically you set it in your BEServer.cfg. That's in theory. In practice, I have mine set to 250 in that file, and no one ever gets kicked. I have to manually kick obnoxiously high pings.

Jonnerz: Couple of quick things. The BattlEye script update doesn't appear to be working from the Updates control panel. Fails complaining about 550 unable to change directory. Just a heads up. Second, if you could answer my ticket about my Mumble server (ticket #543181), I'd appreciate it.

No problem. Several people are having this issue, because a large number of the servers updated to the latest beta patch (at the request of our hosts and the DayZ team), but Six Launcher isn't pushing the client update needed.

Six Launcher isn't pushing 95248 to clients yet, so you and your users will have to manually update (as mine did).

There was just a server beta patch pushed but without the resulting Six Launcher push of the client beta patch. People were having to update manually to 95248 for any server that runs the beta patch (like mine). Try manually forcing 95248 to install for your client, or wait for Six Launcher to push it out (which may already be happening).

Just updated to Beta 95248, as per the DayZ teams request. If you guys see any issues, let me know.

I'm working on a Ruby restart script now, so restarts on the server should become much better announced soon.

Change to C# and we'll talk ;)

It's not supposed to, that's supposed to be disabled by the DayZ mission file.

We're pacific, so you should get quite a bit of daylight in your evenings. The server doesn't get dark until it starts to get dark at my house, which is ~9PM pacific. (Exact is GMT-8)