walkerbait421

US 755 will be shut down on 8/31/12. We were going to shut down earlier but extended it one more month in hopes things would get better. Unfortunately things are far worse. Hacking is completely out of control and admins are powerless. Good luck to all those who continue....

I shot at one and hit it at least 5 times in the engine and tail rotor area, it didn't go down (AS50 with M107 ammo). I would have hit it more but it was shooting at me and had to evade ;) They didn't stay long though so I think I damaged them pretty good. Anyways I think they should stay. Nice side-content/goal but doesn't really change anything IMO.

Do you have any guns/ammo? Try shooting, the zeds should come and warp through to make quick work of you. Or try going prone inside that wall, it may break your bones and give you a cut. Other than that, try vaulting (V key) around and see if you can work your way out.

In before the "I've never seen a hacker, I don't know what you are talking about".

I hear you... Sad thing is that the dev has given absolutely nothing to us in terms of feeling our pain or acknowledging the issue. Only placing blame on Arma2 engine and "there is nothing we can do". Which is BS. There is plenty they can do, starting with maybe a post here to acknowledge our concerns and give us some plans on what that are trying. Then perhaps ID the problems and ban the perps from the hive? It's almost as if the devs want the hacking. I've seen nothing that would indicate otherwise.

Pretty sure this is normal use of the crossbow. I have it all the time on my server as well.

1 - Log detections to "scripts.log" 2 - Log detections to server console 4 - Kick for detections ("Script Restriction #X") You can combine types by adding. I.e. 1+2 = 3 = Log to file and console. 1+4 = 5 = Log to file + kick.

If you haven't witnessed a hacker, please don't assume that there are none or that there isn't a problem. Before I rented a server I didn't think there was a problem either (I only was victim of hacking a couple of times). Now, though, I have reports of hacking about average of 4-5 per day on our server alone. Video proof? There is tons of it out there. Do a youtube search! I'd be interested in what kind of servers those without hacking experience are on... Low population? Avoiding players/PVP?

How to deal with it? Shut down the server immediately (quick 1 minute warning if possible, or no warning if everyone is dying) Make sure you are in contact with a few who are on the server often so you can get the reports in timely. Try to check the logs for anything obvious (but usually is not). But a server shut-down temporarily usually clears things up, as they move on to another server. So basically there is no way to prevent hacking, but you can minimize it and prevent it from continuing for any length of time. Takes a decent investment of time. I contemplate giving up on this crap daily.

This increased artifacting from 1.7.2.4 has been reported to be fixed by many users by "simply doing this" but the fact is there are different fixes for different users, and for some none of the "fixes" work. This includes: - Flush command - Changing video memory away and back to default - Turning on anti-aliasing - Turning HDR to low - Disabling VSync - Installing latest Arma2 Patch - Running Arma2 stand-alone (without OA) then running OA again For me and about 1/2 the group I play with, none of these fixes are working. Some changes make things worse. Some seem to help a little temporarily. The artifacting for me is based on certain military prop items including fences, dead bodies, items in the hangars, mesh in tents, etc. Balota, Stary, Berezino, NWAF are hotspots for this.

If you are anywhere near military tents/hangars there is massive graphic artifacting going on for many users with 1.7.2.4. It pretty much blacks the entire screen. You have to leave the field of view of such areas before you can see.

There should be a disableVoN flag in the server.cfg file that needs to be set to 0. Also, when my server was new, direct comms didn't work reliably. It took about 3-4 days IIRC. Before then, sometimes it worked, sometimes not (voice or text).

I disagree with the last part, Arma2 has lots of hacking issues without DayZ mod.

This is an Arma2 issue. The time lags behind significantly after a while.

As many will tell you here, they have never ever seen a hacker, so they must not exist or must not be a problem! Really, welcome to the club. We have a 3 week old server that has witnessed at least a few hacks every day, getting much worse the past week. Nothing you can do it about it really to ban these people (not shown in logs) but if you enable crosshairs/nametags you can ID those in hacked helis and if you shut down the server for a few minutes they (hackers) will usually just go away (to another server).

I am an HFB customer and plan to pull the plug on my server. Not because I feel HFB is any worse than other slotted hosts (they have been acceptable IMO), but because slotted servers have been crippled by DayZ policy preventing necessary admin capability. That and the rampant hacking that is only getting worse regardless of slotted/dedi. But really HFB hasn't been that bad at all IMO, they are slow, but they are indeed listening to customers and trying to improve to the best of their abilities.

The scripts log only contains items you have chosen to log, but then only if battleye is not bypassed. Most hacks are bypassing, so there is no log. Also there was a battleye update most servers probably have installed now, which basically removed your existing scripts.txt detector, so nothing is logged until you re-create the file with the new format. But again, this doesn't do anything for BE bypassing.

It's getting really bad.... It was bad already, but now.... It's really killing the mod. I honestly don't think DayZ team cares, otherwise they would do something about it. If they can't beat the hacks in a public server system then they need to allow private servers. But they won't do that, so they are indirectly supporting hacking. I give it about 15 days to complete meltdown unless something drastic is done. A cooperative bans list program sounds nice and I fully support that, but I really doubt DayZ will allow it. Most likely this will be terms for blacklist by banning anyone without direct proof on your server.

But everyone says there are no hackers, because they have never seen one! So it must not be a problem! /sarcasm

1 or 2 servers and I want dedi so I can prune my logs, control my scripts.txt detection, update my own patches, add BEC and set the time zone myself. I have a slotted server with HFB I will be shutting down at end of cycle due to lack of admin capability.

Agree that the game is all about PVP now. It frustrated me in the beginning but I have now joined a group and now we're all looking for it.. the best being 6v6 or 4v4v4 type battles between organized groups. With the zombie backdrop, limit supplies/high loot areas, and unpredictability, it's much more fun than traditional FPS PVP with canned flag capture or DM matches. Without a group though, the game is either just frustrating or just boring. Give the PVP aspect a try with a group, you might like it.

Thanks, nice list... However, I notice that for any "3GHZ+" processor, or one with specs comparable, we are still looking at $100+ a month. How well will an Athlon X2 4200, for example, run single or multiple Arma2 servers??? I'd love to switch to dedi at similar cost but concerned about CPU. Thanks for any insight.

Where? Cheapest dedicated I've found with decent specs is about $130 a month... Slotted are going from $35-65.

Agree L85 in the right hands is deadly, especially with an organized group using thermal sweeps effectively. We've lost them every time we've had one though. Backpack or primary, it never comes back the next session. Not sure if due to reconnecting or due to server restart. So if you get one, use it before you lose it!

When you rcon and type MaxPing what does the value show? I had an issue where HFB control panel only lets you edit a predefined BEserver.cfg, but the server wasn't using that.. instead it was beserver_active_xxxx.cfg or something (which we no longer have access to apparently, so hopefully we don't have to change it!). Might want to check for that kind of alternate file and see if that does it.