Skip to main content

Executing Proxy Commands

Q: How do I make UAR run proxy commands?

A: UltimateAutoRestart supports both Bungeecord (and forks) and Velocity. In order to execute commands via your proxy a separate addon plugin must be installed on your proxy. You can find the Bungeecord Passthrough plugin here, and the Velocity Passthrough plugin here.

Q: How do I execute proxy commands?

A: Add [proxy] in front of your command (example -> "[proxy] alert Server is restarting"), this will execute the command via your proxy when the server restarts. However, it is recommended to use timed commands because proxy commands might not have time to be sent (because the server stops). Find out about timed commands below.

Q: How do I execute timed proxy commands?

A: Add [proxy:x] (where x is the time in seconds) infront of your command (example -> "[proxy:5] alert Server is restarting"), this will execute the command via your proxy 5 seconds before the server restarts.

Q: How do I execute scheduled proxy commands?

A: There is a difference between timed and scheduled proxy commands. The difference being that scheduled commands are scheduled on the proxy itself instead of the bukkit server. This allows you to execute proxy commands x seconds after your bukkit server stops. Add [proxydelay:x] (where x is the time in seconds) in front of your command (example -> "[proxydelay:30] alert The server is back up!"), this will execute the command via your proxy 30 seconds after your bukkit server stopped (restarted).

Q: My proxy commands do not always run, why?

A: This is a messaging channel limitation and there's nothing I (as the developer of the plugin) can do something about. In order for proxy commands to execute there needs to be an online player on the server that UAR (not proxy version) is installed on. The scheduled proxy commands partially fix this issue.