Shea

You really shouldn't give two shits about what people think, they can bitch all they want and sick some Team Rocket member at you and it wont amount to much more than the dirt under your feet, so long as you aren't actually hacking. The powers to be (not whinny server admins and their groupies) can look at your account history and see if you're one of the script kiddies or not. If nothing turns up of that nature on your account then you're quite free to use whatever gun you can manage to find, regardless of completely arbitrary glitches that occur to your gear. Go to town with it! Literally lol

News Flash: it does exist (M4 Holo SD). I've found multiple of them on crashed helis over time

Yeah and what's 200 rounds divided by two inv slots? 100 rounds a slot.

Was hunting in Cherno today when I spotted a survivor running to the fire station, right down the middle of the road. I don't pity the people who run out in the open like that. I shot him in the leg with my SVD just as he got near the concrete wall; he tried crawling behind the wall for cover. Those few moments were all I needed to pull out my M4 holo and drop an M203 HE on top of his head. I saw his body bounce back out from behind the wall, seeming very dead!

Use Steam/manual for whenever you need to revert to an old DayZ version, or beta patch. Use Six launcher for playing on current servers. That's how I use them. Works nice! Edit: This method results in being able to server hop between any kind of new/old versions (of any kind so long as you have backups of them) in 2~3minutes. I pretty much keep Steam on 1.7.1.5 (personally my fav. build so far...most stable).

I have seen renewed support for the modding community in another game I play on steam, Killing Floor (Zombie survival fps). This game too started originally as a mod (of Unreal Tournament), just recently for a summer update Killing Floor(KF) added a mess of new guns to the game (now stock guns!) that were created by modders in the community. DayZ has a very similar story as KF.

*bump*

--Dingus: Just use the squad mechanic like I suggested (above) and have the creation of a base/bunker/hole-in-the-ground be create-able in set regions and place-able in the same way tents are (enough clear space/flat ground...whatever specifications you could think of for a base)

Everyone knows about the potential of such ideas to: -bog down servers with data (unused bases still taking up space on a sever, etc.) -be useless to the owners while they are offline -be impossible to defend 24/7 -how to limit the size of such a feature, considering its essentially a base for people -how to have safety features of some kind (any case where there may be ally-accessible-only features) anyways this list goes on and on. SOLUTION: Create a squad system. Have a squad leader and group members possibly. Such a feature allows for an ingame mechanic that has potential to remedy all of these problems, and many more. Examples: Q: limit the size of the base? A: Have the size of the base be dependent on squad size? Hell you could put a cap on base size even, its possible but at least there'd be some sort of mechanism to determine this. Q: Cluttered server due to tons of bases on the map...even unused ones? A: Have your base be tied to your squad info as a file, so that the base can be loaded into a server. Give it a cool-down timer to despawn, have it only be able to spawn in its original location (if un-occupied on the current server of course), hell you could even have a voting/roll-call system for determining when to have it accessible to spawn. The point here is that there's A BOATLOAD of applications for a squad mechanic, hell you could even have armbands or some on-screen icon to ID teammates. The potential is limitless really, and the solution is simple too. I pray someone--Rocket or one of his crew at least reads this. . . . . Pipedream or no? Bad idea or no?

Date/Time: 6/22/12 at 6:15PM-ish Pacific Time What happened: Been noticing all day that once a single shot was fired from a magazine, upon reconnecting at a later point, the entire mag would be deleted from my primary inventory. This issue then persisted to the point that unused (full) mags were beginning to delete out of my backpack once all the ones in my primary inv. were gone. I systematically had all my mags (only for my primary weapon's ammo) deleted. I noticed the mag-eating was occurring with my pistol as well, but only when rounds were missing from a clip. Full clips weren't eaten like my mags were. Where you were: All over the west side of the map, the events were dependent on when I had to DC. What you were doing: Shooting people mostly, was running around quite a lot--covering lots of ground.. then the occasional DC to take care of Irl matters. *Current installed version:1.7.1.5 *Server(s) you were on: LA3 *Your system specs: *Timeline of events before/after error: Sometimes before my mags would get eaten I would get the glitch or whatever it is that refills your mags, but after about two times of that they were systematically becoming eaten, one at a time per DC/Re-connect. I'm now without any ammo for my primary weapon.

I've been thinking about the whole player-built forts and there's a few BIG hurtles to get over first with such a feature. PROBLEM: First is server memory/+lag from a fort being built. If its absolutely huge it'll bog down servers, second it would be easier to find and ransack. Third, how the hell can such a thing be guarded 24-hours a day? SOLUTION: Have a squad mechanic, (a squad leader/creator and team-members) so that the forts will have some means of regulation by squad size. The bigger the squad, the bigger your fort is allowed to be. PROS OF SQUAD MECHANIC: The squad mechanic allows for the possibility of teamwork activities, such as raids and other various ops. Always potential for recognition of friendlies and enemies, ect (servers with no tags). The squad mechanic also could potentially be an in-game feature that carries data with it.... data like your fort. Say if you had a fort that belonged to a squad, it could then be loaded into a server in its original location based on an inter-squad voting system maybe. A voting system allows for use of the fort regardless of whether or not the squad leader is in-game or if its only 6 out of 10 squad members online. PLUS this keeps all those random forts out of servers while they're not in use (presumably they would only be in-game when their creators also are online), so that servers aren't overloaded with data for a big ass fort that nobody's awake to use/defend. Throw in a run-off timer for de-spawning the fort, so it's not instantaneous... like if the fort was being raided the owners couldn't just de-spawn it immediately. Anyways just some thoughts that I hope Rocket takes a look at, could be interesting.

EDIT: I want to clarify that this is intended to report a glitch in the game of some kind.

Excellent article! Love this: Hall: Actually, I want to make the players animals as well. I want to make the players using Create Agent, because at the moment, they’re a unit. They have a group and they do a bunch of other crazy stuff.

Arma 2 has no melee combat system built into it, the herky-jerky nature of the zombies comes from their pathing being all jacked up when they try to move in for a "melee" strike. The erratic movement won't likely be fixed until a solid melee system is integrated into the Arma code. Although there may be a remedy on the horizon considering that Team Rocket has decided to allow players to get in on the melee action too. Making melee combat more of a central method of combat can only assure it will get the deserved attention it needs. Time will tell!

Just so every tl;dr 'ing idiot out there has the chance to see:

I don't think you get it, the 1.7.2+ versions cause server crashes non-stop. There's been roll-backs due to it in fact.

Hey Rocket or whoever is in charge, could u guys please stop updating the old 1.7 servers to 1.7.1 until you have fixed the bugs with 1.71 first? Yesterday I saw hundreds of people an hour (literally) coming back to this one particular 1.7 server I call home, trying to escape the bugs on 1.7.1. Today I Woke up and now that server was assimilated....*sadface* I don't want the new stuff until its patched. Seems like many others are in agreement. So, as the community, I think we ought to be able to have some say in this! How about you? What do you think? EDIT: Please post with constructive comments, any complaining about wanting the thread deleted b/c you're tired of X,Y,Z is not considered constructive. In fact its wasting other's time trying to get to relevant discussion. Thx

There is no rolling back, just pausing the roll-foreward until the obvious problems are patched.

Please delete your post or actually read the thread. You're wasting more space than this thread by not contributing constructively.

my thoughts... man up and do your part to test this mod. as it is in alpha' date=' the primary drive for rocket isn't to provide you with a complete and carefree experience. You and everyone else is a lab rat. Play the mod, welcome the idea of being part of the data collection process. [/quote'] You think I don't know this is an alpha? What I'm suggesting has no impediment on resolving the issues with the new 1.7.1, the bugs are well known, the problem lies in that THERE AINT JACK SHIT TO BE DONE ABT IT if you're playing on those servers. So as a resolution, in the mean time, stop updating the more stable 1.7 servers. They're running better than the current 1.71, but only until Team Rocket comes out with a hotfix. Which we're still waiting on.

Actually no, the server admin doesn't have control over that (with this particualr server at least). I talk to the guy often and he hasn't been on in days, this update happened regardless of him being online.