Automation source	Cron job" : "Page loads (fallback)"; ?> When the cron job is not running, the game still works: players' page loads process the tick, exactly as before the cron was introduced.
Last cron tick	0) { echo date('d.m.Y H:i:s', $cronLastRun) . ' (' . $cronAge . 's ago)'; } else { echo "Never"; } ?>
Cron job command	Add this in cPanel → Cron Jobs. Writing to cron.log instead of /dev/null lets you see errors if it fails to start.

Invocation length (seconds) ?How long one cron.php invocation keeps working. Most shared hosts only allow a cron every 5 minutes, while Automation expects to run about every minute — so one invocation runs several ticks in a row. Use 300 for a "*/5" cron. Set 0 only if your host allows a cron every minute.	0 = a single tick per invocation. Maximum 3300 (55 minutes).
Tick interval (seconds) ?How often Automation runs inside one invocation. Automation's own guard expects roughly 60 seconds; going lower mostly adds load without processing anything new.	Recommended: 60. Allowed range 15–900.
HTTP trigger key ?Only needed when calling cron.php over HTTP (for example from an external cron service). The server's own cron job does not use it. Regenerating invalidates any URL you configured elsewhere.	Not set – one will be generated on save. •••••••• show Generate a new key on save