Rokochan

you just dont know how to use flares efficiently, flares are not a light illuminating tool, it can be use as a weapon and distraction. also the flare rounds on the m16a2 m203 are best to spot people in ghilles who are hiding in the trees.

the majority of the servers are daytime based mainly cause a. they cant see, b. 85% of the tree wookies cant use their favorite sniper rifles since they dont work with nvg. especially on a vet server or a nametag off server

implement a logout timer. and disable logout during combat, if user uses alt-f4 to exit the game, character gets erased and they have to restart their character edit add: or add a confirmation with a timer when alt-f4 / program closing is activated

the main problem with shotguns in the arma2 engine is although the shot is short range it's single target unlike it's real life counterpart in which the blast is scattered hitting multiple targets.

nope but you can however see this in gametracker and just search for your name

Commands The following commands are available to you once you have connected to a server: Admin Command Example Description #login password #login adminPW Log in as the admin #logout Admin log out #mission filename #mission myDM.intro Select mission with known name #missions Select mission #restart Restart mission #reassign Start over and reassign roles #shutdown Shuts down the server #init Reload server config file loaded by –config option #exec ban (name, ID or Player#) #exec ban nickName #exec ban 47114712 #exec ban 3 Allows you to ban a player. Their ID will be added to the ban.txt #kick (name, ID or Player#) #kick nickName #kick 47114712 #kick 3 Allows you to kick a player #monitor (interval in sec) #monitor 1 Shows performance information of the server. Interval 0 means to stop monitoring #debug off #debug off Disables debbuging. #debug (interval in sec) #debug 30 Default interval is 10 seconds. #debug (command) (param) #debug checkFile expansion\Dta\ui.pbo #debug userSent <username> #debug userInfo <username> #debug userQueue <username> #debug JIPQueue <username> #debug totalSent 10 The available commands are: checkFile userSent userInfo userQueue totalSent JIPQueue Each command command can be disabled by off instead parameter e.g. '#debug userSent off' Each command differs bit some output to screen, some to log file etc. You need some debugger capable of catching OutputDebugString running on the client machine (one very small and easy to use is available at SysInternals website. You launch this debugger, you launch ARMA client, connect to the server, issue any of commands #debug (command) #debug von #debug console The available commands are: Console send to submitter what's on server console , works as DebugAnswer for all writes into the console [*]von outputs into logFile defined in server.cfg as e.g. logFile = "server_console.log"; Each of those commands should show a confirmation in the chat channels. New admin commands since Armed Assault: Command Description #exec server side command Execute administration scripting command #lock Locks the server, prevents new clients from joining #unlock Unlocks the server, allows new clients to join http://community.bistudio.com/wiki/Multiplayer_Server_Commands

come back after you can type out legible words please,

well there are a couple of ways to get to work this. on dayz commander you could always downgrade to the arma2 patch to match the server you are trying to get into. Also when downgrading the dayz build patch from 2.5 to 2.4 there will always be a very long loading screen mainly cause you will be spawning on the coast, it's a known bug when upgrading or downgrading from a dayz build.

private servers hm.. dont know any. most likely you're going to be playing on one server exclusively to maximize the use of the gear on a particular server.

hackers will most likely invade high ranked servers on the gametracker server list. or high pop servers.

wire fencing is the best for torturing noobs. grab 3 ~4 wire fencing then go to the hospital of a major city, then inside of the glass set up a row of installed fencing so that any players who dont have a tool box cant get in regardless of breaking the glass or not

if you are afraid of the " owner's past" still on the computer, if you have gotten the windows cd you can always reboot the computer from scratch. also if you already have arma2 installed on there make sure there's no scripts folder on it just to be safe

weapons dont particularly disappear, only after a server restart.

have you tried joining other servers?

spawned in by a hacker most likely. i havent seen this car in the game,