Cavero Plugins
Docs / Client Watcher

// plugin guide

Cavero Client Watcher

One-view fleet monitoring. Every running client posts scheduled screenshots (and optional alerts on logout or death) to a Discord server you control.

Discord webhookLogout + death alerts · Shop page →
Jump to section

Overview

Cavero Client Watcher keeps tabs on multiple clients at once. It posts periodic screenshots to a Discord channel you control, and — if you enable them — immediate alerts when an account logs out or dies. Each client runs independently and posts to the same webhook.

Quick start

  1. Create a Discord webhook — see Setting up the Discord webhook.
  2. Paste the URL into the plugin config's Discord Webhook field.
  3. (Optional) Set the screenshot frequency — default is every 5 minutes.
  4. (Optional) Enable logout / death alerts — both default off.
  5. You're done — screenshots start posting on the configured cadence on every client running the plugin.

Setting up the Discord webhook

Webhooks are a Discord feature that lets any service post to a channel without logging in as a bot. You only need the URL — there's no token, no bot invite, no OAuth:

  1. Open the Discord server you want the posts to land in.
  2. Server settings → Integrations → Webhooks.
  3. Click New webhook, pick a name and the target channel.
  4. Click Copy Webhook URL.
  5. Paste it into the plugin's Discord Webhook config field.

Keep the URL private

Anyone with the webhook URL can post to that channel. Don't share it, don't commit it to a public repo, and rotate the webhook (delete + re-create) if you think it's leaked.

Screenshot cadence

Screenshot Frequency is in minutes (default 5). Each client captures and posts its own screenshot on that schedule, independently. Posts only happen when the client is actually logged in — logged-out clients sit quiet.

Alerts

Both alerts default off. When enabled they post a screenshot plus a text mention so you actually get notified:

  • Logout — fires when the game state transitions from logged-in to logged-out, however it happened (manual, timeout, kick).
  • Death — fires when your local player dies.

Multi-client behaviour

Every client you have the plugin installed on will post to the same webhook URL. Each post includes the player name and context, so a single Discord channel can host a whole fleet without confusion. Discord accepts concurrent requests fine — there's no need for per-client webhooks.

Configuration reference

  • Discord Webhook — URL you got from Discord
  • Screenshot Frequency — minutes between posts (default 5)
  • Logout alerts — post a screenshot + mention on logout
  • Death alerts — post a screenshot + mention on death

Tips & gotchas

  • Use a private channel — screenshots include the full client window, chat and all.
  • Don't drop the frequency to 1 minute on 10 clients — Discord rate-limits webhooks around 10 requests/sec per hook; low intervals × many clients can hit that.
  • Discord file-size cap is 25 MB — massive resolutions can fail silently; stick with default client sizes.

Support

Join the Discord Plugin overview All docs