Inkompetent

All bullets have magazine-spefic muzzle velocity. This is a bit flawed since for example the AKS-74U and AK-74 use the same magazine, so even though the AKS-74U should have a lower muzzle velocity it doesn't. Additionally all bullets have a variable that decides how fast they decelerate from wind resistance. And lastly all bullets are affected by proper gravity. If all variables are set up correctly you'll see trajectories for each kind of round very, very close to what it should be in real life.

You can't use a sleep command inside a waitUntil

{ bomb = "Bo_GBU12_LGB" createVehicle getMarkerPos _x } forEach ["bomb1","bomb2","bomb3"]; would be the shortened way to write it :) I.e. run the code within the curly brackets for each element in the list, where _x is the currently looked at element.

The server's difficulty settings are forced onto all clients, so it doesn't matter at all what difficulty settings the clients have since theirs' won't be used. I haven't looked into how the difficulty settings look in ArmA2 though, but Binkowki's post is informative enough about alternatives :) Running missions in Veteran mode will disable auto-spotting at least, but I think there'll still be some markers on the maps.

Yep. That looks correct.

swe. Coop *is* a form of multiplayer. Just because you prefer PvP it doesn't mean coop isn't multiplayer. And I definitely agree with the OP. I haven't seen it much, but seeing it at all is pretty baffling.

Just to be a nitpick linnx, I'm yet to see a single server running any kind of modification at all. The most custom I've seen are user-made missions like Evolution, Domination and some AAS missions ;)

Mac. Just play at a server using Veteran or Expert difficulty settings, or with difficulty settings modified to disable the spotting/auto-spotting... Why do everyone persintently think that parts of the game suck, when what they think suck are OPTIONS that can be ON or OFF?

Yep. Just got to lie prone under a tree in the shadow, one shot at 300m with an M16A2, and there's one running (and want-do-bunny-jump-but-can't-because-they-can't-jump-in-ArmA2) player less, and his buddies won't even know where the shot came from.

'Bad version' means exactly that: Bad version. Update your game to 1.02 and try again ;)

Well, added on the topic of respawning: How about missions with only one side that gets to respawn? Generally it is by strategists adviced to have three times as many attackers as there are defenders to have a good chance of a decisive victory. However most missions I see are designed for equal numbers on both sides. What about a mission then that are designed for equal numbers, but where the defenders aren't allowed to respawn, but the attackers are (possibly with either limitations on the respawning, or with a fairly strict mission timer)? Could be wave respawning or whatever for the attackers to avoid a small, constant stream of people and instead make a dozen or two come at once. Wouldn't this be one thing to make respawns viable, rather than designing a mission for 20v40 (which unless the server is full will never ever be balanced since on public servers people never balance out teams if they are assymetrical)?

Auto-kicking/banning on connect can be set up in the server.cfg to give specific messages, so that isn't really a problem. I can agree though that there need to be a 'kick/ban player X with reason Y' kind of command that can be used by admins mid-session.

Heck, he asks about how to do it. Not what people's thoughts about doing so are. Give the OP a break. Unfortunately I can't help though. Looked quickly at the dedicated server and server.cfg wiki pages, but couldn't see anything about micromanaging difficulty settings. Good luck though :)

Camping in AAS highly viable. Done it multiple times myself. People will try to flank and get past the bulk of your side's forces to get easier kills, and sitting at some spot and wait, letting them pass, and shoot them in the back is incredibly fun. Of course not everyone can camp around, but it can be very valuable to have a few people doing so, since it can interrupt the enemy's plans. He might have to create search parties just to eliminate the campers, rather than spending enough energy on taking zones. Campers are stationary and can either be circled around, avoided completely (go on the side far, far away from them to even make their ability to spot become useless), or suppressed. It is always easier to kill an enemy that you know where he is, rather than one you don't. A camper simply can't be as efficient in ArmA as in other games with phone booth-sized maps. There are too many ways to kill them or avoid them, and it is hard to get away. They can't just run around a corner. They either have to crawl several hundred meters into the woods to not get shot (which is terribly slow) or run across more or less open terrain and just hope to not get hit, when they relocate (which they'll often have to do if they don't want to get fragged after a few shots)

It doesn't. Unless specified the game will label it as 'Unknown'. Look at this link to see how you can make a correct label in the Description.ext file.

As long as it isn't spawncamping camping is very viable as long as it fits into the mission's/superior's plan.

Ohhhh! That looks pretty! Dirty lenses to my computer as soon as I get home! :D

Heh. Seems like I didn't read your last post before mine properly. To check if a specific side isn't in a trigger area you simply set the trigger to SIDE - Not Present,where 'side' is BLUFOR, OPFOR, Civilan or Independent. As soon as no more of the selected side is in that trigger area the trigger will become true (activate) As for the countSide command you can use it in any field, depending on what you want it do. You could for example use it in the Condition field in the shape of ( EAST countSide thisList ) < (( WEST countSide thisList) / 2 ); to make the trigger activate when there is less than half as many OPFOR as there are BLUFOR. Or you can use it in the On Activation (or Deactivation field) to count the numbers of one side when the trigger activates or deactivates. For example eastCount = EAST countSide thisList;. That way you can let something else (maybe a script, or other triggers) use the variable eastCount in some way.

You can use the countSide command: EAST countSide thisList; will only count how many of the units in the trigger area belong to the East (OPFOR) faction

You can read more about it here here. Any time you wonder about a command I suggest you check the wiki first, then ask if the wiki doesn't answer the question :) setFriend can only be used for a Side and not a single unit, and it also seems like especially the civilian side can cause issues since all Empty-side objects are classed as civilians.

Fact is that there IS problem with the VOIP. Not all bugs with the new sound engine used in ArmA2 are ironed out yet, and VOIP can cause problems like crashing clients and stuff. Other than that, nice report!

Yep. It's a boolean, so it does :)

That sounds like it should work.

Servers without password and without an admin tend to attract the worst kind of people you can find on the internetz. Try out ATOW, GOL, TacticalGamer, or some other more well-kept server and you'll hopefully have a much more pleasant experience.

Don't quote me on this, but I do think that the supersonic crack is speed-depending, so that it won't occur if a bullet drops below supersonic. Weapons that do fire subsonic ammunition never cause sonic cracks. They might cause a wizz, but not a crack.