Как использовать команды администратора в ARMA 3
Вы можете получить доступ к командной строке, нажав клавишу чата (по умолчанию: /).
В окне ввода чата вы можете ввести любую из следующих команд и подтвердить их клавишей ввода.
Вы должны добавить символ # перед командой.
Команды можно использовать в сценариях SQF с помощью serverCommand.
Устранение неполадок: dсе команды подтверждаются сообщением в консоли. Если вы вводите команду в правильном формате и не видите подтверждения команды, значит, произошла ошибка. Проверьте журнал вашего сервера для получения дополнительной информации (например, один или несколько файлов ваших миссий повреждены или имеют ошибку, которая препятствует загрузке лобби миссий или может помешать выполнению других команд, таких как #restart или #reassign).
Команды
После подключения к серверу вам доступны следующие команды:
Админ
| Command | Example | Description | ||||||||||||||||||||
| #login #login password | #login #login adminPW | Log in as the admin. Without password only possible if you are listed as an admin[] in server.cfg#Server_Options | ||||||||||||||||||||
| #logout | Admin log out. | |||||||||||||||||||||
| #mission filename #mission filename difficulty | #mission myDM.intro #mission myDM.intro Veteran | Select mission with known name and set the difficulty. Difficulty parameter is optional and if not set, current difficulty is kept. | ||||||||||||||||||||
| #missions | Select mission. | |||||||||||||||||||||
| #restart | Restart mission. | |||||||||||||||||||||
| #reassign | Start over and reassign roles. | |||||||||||||||||||||
| #shutdown | Shuts down the server immediately | |||||||||||||||||||||
| #restartserver | Shuts down and restarts the server immediately (since Arma 3 v1.66) | |||||||||||||||||||||
| #shutdownserveraftermission | Shuts down the server after mission ends (since Arma 3 1.72.142200) | |||||||||||||||||||||
| #restartserveraftermission | Shuts down and restarts the server after mission ends (since Arma 3 1.72.142200) | |||||||||||||||||||||
| #init | Reload server config file loaded by -config option. | |||||||||||||||||||||
| #exec ban name #exec ban ID #exec ban 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 #kick ID #kick 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.
| ||||||||||||||||||||
| #monitords (interval in sec) | #monitords 1 | Shows performance information in the dedicated server console. Interval 0 means to stop monitoring. (since Arma 3 v1.64) | ||||||||||||||||||||
| #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 can be disabled by the use of the off parameter e.g. #debug userSent off Each command differs a 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, then launch ARMA client, connect to the server, and issue any of the 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. |
Игрок
| Command | Example | Description |
| #vote missions | Users can vote for the mission selection. | |
| #vote mission (name) | #vote mission myD.intro | Users can vote on a particular mission to loaded. |
| #vote admin (name/ID/PLR#) | #vote admin nickName #vote admin 47114712 #vote admin 3 | Users can vote an admin to control the server. |
| #vote kick (name, ID or Player#) | #vote kick nickName #vote kick 47114712 #vote kick 3 | Users can vote to kick off an individual. |
| #vote restart | Vote to restart the mission. | |
| #vote reassign | Vote to reassign. | |
| #userlist | Displays the list of users on the server (use PgUp to scroll up). |
Battleye
| Command | Description |
| #beclient players | Displays the list of GUID’s of all players on the server. |
| #beclient guid | Show your own GUID. |