Magotchi

I haven't messed with it since my last update, I stopped hosting a server in the beginning of April, and I stopped playing DayZ a month or so before that. The concept probably still can work, but you'll have to keep your whitelist updated with the current items the game has.

We shut US 303 down in the beginning of April, so I assume ThePimpz is talking about some other server.

Thanks for the kind thoughts, bad_mojo. I'd really thought we were in it for the long haul when we started the server back in about early July, and it's been a fun ride. However, at that point, we had a big group of players from my Counter-Strike: Source clan all playing together on a regular basis, and when I wasn't sleeping, eating, or working, DayZ was all I did. When I wasn't playing DayZ, I was thinking about it or tinkering with the server. Things have changed since then. Everyone in my clan got burnt out on the game. Hacking got bad. The standalone never came out as we had all been excited for. Administering the server became more of a chore I had to complete a couple times a day rather than something I really enjoyed doing. I even eventually got burnt out on playing the game itself. At this point, we've (mostly one guy) basically been dishing out a decent sum of money every month for something nobody in our clan uses anymore, so we decided it was time to pull the plug. It has been a good server, and I've tried my best to keep it a fun place to play, even developing some of my own anti-cheat tools, but in terms of the various servers I've ran and still run, DayZ has been, by far, the hardest game to administrate, so I can't say I'm sad to be done with the job. We'll see what may happen down the road, when the standalone eventually comes out, but until then, it was fun playing with everyone, and I'm glad our clan could be a part a great game and community.

Sorry about that. I've made sure this time.

Your description of the problem doesn't indicate hacks. You said you shot at a guy that had an AS50, and then the same guy with an AS50, minutes later, killed you. I'm sorry, but I just didn't see how that was very conclusive. Additionally, you have no proof that the guy being kicked for an M249 is the same guy you saw with an AS50, and if he had had an AS50, that would also have been repeatedly showing in the kick message. There's no cause for you to be a dick to me about it. As far as the server goes, my clan and I just don't really play much anymore, it's a thankless job to run a server, as evidenced by your response, and it costs money. I have always prided myself on having a server mostly free of hacks, with my own custom-written ant-cheat scripts, etc., and I still do. That I would tell you it's no big deal if I do or don't perma-ban the guy is only a simple fact based on the reality of the situation of the server shutting down in less than a month.

Having invalid items isn't proof that the player spawned the items in themselves. Also, even if I do or don't ban this player, the server is going away on April 3rd.

I don't see it in the dayz_code config files, and I haven't seen anything about it in the changelogs, so I believe it's still bogus.

Well that was a couple days ago, and in that thread, I mentioned that everyone from that incident had been unbanned at that time. I understand why you might have thought that, though.

Unbanned. It was a false-positive due to something in 1.7.6. I've updated my script to whitelist that particular activity (shooting a ton of wooden bolts) in the future. Also, it was not related to the issue burritoman mentioned.

I'm looking into this. In the future, though, please post all ban appeals to our forums at http://clansm.net/ for the fastest response. I only see posts in these forums when I get a Google Alert about them, which can take a while. Edit: It looks like a hacker was able to cause everyone in the server to run the setpos command several times simultaneously, therefore causing everyone in the server to be banned. Everyone from that has been unbanned, and I'm investigating to make sure the hacker's GUID stays banned.

I'll look into this. For the fastest response, though, please post all ban requests to our forums at http://clansm.net/ . I only know about posts in these forums when I get a Google Alert about them, which can sometimes take a few days.

I'm not exactly sure what it is, but it should probably go in the whitelist.

Hohlraum: I have 1 "" in my publicvariable.txt and publicvariableval.txt . Weapons are not logged, and they haven't been since quite a while before I made that other fix, as had been discussed at length in this thread around that time. You were even involved in the discussion, so I really don't know how you believe it's still working (with the public hive and official files). Edit: It just stopped working as of 1.7.5.1 with dayzCharDisco, but it's not been working since before I made the fix with dayzPlayerSave.

Anyone can try this simple exercise on their public hive server to know that it's not working: Search your publicvariable.log for "Colt1911" (or any other common weapon classname).

Yeah. This is the second time I've rejected a ban appeal of his. The first time he said hackers had stolen his GUID and that Steam took care of getting him a new CD key. :-p Edit: Now that I check, he also used the same IP on the forums as in the hack in the original ban appeal. I hadn't checked before since already found it pretty conclusive that he was a hacker without it.

marrr: The method no longer works, so there's no point in updating the blacklist. You're welcome to use my working solution here.

Please post in the clansm.net forums, as you've already done before, benny, or at least start your own thread somewhere to discuss your own issues. Here's why that GUID was banned: 04:11:55 : Player #7 Doc (24.205.151.225:2304) connected 04:11:56 : Player #7 Doc - GUID: 8a944b674b5e0108297ee14e882e4eea (unverified) 04:11:56 : Verified GUID (8a944b674b5e0108297ee14e882e4eea) of player #7 Doc 04:11:57 : Player #7 Doc (8a944b674b5e0108297ee14e882e4eea) has been kicked by BattlEye: Global Ban #8a944b 04:14:37 : Player #12 Doc (24.205.151.225:2304) connected 04:14:39 : Player #12 Doc - GUID: da68bc31fef275046d466707ce9b40f0 (unverified) 04:14:39 : Player #12 Doc (da68bc31fef275046d466707ce9b40f0) has been kicked by BattlEye: Admin Ban (2013-01-31 hacking (bad set variable)) 04:15:30 : Player #12 Doc (24.205.151.225:2304) connected 04:15:32 : Player #12 Doc - GUID: 8a944b674b5e0108297ee14e882e4eea (unverified) 04:15:32 : Verified GUID (8a944b674b5e0108297ee14e882e4eea) of player #12 Doc 04:15:32 : Player #12 Doc (8a944b674b5e0108297ee14e882e4eea) has been kicked by BattlEye: Global Ban #8a944b 04:17:49 : Player #11 Doc (24.205.151.225:2304) connected 04:17:51 : Player #11 Doc - GUID: b0858a491e291f3d50ed2edcbe0f22e1 (unverified) 04:17:51 : Verified GUID (b0858a491e291f3d50ed2edcbe0f22e1) of player #11 Doc 04:20:09 : Player #11 Doc disconnected All from the same IP, Doc (similar to the the name you play with on my server, coincidentally) came in, was kicked for a global ban, then came with a different GUID that I'd already banned for running code via setvariable, then came back with a different GUID (same IP still) to test if that GUID was banned or not, so I banned it. Whether it was or wasn't you, that CD key is compromised, and I will not unban it on my server.

I've unbanned you, giving you the benefit of the doubt.

I've been trying to get a Panthera server up and running for a friend. A fresh Bliss install of it, following the instructions at Bliss' github, creates a server that shows up as running server version "1.7.4" in DayZ Commander, while most of the Panthera servers are 1.7, and therefore the server is marked as having the incorrect version of the game. Similarly, a fresh install of the Pwnoz0r private hive, with either the mission file from Bliss or from the Panthera 1.5 release thread does the same thing. Does anyone have any idea on what I need to tweak or where I can get the appropriate server files to make the server have the right version? The server already works fine as far as I can tell, including vehicle spawns, things saving, the 1.7.4.4 features like the combat timer icon, etc. I know that 1.7 was created by Vilayer, and that for a while there were some issues with them not releasing the server code, but I see in the browser that there are Vilayer, HFB, DayZ.st, and several independent servers showing as running 1.7 in DayZ Commander. EDIT: I figured it out. Apparently I just DayZ Commander actually reads the version in the server's name. When I had 1.7.4.4 in the server's name, DayZ Commander showed 1.7.4, but when I changed it to 1.7, it showed 1.7.

Responded to here, in your duplicate thread..

There are 0 threads without a reply in that forum at clansm.net. I'm looking into your ban, though. EDIT: I also see that you created this thread: Banned from US Dallas 303 during mass hacker attack I highly doubt your tent ban had anything to do with a hacker attack. Also, again, I didn't see it yet because I hadn't yet gotten a Google Alert about it. EDIT: Alright. I found the ban and removed it. It wasn't where I usually keep all my ban evidence. This means I probably meant to remove the ban, but somehow didn't actually remove it from the ban list itself. The tent spam thing's been happening often in the last couple weeks, so I've been giving people a pass on it, but obviously from simply a log perspective, 15 tents shown in a row, many often in the same second, looks pretty suspicious.

I don't use DayZ Anti-Hax, for one, and if you believe just kicking would be an effective way to keep the hacking down in a server, I have to assume you just haven't seen the volume of hacking my server sees. I get false-positives, but they're a small fraction of my bans, which number 10-20 a day.

Your post is very cryptic and doesn't seem to relate to this thread.

I believe he's referring to the hacker-induced false-positive mass ban on US 303, my server: http://dayzmod.com/forum/index.php?/topic/111875-banned-from-us-dallas-303-during-mass-hacker-attack/ Manky is a regular on my server (see him in the list all the time), and he was indeed banned today. It's of course been fixed. Also, you'll always get the fastest response from me by posting ban appeals at clansm.net . I generally only know about threads here via Google Alerts, which can take a while.

Yeah. It's us idiot server admins who don't know what we're doing. I really wish I had some good tips for running a successful server, hopefully from a knowledgeable person like TheDesigner. Until then, I guess my server will just sit empty all day. Anyway, the mass ban was corrected a while ago. A hacker had caused everyone in the server to execute some nasty code, and everyone therefore got banned for it automatically. The anti-hack script has been tweaked to avoid the mass-ban for that particular method for the future. Also, you'll always get the fastest response by posting ban appeals at clansm.net. I generally only see posts here via Google Alerts.