Notifications

Notifications (ntfy)

AquariusProxy can push alerts straight to ntfy — no account, no token, just a topic name — for the events only the bot process itself can see:

• Visual range — a player entered / left visual range, or logged out while in range
• Connection state — connected to the destination server, disconnected, login failed
• Proxy events — currently just login failures; more may be added over time

This is independent of the Discord module (discord.*), which keeps working unchanged. Ntfy is additive, not a replacement — enable either, both, or neither.

If you manage this bot with Aquarius Bot Manager, its Notifications tab covers the manager's own alerts (scheduled jobs, watchdog restarts, the bot's OS process going offline/online) and can share the same ntfy topic as this bot's config below, so everything lands in one place.

Config

There's no command for this yet — edit config.json directly, or through ABM's per-instance Config tab (Notifications category) if you use it. Fields under notifications.ntfy:

"notifications": {
  "ntfy": {
    "enabled": false,
    "server": "https://ntfy.sh",
    "topic": "",
    "visualRange": { "enabled": true, "priority": 5, "tags": "warning,eyes" },
    "offline":     { "enabled": true, "priority": 4, "tags": "red_circle" },
    "online":      { "enabled": true, "priority": 2, "tags": "green_circle" },
    "proxyEvent":  { "enabled": true, "priority": 1, "tags": "" }
  }
}

• server — ntfy.sh, or your own self-hosted instance.
• topic — anyone who knows this string can subscribe, so treat it as the only "secret" here. Generate something random rather than a guessable word.
• Each event bucket has its own enabled/priority (ntfy 1=min – 5=urgent)/tags (comma-separated ntfy tags/emoji).

Restart isn't required to pick up a config edit — each event checks notifications.ntfy.enabled and its own bucket's enabled at send time.