Note that the Scheduler has it's own schedule.json file containing the timetable (see below). When declaring a command in your config as restart event, the command string will be ignored. Please note that without any kind of watcher your server might not come back up. If there is only RCon the restart will send a '#restartserver' command. If the Watcher is enabled, the restart will be done by sending a SIGTERM/SIGKILL to the process. The Scheduler is able to either send a string over RCon (like: say -1 hello all) or send a restart command. On Windows the server is not being killed when gorcon-arma ends unexpected so take care of this when restarting it. This is a wanted feature as an automated restart of gorcon-arma would start a new server anyways which would then concur with the old one. When using the watcher as process manager, ending or killing gorcon-arma will also terminate your server process. When using the Watcher you always have to let the Tool start your ArmA server otherwise the process won't be detected. The Watcher is responsible for starting and watching your game process. The other parts yet integrated are the Watcher and Scheduler. Main Part is the RCon library which connects to a given server and sends commands/handles responses. In addition to that, it is planned to make this Project extensible with Plugins.Offering ease of use with exisiting Tools.Provide Server Performance and Host Information to Interfaces.Streaming in-game Chats and Events to Console.Sending timed Messages/Commands to Servers.The Go based Rcon solution for ArmA servers with server management features

Arma 3 rcon setup