Then "Goldfinger" Maybe. Goldfinger had his gold-plated revolver.

That would be "The Man with the Golden Gun".

Haggard, glad to meet you and your bud in game. After we dropped you off up north, we headded back down in the heli to save it and wait for the server restart. Unfortunately, the heli didn't save and it was back at its original spawn point in it original condition (broken). Apparently, 10 isn't saving the helis properly and just resets them with each server restart.

That's what was happening when the helis were first brought back into the game, just check some threads here in the forums on that issue. 2 days ago, we fixed one on another server, flew it around, got it refueled, then flew back to the island for the server restart, expecting the heli to be back in its original state. We were pleasantly surprised to find it where we had landed it in the condition we saved it. I can't speak for 9 & 10, but that server appears to be working correctly now. If it's a hive update, one could assume that the helis save correctly across all servers now. I stopped by this morning to see if the heli I saw yesterday was back, and it was, so it looks like they respawn at server reset, and not after 7 days as before.

Actually, the Hueys have been respawning in their original state after every server restart on most servers, whether they had crashed or not. My team has had several helis crash, and be there at the next restart several times (not US 9 or 10 though). We did have a heli save through a server restart a couple of days ago on another server, so the hive may be getting better with them. Anyway, this particular heli was there, I killed the 2 players, and then it despawned. Seemed kind of fishy to me. I actually came back to the server about 30-40 minutes later to check if the heli respawned, and wound up killing one of the same guys again. He was a survivor this time, with a shotgun and most survivor gear...again

Just got off of US 9 a moment ago (~8:45pm MST). Was on Skalisty Island at the huey that needed repairs. I had teammates coming so I was about to get started on repairs when 2 bandits came on the scene, both carrying hatchets for primaries. After a little running around, and getting shot at by an M1911 pistol, I smoked 1 with an M4A1 SD, ran out of ammo, and got the other with an M9SD after chasing him down a hill. He didn't Alt-F4, so kudos to him for that. I got the name of both bandits and checked their bodies. They had plenty of gear, including satchels, NVGs, rangefinders, etc., but no primaries except for hatchets. At this time, I checked the player list and both players were not on the server. After taking some food/drinks, and re-checking around the heli for any of their friends, I buried the bodies and headed around the house back to the heli to continue repairs. I returned to the heli that had been there about a minute ago and it was no longer there; it had been despawned. I checked the player list again, and sure enough, both players were back on the server. Both myself and my teammates that were on the server immediately D/Ced, sensing a script-kiddie rage attack. I have the names of the players, but no screenshots or evidence that they're skiddies, so I won't list their names here. If the server admin wants them for the logs, I'll be glad to give them to you.

My Player name : Jeff (not very original, and probably the problem) Time of ban : Between 2130 and 2200 MST approximate I was playing on US 228 last night with teammates. We had a UAZ stolen from down south, and one of our guys followed it north (on a bicycle no less) before being killed. I was already alone to the far northwest running a LRRP for supplies and camp locations. I started heading east along the northern edge of the map to maybe find the UAZ and opfor. About the halfway mark, I ran into a guy who was on top of a hill. It looked like he had possibly spotted me earlier and was trying to reacquire me. I spotted him through thermals (L85, legally looted off a heli), put a few rounds in his general direction, then retreated back the way I came into a treeline. A short time later, there was a burst of automatic fire towards my original position, I assume in an attempt to flush me or pin me for a flanking maneuver by a teammate. Since they had not D/C'd after my initial volley (a banner event in this game), I stayed in the fight and spent about 20 or so minutes moving around to position myself on the other side of the hill for a flanking shot. I was under a tree doing a thermal scan with no further contact, when I was booted from the server with a "Battleye: Banned for hacking/scripting" message. Thinking it was an error like other Battleye messages, I tried to log back in and was promptly kicked again. I tried another server I frequent, and had no problems, so I know it's not a global ban mistake that's happened as of late. I thought that maybe I had engaged and admin and gotten a rage-ban, but my debug didn't show any extra kills, so the brief exchange of gunfire was bloodless. There were skidmarks on US 228 at the time. My other teammates were further down south getting ghosted on by another group at one of the factories. They killed one of them and found an MG36 with ammo in his inventory. One of my guys has screenshots with the name and inventory, but I don't have that info at the moment. Anyway, there was another Jeff on the server at the time : Jeff(2) to be exact. I'm thinking that maybe he had been hacking and the admins saw his name in the logs and got me by mistake. I and my team have been regulars on the server for a couple of weeks now without incident, and it's a great server. I'm not mad or anything. I would rather the admins be aggressive with the kiddies and get accidentally caught in the net. I would just like to get unbanned since I like ther server and my team has a camp and vehicles there.

Suggestions/Ideas about anti-Alt F4 measures : * Logging activity : Don't bother logging the first minute of a player's server time. That should save from having to wade through a bunch of data, and would make time for the player to judge the server performance and time, extract from a bad situation that was not their fault (other player in the vicinity, previously aggroed zeds, etc.), and bad spawn loads (missing gear, displaced locations, etc.) * If it's even possible, make some areas off-limits to spawning (e.g. NW Airfield, Stary tents/Sniper hill, etc.) If a player can't server hop the high traffic/loot areas, that should knock the server hopping down quite a bit by itself. If somebody D/Cs from these areas, have then respawn in a different location. For example : Disconnect inside the NW Airfield barracks and respawn in the middle of a field outside the airfield. The server hopper is exposed in the field and would have to make their way back to the airfield like real players. If all the key areas that server hopping looters/campers frequent can't be re-spawned into that may stop alot of griefing as well. Why wire up a firehouse stairwell if you can't get into it either? There are, of course, legitimate disconnects from these areas due to real-life emergencies or server crashes/resets, but those people would probably not complain too much if it means an end to the server hoppers. * I've always managed to use the normal disconnect when a script kiddie hits the server, but they've been rampant this past week (whole other can of worms), and I'm sure many have Alt F4'd to get away from the little shits. You may want to find a way to track and forgive those disconnects. You may even be able to use it to catch the kiddies in the act; For example, if the logs detect a a rash of disconnects from a server, have one of the dev team log in and see if a kiddie is running rampant.

Have it on FRAPS. Is killing server with silenced weapon and rapid grenade launcher.

REPORT: Installed latest patch (94997) Installed Battleye update with link on first page No issues encountered Joined one of our team's regular servers that had updated to patch and checked on tents : All was well; all items still in place. Joining was much faster than 94876 (skipped 94945 altogether), and never saw the "character creating" screen so prevalent in 94876. Moved to another server I had never been on to test further. I and another member of my team spent 2+ hours on this server and, though the server crashed twice in that time (nothing new there, doubt it was patch related), framerates were smoother for us than 94876. Zeds have been a definite improvement from 1.7.1.5; much more dangerous when doing something stupid, but also easier to lose around buildings/trees/bushes. Some sighting behavior was suspect, so the detection variables could probably use some tweaking, but never had the unresponsive zeds others have reported. Sound detection is sketchy though. Firing unsilenced weapons in what should be their detection zone went unnoticed by many of them, while others heard us just fine. One thing we couldn't check for due to lack of a heli was their spawn rate: in 94876, the rate was seriously messed up. (eg: killing all zeds at a heli site, and having a new batch spawn on top of us about 2-3 minutes later, most of them aggroed) Overall though, we agreed that the zeds' behaviour is moving in the right direction game-wise, and with a little more tweaking should hit 'gold' status soon. About 2 hours ago, we had several more teammates show up, and we sent them here for the update procedure. Some got on easily, while others were getting Battleeye errors no matter what they did. When trying other servers, some worked, and some did not. Just as I was leaving, the servere I had been on crashed and restarted. Some of the people who had been having problems earlier re-tried and were able to get on after the reset. We can only assume Battleye is doing some updating on its own and may be a reason others have been having problems in this thread. Hope this helps.

There's a teleporting hacker on US 10 at the moment. Killed 4 of us spread throughout the map within a couple of minutes with a silenced weapon.

POSSIBLE BUG : Encountered with latest patch (.4) last night. *Could not refill empty jerry cans at gas station east of Gorka. Had 3 jerry cans (empty) and 3 separate players tried to refuel w/o success. We had successfully refueled at that gas station 2 nights previous (so what, 5 hotfixes ago:) ).

Actually, if you have items like the medical boxes spawn on the beach, that could simulate the debris left by a sea evacuation. You would be amazed at what can actually float in saltwater. Just have the boxes randomly spawn with possible medical supplies and food. That might provide some relief for all the new spawns having difficulty obtaining said items.

Disclaimer: This is my first forum post, and I've no interest in flame wars. Just trying to contribute some constructive ideas for the devs in an organized manner. D/C Abuse : Apparently a big deal (haven't seen it myself), so assuming these ideas can be implemented within the constraints of the Arma 2 engine : 1) Make Alt-F4 an actual unalterable game keybind like the ESC key. Call it the 'Wussy' command key or something. When a player Alt-F4s, they drop their primary gun, backpack, and ghillie suit (if so equipped) and leave the game. In the game, this represents them panicking, dropping their gear and fleeing like a little girl [insert French soldier joke here]. If the cheater was trying to avoid death to another player, the opposing party is then free to take the gear the coward has now dropped. 2) When said coward logs back in, respawn them in some random location. This simulates them fleeing without care or thought where they are heading, finally stopping and not knowing where they ended up. If they have a compass and/or map, maybe they can figure it out....This should also solve the problem of players who use this exploit to server-hop into a better position for ambush or back-stabbing. They can't do it if they wind up on the other side of the map. 3) On re-spawn, skin 'em in a white T-shirt and boxer shorts with hearts, or something equally embarrassing; maybe granny panties for the females..... I'm sure the design team could come up with something. This simulates the fact they weren't wearing much under the ghillie, or the bushes and branches shredded their other clothes as they fled. Who needs to bother with cheating reports on the forums when public ridicule will do the job. I imagine the reports of "I saw so-and-so running around in their undies" both entertaining and confirmation of the cheating. The cheater's new priority would be to find new clothes, so I assume spawning more skins would need to be looked into if the devs wanted to show mercy. Possible problems to this idea that I can think of : * Don't know if the devs can even implement the alt-F4 bind in the Arma engine. * Valid Alt-F4 situations like phone calls, answering the door, etc. Maybe post a warning confirmation that the player needs to disconnect from the server through the normal means. * Game lock-ups. I know this happens often, especially in the development cycle, and innocent players shouldn't be punished for it. Can the game differentiate between crashes and Alt-F4s? * After reading many of the posts in these forums, I have a sneaky suspicion that many players would Alt-F4 just to run around in their underwear. That's a whole other can of worms...... The fix for players who D/C to avoid death through the normal ESC/Disconnect has been discussed ad nauseum (timers, etc), so I'll leave that alone. I hope I've brought a new idea to the table here. Feel free to point out any problems, or share other/better ideas, just keep the discussion organized and on track so that maybe it can be of help to the devs.