v0.4.3

Full Changelog: v0.4.2...v0.4.3

v0.4.2 — reliable auto-update

Auto-update reliability fix. Background installs were staying pinned to old versions.

• Re-checks every 6 hours while running (previously only at launch — a daemon up for days/weeks never saw a new release).
• Self-relaunches to apply the update immediately, instead of logging "please restart" and continuing on the old binary.

If you've been running an older build, grab this one once (the old auto-update couldn't reach you) — from here on it stays current automatically.

Full Changelog: v0.4.0...v0.4.2

Full Changelog: v0.4.1...v0.4.2

v0.4.1 — combat-log retry fix + earlier chunking

Fixes

• Combat-log upload no longer gets stuck retrying. A log with no scorable boss fight (dummy / trash / abandoned pull) is now correctly marked done instead of retrying every 6 hours forever.
• Combat logs chunk earlier (8 MB). Large session logs upload reliably as per-encounter chunks instead of one big body — whole-file uploads got flaky through the tunnel well below the 100 MB cap.

Profile, session, and VoidRaidTools data uploads are unchanged. The single ~7 MB binary still has zero install dependencies.

Full Changelog: v0.4.0...v0.4.1

v0.4.0 — persistent retry + chunked upload

What's fixed

After today's Mythic Chimaerus prog, the uploader had two hard failures that would lose data for any contributor on a heavy raid night:

1. 429 retry-storm: on rate-limit the uploader retried every 30 seconds, burning the 200/day per-character cap within minutes.
2. Cloudflare 100 MB cap: a 390 MB raid log hit 413 Payload Too Large from Cloudflare's body cap.

What this release does

• Persistent per-file retry backoff in state.json. Each combat log gets its own next_eligible_unix, attempt_count, last_error_code. Backoff by HTTP code:
  • 429: 5m → 15m → 1h → 6h → 24h
  • 413: 24h flat
  • 5xx: 1m → 5m → 30m → 2h
  • other 4xx: 6h
  • transport error: 30s → 2m → 10m → 1h
  • state survives process restart so a failed upload doesn't restart the timer when you reboot
• Per-encounter chunked upload for files > 90 MB. Splits at ENCOUNTER_START / ENCOUNTER_END boundaries, each chunk is a self-contained mini combat log. Each chunk POSTs to the same /api/upload-log endpoint — no server-side changes. Works around Cloudflare's 100 MB cap permanently.
• Bump local skip cap 200 MB → 2 GB. Only protects against accidentally uploading the wrong file.

Binaries

Auto-update will pull the platform-specific binary on next restart.

Full Changelog: v0.3.1...v0.4.0

v0.3.1

Full Changelog: v0.2.0...v0.3.1

v0.2.0 — Initial public release

First public release of VoidScout Uploader.

What it does

Watches your WoW SavedVariables/VoidScout.lua file and uploads scored fights to api.voidscout.io.

Features

• Single binary, ~6 MB, no install dependencies
• Auto-detects WoW SavedVariables folder on Windows/Mac/Linux
• 5-second mtime polling (more reliable than fsnotify on Windows)
• HMAC-free public API endpoint (rate-limited + sanity-checked server-side)
• Self-updates from GitHub Releases on launch

Install

Download the binary for your OS below, run it. That's it.

Windows users: SmartScreen may warn on first launch (we're unsigned). Click 'More info' → 'Run anyway'.

Reporting issues

File issues at https://github.com/bughatti/voidscout-uploader/issues