Command
Example
Description
#login QWERTYUI
-
#login adminPW
Log in as the admin
#logout
Admin log out
#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#)
<May not be available in DayZSA>
-
#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 debugging.
#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 commands
#debug (command)
-
#debug von
-
#debug console
The available commands are:
-
Console
-
send to submitter what's on the server console , works as DebugAnswer for all writes into the console
-
von
Admin commands since Armed Assault:
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
