Automations: the server reacts by itself

Automations are in your game server's Automations tab. Each has When (the event that sets it off), optionally Only if (a condition) and Then (the steps). For fixed times there are schedules.

When: the events

• a line appears in the console (it contains a text, or a regular expression matches; you can try it on a sample line)
• the server has started, has gone off or has crashed (a crash is detected after about one to two minutes)
• Minecraft only: a player joins or leaves, or the player count reaches a limit (optionally: for some minutes)
• another automation runs it

Then: the steps

• send a command; for player events {player} puts in the name
• start, restart or stop the server
• create a backup (when all slots are in use, it replaces the oldest unlocked one)
• send a notification: always to your notifications, optionally also by email, Discord, WhatsApp or push
• send a webhook (see below)
• run a schedule, wait (up to 600 seconds per step), or run, switch on or switch off another automation

As a condition under Only if there is: another automation is switched on or off, and on Minecraft: nobody is online, or at least one player is online.

Create an automation

1. 1

   Press Create automation, then start from a template or start blank.

2. 2

   Templates include notifying Discord on a crash and, on Minecraft, a welcome message for new players or: when the server is empty, stop it after 10 minutes.

3. 3

   Set how often it may be set off at most (60 seconds by default) and save.

Under Recent runs you see when it ran and whether it worked. Every run is also listed under Activity.

Webhooks

The send a webhook step sends a message to an https address of your choice each time the automation runs. If the address is a Discord webhook, a message arrives in the channel. Any other address gets a POST with JSON and a signature in the X-GoodFlare-Signature header (t=…,v1=…, HMAC-SHA256 over time and content), which your receiver uses to check that the message comes from us.

Send test shows at once whether the address answers. Deliveries lists every delivery with its response and duration; if one fails, the portal tries again. You see the signing key only once, when it is created; you can create a new one there too. How to check the signature is in the API documentation.

Limits

• 25 automations per server, 10 steps per automation.
• Together at most 10 runs per minute per server; chains of automations at most 5 deep and without loops.
• After 5 failures in a row an automation switches itself off.
• So far the portal recognises joins and player counts only on Minecraft.

People you share the server with need the Schedules right, and for each step the right they would need by hand (Console for commands, Power to start and stop, Create backups for backups).