Patchy

Patchy monitors games on Steam, Battle.net, and PlayStation and notifies about updates via Discord.

Patchy checks each configured title's current version, remembers it in a SQLite database, and posts a Discord message when the version changes.

Setup

A Discord Webhook is required to receive update notifications.

Patchy reads each setting from exactly one place.

config.toml holds what to watch and where to report it. Copy config.example.toml to config.toml and edit it.

interval sets the default minutes between checks of each instance. 0 (the default) checks once. Patchy exits once no instance is due to be checked again.

Each [[platforms.<key>]] table is one instance of a platform with its own titles and webhook. Repeat a table to watch another set of titles on the same platform, for example two Steam instances posting to different channels.

Instance option	Description
name	Identifies the instance in logs and the database. Defaults to the platform key; required and unique when a platform has more than one instance.
enabled	Whether this instance is checked. Default true.
webhook_url	Discord Webhook URL for this instance's updates. Omit to only log them.
titles	Title IDs to watch.
interval	Minutes between checks of this instance; 0 checks it once. Defaults to the top-level interval.
branch	Steam only. Depot branch to track. Default public.
region	Battle.net only. Region to track. Default Americas.

Platform keys are steam (Steam app IDs), battlenet (BlizzTrack product codes), prospero (PlayStation 5 title IDs), and orbis (PlayStation 4 title IDs).

interval = 30

[[platforms.steam]]
name = "favorites"
webhook_url = "https://discord.com/api/webhooks/XXXXXXXX/XXXXXXXX"
titles = ["730", "440"]

[[platforms.steam]]
name = "betas"
webhook_url = "https://discord.com/api/webhooks/YYYYYYYY/YYYYYYYY"
titles = ["730"]
interval = 5
branch = "beta"

Each instance remembers versions separately, so a title watched by two instances is reported to both webhooks.

Steam updates also list the depots that were added, removed, or changed since the previous version Patchy saw, with how much each changed depot grew or shrank.

Environment variables hold runtime settings. Set them directly, or copy .env.example to .env.

Variable	Description
PATCHY_CONFIG	Path to config.toml. Default config.toml.
PATCHY_DRY_RUN	Check titles without saving versions or sending notifications. Default false.
PATCHY_LOG_LEVEL	Console log level. Default INFO.
PATCHY_LOG_DISCORD_WEBHOOK_URL	Discord Webhook URL to forward log events to.
PATCHY_LOG_DISCORD_LEVEL	Minimum level forwarded to Discord. Default WARNING.
PATCHY_DATABASE_PATH	SQLite database location. Default patchy.db.
PATCHY_HTTP_TIMEOUT	Seconds to wait for upstream services. Default 30.
PATCHY_HTTP_RETRIES	Retries for transient upstream failures. Default 3.

Runtime settings placed in config.toml are reported as an error. Environment variables for config.toml settings, or for options that don't exist, are ignored.

The first time Patchy sees a title it records the current version without notifying. Later checks notify only when the version changes. A notification that fails to send is retried on the next check.

Docker (Recommended)

Images are published to the GitHub Container Registry for linux/amd64 and linux/arm64. Patchy reads config.toml from, and stores patchy.db in, the /data volume, and runs as the user and group set by PUID and PGID (default 1000).

Place your config.toml in ./data, modify the following compose.yaml example file, then run docker compose up -d.

services:
  patchy:
    container_name: patchy
    image: ghcr.io/ethanc/patchy:latest
    restart: unless-stopped
    environment:
      PUID: 1000
      PGID: 1000
      TZ: America/New_York
      PATCHY_LOG_LEVEL: INFO
    volumes:
      - ./data:/data

Set interval in config.toml, globally or per instance, to have Patchy check on its own. To use cron or another scheduler instead, leave every interval at 0 and run the container on your schedule without restart.

Standalone

Patchy requires Python 3.15 and uv.

1. Install dependencies: uv sync --no-dev
2. Copy config.example.toml to config.toml and fill it in. Optionally copy .env.example to .env to change runtime settings.
3. Start Patchy: uv run patchy

Run uv run patchy --help for every command and option.

Development

See AGENTS.md for the project layout, conventions, and how to add a platform.

uv sync
uv run ruff format && uv run ruff check && uv run ty check && uv run pytest

Credits

• Helba: BlizzTrack.com
• 0x199: PROSPEROPatches.com & ORBISPatches.com
• JonaKoudijs: SteamCMD.net