Ragotag

You are also 100% wrong since me and my crew did get one... til our pilot crashed it. :P Was fun doing it, only it sucked that hackers made it take a whole lot longer to achieve by Thunderdoming us once followed by the always entertaining teleport-murder... that one just never gets old.

Hi-sterical, ain't it? :o

I did not suggest that a wipe occur for every Arma2 beta, just each DayZ Alpha. =)

On the contrary my friend, your experience does not necessarily represent the whole. Just look at the hack reports in this forum, it's probably only a very small fraction of what is actively occurring simply because many people (myself included) have been victims of these hacks so many times that we no longer have any desire to spend our time typing up and submitting reports on them. In the past two weeks of playing this game, I have been a victim of these hacks at least once or twice a day across over a dozen different servers. In the past three days, the frequency has gone up to almost once every few hours. My regular crew of players is becoming quickly frustrated over this, and many are already moving on in disgust -- they absolutely love this game and the concepts behind it, but the Dev's lack of a solution or proactive support of the server admins regarding hack prevention is absolutely ruining their experience. I truly hope something is done about it and soon because it would be sad to see this project fail and the company's product reputation tainted.

You and your crew may not only have my beans, but all of my cooked meat and Mountain Dew as well! Good job!

Just happened to me and several in my crew on US302 during the "loading..." message. None of us were previously in or near any known vehicles, although all of us had been in vehicles with our current characters at one time or another prior to the logon attempt on this server. We don't have this problem on other servers at the moment.

This occurred at approximately 7:37AM EDT (GMT -4). I was back on this server with my crew (following an earlier hacker incident) to continue our in-game efforts. Myself and two of my crew, Cpt. Starfish and RockstarG, were waiting in the PBX for another of our crew (Saitaer) to meet us for pickup. Suddenly, Cpt. Starfish disappeared, followed by saitaer; myself and RockstarG DC'ed as soon as we realized that a hacker attack was underway. Another member of our crew, CodenameAlex, located near Chernogorsk was also teleported. The three who were teleported from their positions (Cpt. Starfish, Saitaer, and CodenameAlex) were executed as soon as they arrived at their teleport location. Here is a screen shot of the players remaining once I DC'ed. Sadly, Cpt. Starfish was eight days into his character -- a great run ruined by yet another hacker.

Occurred at approx 5:15AM EDT (GMT -4). While providing cover for my comrade RockstarG, on the coast of Solnichniy, I was suddenly teleported to an area called "Thunderdome" containing at least one other player; I quickly aborted and DC'ed from the server, snapped screenshot, and then relogged into another server to check out the damage done. I found myself in the middle of the NW Airstrip, but otherwise all of my equipment was intact. RockstarG was also teleported to the "Thunderdome" and promptly aborted/DC'ed, then joined me on the other server and also found himself located in NW Airstrip; his main weapon and ammo had been removed by the hacker's script along with his GPS and NVG's, and he was given a horn. Our third comrade, CodenameAlex, was in Elektrozavodsk looting factories when he too was teleported to the "Thunderdome", his main weapon and ammo had been removed and he was given a horn, but he managed to grab a Bizon plus ammo from a nearby ammo crate as the ensuing Thunderdome firefight started. He too aborted and DC'ed, joining both myself and RockstarG on the other server, also finding himself located in the middle of NW Airstrip. Here is the screen shot of the players remaining on the server after I DC'ed; RockstarG and CodenameAlex are in my crew, so I *know* they are not the hacker. However, we do suspect that the hacker was still logged on since I left quick enough to not lose any weapons or gear, and took this snap before RockstarG was able to leave - and RockstarG did manage to get out before the hacker had executed the script to issue him a Bizon.

Not to beat a dead horse here, but apparently it ain't quite dead yet. ;) So did I, and he most certainly did not clear GhostHawx1 from the unfounded accusation of "Combat Logging"; an accusation made by your mates and the sub-admin who issued the ban. My entire quote was: The banning issue has been dealt with to everyone's satisfaction; nobody is arguing that. What SolarFlare wrote was: Nothing in that statement actually apologizes or exonerates GhostHawx1 from the accusation of "Combat Logging"; instead it actually supports the erroneous accusation that GhostHawx1 was "Combat Logging" -- something he most certainly was not doing. SolarFlare, I respect you and your admins, but I am in disagreement here... nowhere in your statement do you "clear his name" and exonerate GhostHawx1 of "Combat Logging". On the contrary, your wording implies that the accusation stands; you simply state that your server sub-admin was in error for issuing the ban. I'm truly disappointed that this is as sorted as US 88 admins feel it needs to be. Black mark indeed... I only offer my final comments on this because I feel that other players who are considering any server as a home ought to be aware of any potential issues on that server, be it the other players, hackers, or even the server admins. This is my final post in this thread out of deference to both SolarFlare and GhostHawx1 who I truly believe wish that this thread had never seen the light of day to begin with.

Yep, seeing vehicle locations getting reset after server restarts as well.

Had the same issue on US 88 running 1.7.2.4... a tent duped itself from relocation and all items saved in it were deleted. Other friends who had not relocated their tent had their items deleted as well. Furthermore, old tent sites -- sites that had been packed up and moved days ago -- are now respawning on server restarts with items duplicated from last save. Good thing this is only an Alpha release.

Shhhh... don't tell them where I am, they might find my survivor suit. ;)

I don't tarnish reputations, I let others tarnish their own. ;) Okay, you are *not* a Vigilante... "Witch Hunter" maybe? a.) GhostHawx1 was wrongly accused of combat logging, and I'm the one who shot you in the face. b.) You aparrently expected proof to substantiate a perma-ban to be discovered, and it wasn't. c.) You may "believe" the server logs contain proof of the accusation, but I *know* that the logs - if left untampered - indicate otherwise. d.) To me, it sounds as if the jury (you and your mates) already made up your minds that GhostHawx1 *was* a hacker. e.) Good thing you're not one of US 88's admins. f.) Are there any excuses for unsubstantiated accusations and a complete lack of due process? I never wrote that - you did... your interpretation, not mine. Really? In what way was the sub-admin involved? I am very curious on this point because if by "involved" you mean "part of that battle", it could certainly imply some form of admin abuse; not that I'm making that accusation -- I am not; but I could see how others might. I'll assume for the moment that this was *not* the case, but I'd still like to understand in what way the sub-admin had been involved. However, you did at least admit that it was your mates who made the accusation and reported GhostHawx1. Thank you for the correction. However, your words imply to me that you expected some sort of appeal and came trolling the DayZ forums looking for a chance to defend the sub-admin's actions in taking down and dealing with a supposed "Combat Logger" that your mates reported. Obviously some huge errors on the sub-admin's part since: 1) GhostHawx1 logged out at least 10 minutes following your death by my hands during the battle; 2) GhostHawx1 had an AS50 -- I had the L85, I dropped you on the run with a ~750m head shot with it. Vigilante... okay, maybe too strong a word to use and I apologize if my use of it caused your reputation any amount of "tarnishment" -- that was not my intent. However, don't be shocked if your adamant support of this sub-admin's actions discredits you in the minds of some of us. As SolarFlare wrote: As far as tarnished reputations go, I sincerely hope that a server admin of US 88 will submit a post on this thread clearing GhostHawx1 of the unsubstantiated accusation that he was "Combat Logging". An apology for invalid banning is only half of what should be done to rectify this disaster, and not necessarily the most important half -- but that's just my opinion.

Great idea and it totally fits in with DayZ. Devs could also add a Vaccine to military locations to heal the player from the zombie infection.

Austin, I really hope this ban is not a result of you and your crew misreporting and making assumptions regarding the events of this fight, and asking the server admin to issue this ban... that would be a real shame since Ghosthawx1 is a legit player and does not hack. Allow me to offer my point of view since *I* was the one who shot you from the west of your position with the L85. Please note: There is a glitch on that truck. When it takes damage, if both the driver and passenger get out and then back in, it auto-repairs itself. Same exact glitch that the bicycle has. This is not a hack, it is a bug; get the truck, run into something, and try it. You will be able to confirm this just as I have. He did check *for* the bodies but could not find them. Not sure why he could not find the bodies because myself and the other two of our folks had respawned on the coast and were working our way back north with fresh characters. I suspect that Ghosthawx was just being careful -- he was shot up pretty good and did not want to loiter in the area not knowing if your crew were still in the vicinity. However, I can confirm that someone found my body in the woods to the west but did not hide it because a few of my item were missing; thankfully I was able to recover most of my items. I understand the desire to ban cheaters, I too would like to see combat logging and ghosting eliminated. Sadly, I think you're taking a bit of a Vigilante position here, and falsely accusing a legit player. I urge you to reconsider your position on this. It's good to know that you speak for the admins, but I would really like to hear from them directly on this. I *know* that the server logs will clear him, but sadly Ghosthawx1 is being wrongly accused and banned without any due review. ..and yes... That was *my* first encounter with an L85 -- I did not know that I could zero the gun sights to range which is why I fired so many shots attempting to get the "Kentucky Windage" correct. Some of those shots were at the truck, not you and your crew as I was attempting to hit the tires. However, once Ghosthawx1 mentioned to me that I could adjust the gun sights, I zeroed them to 700m and dropped you in three shots -- you were making it difficult running around like that, and I admit that the final shot to the face was somewhat lucky on my part. Unfortunately, this is *exactly* what is happening here. Austin, obviously the server admins respect you and your crew as legit players since they issued a ban on another player solely on your report (I assume) without fully reviewing the logs. Sadly my friend, you are in error here. Here is the breakdown from my angle... We had five in our crew: three out in the Ute and an ATV scavenging helicopter crashes south of Pobeda dam, one (myself) scouting terrain for vehicle hiding spots, and one (Ghosthawx1) who had just returned back to our base with another of our crew (a sixth) from Berezino after seeing how badly it was glitched and calling off our planned raid over there. We have our own TS3 server, so Ghosthawx1 was still on TS with us even after he logged off US 88. Your crew ambushed our two crew driving the Ute up through the Pobeda damn area about two minutes after Ghosthawx1 logged off; he heard the call on TS for contact and the report of our two dying to your ambush. Cudos to you and your crew Austin, your ambush was well executed and our two crew were being stupid and deserved what they got driving around like that. However, Ghosthawx had logged out only 1km away from the ambush location and I was about 1.5km to your south west scouting terrain. Our guy on the ATV was within 4km, but he crashed the ATV trying to get up to the dam from your south -- he never made it to the subsequent fight. Ghosthawx1 logged back in and moved into a firing position to get eyes on you with rangefinders while I maneuvered around to your west. Ghosthawx1 got into a high position and began dropping rounds on your head, and your crew fought back and wounded him. While this was happening, I got into position to your west and began taking shots at your crew as well. Ghosthawx1 became critically wounded and had to retreat out for medical treatment - he also warned me of the likelihood that at least one of your shooters had an L85. I managed to drop you from a lucky shot, and one of your crew (the L85 guy?) nailed me with a head shot -- nice shooting. This was a legit encounter from my perspective that in no way warranted a player ban; your crew won the day -- good job, you have my respect. But please, refrain from the Vigilante approach and give the process of server admin review the chance to work. The ban of Ghosthawx1 is an invalid and completely unwarranted ban.

Hands down... NVG's.

It wasn't Ghosthawx, he is not an admin, and US1169 has been unstable as hell for the last 24-hours with frequent server resets, disappearing vehicles and tents, huge amounts of lag, and possible hackers executing murder scripts on random players. Heck, I logged off just before noon today -- alive and well, and logged back on around 12:30PM only to be instantly teleported over to debug forest and then back to my original location, followed by seeing my death notification in the bottom left corner of the screen while still in game and walking/running around with a broken leg and a wiped inventory -- go figure. Simple fact is, this server is a disaster and highly unstable and what you experienced is just a coincidence of such.

A few friends and I are now experiencing this problem as well. We all use a variety of different methods to connect to a DayZ server: via Steam shortcut using the in-game Multiplay, Six Launcher/Updater, DayZ Commander, and one even uses a shortcut to the beta patch installer (???) to launch the game then uses the in-game Multiplay. This is not happening on all servers we try, but just the most recent ones. However, the only people from my group not having any issues are those launching Arma2 from DayZ Commander. I tried this as well, and had to disable the "Launch Through Steam" option in settings (caused a DirectX error), but it has worked for me as well so far.

I can understand the desire to hook up with friends faster and easier, but I actually prefer a game that is in no way faster or easier -- this includes spawn selection. IMO, if realism is the goal, then it should be painful/costly to die to include getting a tough/inconvenient respawn location. Being stuck across the map from your friends also gives your friends something risky to do, that being coming to your rescue to help you re-arm and get back to your established camp. I really like this aspect as it promotes risk vs. reward and team-based play. Any feature that makes any aspect of DayZ gameplay less realistic and easier or more convenient detracts from the spirit of it in my opinion - but that's just my opinion.

Sadly, with the recent Ban lift all of those script bunnies have returned with a vengeance; so it will take a while for them to get hunted down again and re-banned. Just about all multiplayer games that support modding at the level that Arma II does has these problems with script hackers; the best solution is to adapt the Arma II engine with the DayZ mod design and make it a new stand alone game executable that does not support mods at all -- problem mostly solved. Unfortunately, Arma II or the DayZ mod itself is either currently not designed to support signed (encrypted) scripts or the server bandwidth and processing requirements to implement signed scripts is simply too high to make such a feasible solution. It also does not help that Battleye is only black-listing hacker scripts, not white-listing as well; because of this the script bunnies can easily get around Battleye making Battleye fairly ineffective at this point. This is not to say that Battleye itself is the problem, just that Battleye has too many limitations dealing with a game engine that fully supports client-side execution of mod scripts on game servers -- scripts that aren't signed by the mod developer and can do just about anything the script bunnies want them to do. This is a limitation on the Arma II/DayZ mod side more than anything else that is effectively tying Battleye's hands. Hopefully, a better strategy will be implemented for the beta release.

It's possible that you have an older version of DayZ Commander that still has some bugs and is not auto-updating itself properly -- especially if installed on any drive other than your C drive. This latter issue (auto-update) just got fixed, so I suggest doing the following to get your version up to 0.9.0.47 to see if it fixes your problem: 1.) Uninstall DayZ Commander via START --> Control Panel --> Programs and Features. (Your friends or favorites lists will remain intact.) 2.) Download from here --> (http://dayzcommander.blob.core.windows.net/releases/Dotjosh.DayZCommander.Installer.msi) and install into the same directory on the same drive as the previous install.