Added

• Fleet-save reminders can now be cancelled — but only at the last
  moment. A 🛡 reminder becomes clickable only in the final 2 minutes
  before each slot fires (before that it stays the passive auto badge). One
  click cancels just that nearest reminder; any later ones in the series stay.
  The exception: cancelling the last reminder before landing also drops
  every at/after-landing reminder — if you're in-game seeing it, the
  post-landing pings are pointless. The cancellation is local and
  self-expiring, and survives the fleet being re-detected on the next scan.

Fixed

• Your ntfy topic (and the account-status line) now show on load in
  Reminders settings, ready to copy — they used to stay blank until you
  edited the token. The async status rows fired their first probe while the
  row was still detached from the page, which then suppressed the real
  paint once it was attached.

Added

• Trader red glow clears from the Import/Export page. Opening
  Import/Export and seeing "no more offers today" (the daily container is
  already taken) now clears the red glow for the rest of the day — you no
  longer have to take the container through OG-E in the same session for
  the reminder to settle.
• Trader yellow glow follows the auction clock. On the Auctioneer page
  between auctions, OG-E reads the "next auction in …" countdown and keeps
  the yellow glow quiet until that auction actually opens — a precise
  replacement for the old fixed ~30-minute guess. While an auction is live,
  the glow is left alone so it still nudges you to bid.

Changed

• Reminders settings — "Check now" moved to the master row. The ntfy
  account-status re-check button now sits on the Reminders — master switch
  row (right-aligned, like Sync now in Multi-device sync); the status line
  below it is read-only.
• Reminders settings — per-group gating. Each reminder group's options
  now grey out when that group's own enable is off: the expedition-wave
  schedule follows Expedition-wave reminders — enable, the ad-hoc lead time
  follows Ad-hoc reminders — enable, and the fleet-save threshold / min
  flight time / schedule follow Fleet-save reminders — enable.

Added

• All your settings now sync across devices. Cloud sync used to carry
  only scan/colony data; it now also syncs your OG-E preferences through
  your private GitHub gist — including the ntfy token — so a second
  device picks up your configuration. Each setting merges independently
  (most-recently-changed wins per setting). Per-device exceptions that never
  sync: the two floating-button sizes and the GitHub token itself.
• ntfy.sh account status under the token field: today's usage vs your
  daily limit (✓ 12 / 250 messages used) with a Check now button, and
  explicit feedback for a wrong/rejected token (✗ Not a valid token,
  ✗ Token rejected by ntfy.sh) instead of silent failure.
• Your ntfy topic is now shown in the Reminders settings too (was
  Dashboard-only) — the topic to subscribe to in the ntfy app on your phone,
  right where you enter the token.

Changed

• Expedition-wave reminder schedule is now free-form (default
  0m, 10m, 30m, 60m), and all reminder time fields share one
  minutes-first format with an optional s/m/h suffix (a bare number
  is minutes). Lead time / min flight read 1m / 10m; fleet-save offsets
  read -10m, 0m, 10m.
• Section master switches: a section's top toggle now greys out the rest
  when off. Multi-device sync (Sync across devices) gates the token +
  status; Colonization gates its options. (Expeditions stays independent —
  badges and auto-redirect aren't tied to the floating button.)
• Multi-device sync layout + feedback: the Sync now button moved onto
  the master row (right-aligned); the status line gets its own full-width row
  with upload/download on one line, updates the instant a sync settles
  (a failed sync shows ⚠ HTTP 401: Bad credentials right away instead of
  after a delay), and the GitHub error is condensed to one line instead of a
  multi-line JSON dump.
• Reminders settings relabelled to a consistent Group — attribute
  scheme; value input fields widened.
• Max expeditions per planet is now a 1–20 slider instead of a text box.
• Colonization tidied: the target-positions field documents its range
  syntax (8,10-12,15), the "prefer neighbouring galaxies" toggle moved
  above it, and its label was shortened so it no longer wraps.

Note

• The wave schedule and fleet-save offsets reset to their defaults on
  this update (the old formats are incompatible with the new free-form one).
  Re-enter a custom series if you had one.
• Synced settings include your ntfy token and — if set — the abandon
  password, stored in your private GitHub gist. Private gists are not
  encrypted: anyone with your GitHub token could read them. The GitHub token
  itself is never synced.

Fixed

• Fleet-save reminders now appear on the Dashboard. The Reminders tab
  listed expedition waves and ad-hoc fleet reminders but silently omitted
  the auto-detected fleet-saves added in 1.11.0 — the preview had no
  fleet-save section at all, so a detected 🛡 save showed nowhere even
  though its pushes were queued.
• The Dashboard no longer cancels its own fleet-save pushes. The tab's
  orphan sweep (which deletes ntfy messages that belong to no live
  reminder) only recognised wave and ad-hoc messages as "ours", so it
  treated every queued fleet-save reminder as a stray and deleted it from
  ntfy — quietly undoing the feature whenever the Dashboard was open. It
  now claims all three reminder kinds.

Changed

• The extension page is now named dashboard on disk (dashboard.html /
  dashboard.js), retiring the legacy histogram filename — it has been
  the multi-tab "OG-E Dashboard" for several releases, not just a
  histogram. Purely an internal/asset rename; the visible name, tabs, and
  data are unchanged, and your saved active-tab preference carries over.

Fixed

• Long fleet-saves now actually fire. A fleet-save detected while its
  landing was still more than 3 days out got its 🛡 badge but never a
  push: ntfy.sh refuses delays beyond 3 days, so every reminder slot was
  filtered out at detection — and because the producer skips the sync
  whenever the event list looks unchanged, nothing rescheduled it once the
  fleet finally crossed into the 3-day window (the row's id and arrival
  never change as time passes). The scan signature now tracks when a
  fleet-save's earliest slot enters ntfy's range, so it re-syncs and queues
  the pushes exactly once at that moment. This also closes the matching gap
  for a fleet recalled mid-flight whose return leg is retimed past — or back
  inside — the 3-day cap.

Changed

• Reminder tooltips now spell out the exact clock times that were
  registered with ntfy, matching the expedition-wave tooltip:
• Fleet-save hover now reads Fleet-save reminders at: HH:MM, … (the
  slots actually queued, inside the 3-day cap) followed by Set
automatically — can't be cancelled. The mission, coordinates and ship
  count are dropped from the hover — you already see them in the row; they
  still ride along in the push itself. A save still beyond the cap shows
  the bare auto hint until its first slot comes into range.
• Ad-hoc hover now reads Reminder at HH:MM — click to cancel instead
  of the time-less Reminder armed.

Changed

• Trader reminder reworked. The Auctioneer and Import/Export reminders are
  now separate glows, and each one clears only when you actually do the
  thing — place a bid / take the container — rather than just by opening
  the Trader menu.
• Yellow (Auctioneer): glows during auction hours; placing a bid quiets
  it for about half an hour, then it reminds you about the next auction.
• Red (Import/Export): glows from 14:00 until you take the daily
  container, then resets at midnight. It deliberately stays dark before
  14:00 so it never tempts you to spend your one daily import before the
  afternoon tasks that may need it.
• The glows now also light the matching tiles on the Trader overview
  screen, and the Trader menu button steps aside for OGame's own
  hover/selected styling instead of overriding it.

Fixed

• ntfy pushes are now correctly authenticated as your account. The auth
  query parameter was malformed — it carried the bare token credential with
  no Bearer/Basic scheme, so ntfy.sh silently fell back to anonymous
  publishing. Notifications still arrived (the topic is public), but they
  were never attributed to your account (the ntfy dashboard showed 0 sent)
  and were rate-limited per-IP instead of per-account — defeating the whole
  reason the access token exists. The parameter now sends the documented
  base64("Bearer <token>") (url-safe, no padding) on every publish, poll,
  and cancel.

Fixed

• Round-trip missions (Transport, Espionage, Attack, …) no longer raise a
  duplicate fleet-save reminder on their outbound leg. OGame shows an
  outbound and a return leg the moment such a fleet is sent, but the fleet
  only lands back home on the return — so only the return leg is now
  treated as a fleet-save. One-way missions (Deployment, Colonisation), where
  the fleet stays at the destination, keep their single outbound leg.

Fixed

• Fleet-save detection no longer flags short planet⇄moon shuffles. A big
  fleet on a quick hop is logistics, not a save — so a leg now counts as a
  fleet-save only if its flight time is at least a configurable minimum
  (default 10 min), on top of the ship-count threshold.
• The flight-time check runs once, when the leg is first seen, and the
  classification is then locked. Logging in shortly before a long
  fleet-save lands can no longer reclassify it as "short" and cancel its
  already-scheduled reminders — the lock survives reloads and crosses
  devices (it lives in the gist state).

Added

• New Reminders setting: Fleet-save minimum flight time (seconds) —
  server-speed dependent, so configurable (default 600).

Added

• Automatic fleet-save (FS) detection. Any of your own fleets in the
  event list whose total ship count crosses a configurable threshold
  (default 100 000) is flagged with a 🛡 badge and gets a push-reminder
  series. It is auto-detected and auto-scheduled — non-cancellable by
  design (the badge carries no click action), and it takes precedence over
  the ad-hoc toggle on the same row (wave → fleet-save → ad-hoc).
• FS reminder times are a free-form, comma-separated list of offsets
  relative to arrival (default -600,0,600 → 10 min before landing,
  at landing, and 10 min after). Negative = before, 0 = at, positive =
  after. Post-landing pings auto-cancel once the fleet has landed and you
  are back in-game (being in-game re-runs detection; the landed row is gone,
  so its remaining future slots are swept from the ntfy queue).
• New Reminders settings: enable fleet-save detection, the ship
  threshold, and the offset list — beside the existing ad-hoc options.

Changed

• Reminder gist file is now schema v5 (adds the fleetSave /
  fleetSaveNotify blocks). v3/v4 files are read forward additively, so
  existing wave + ad-hoc schedules survive the upgrade.

Fixed

• Trader menu highlight: a morning click no longer silences the intense
  (red) afternoon escalation. The 14:00–24:00 red pulse is now cleared
  only by a click made inside that window — a click earlier in the day
  satisfies just the subtle morning reminder.

Changes in v1.8.2:
- Red notification icon for high-priority (player-armed) reminders

Changes in v1.8.1:
- Return-flight reminders now show the coords where the fleet lands
- Cleaner notifications: dropped tag emoji, 🔥 on top-priority reminders

Changes in v1.8.0:
Added
- Ad-hoc per-fleet reminders: tap a fleet's arrival time in the event list to
get a push reminder before it arrives (any mission, outbound or return);
tap again to cancel. Fires a configurable lead time before arrival; auto-
dropped if the fleet is recalled/leaves the list. ntfy's 3-day cap applies.
- Expedition waves controllable inline: one control on the wave cancels or
re-sends the whole reminder series without opening the dashboard.
- "Enable reminders" master switch gating the section behind it + the token.
- Dashboard: ad-hoc reminders view with per-reminder cancel.
Changed
- ntfy topic now derives from the ntfy access token, not the gist id
(push notifications decoupled from cloud-sync setup).
- Expedition-wave reminders ring at normal priority; ad-hoc at maximum.
- Reminders settings reorganised; "Open OG-E Dashboard" moved to the top;
friendlier labels. Combined sync = one ntfy poll per refresh.
Fixed
- Event-list badge clicks update immediately (no reload needed) and survive
the page reload OGame fires on the triggering click.

Changes in v1.7.0:
- Selectable expedition-reminder schedule (3 presets: 6×10 min, 4×5 min, 8× Fibonacci)
- Richer push notifications: icon, wave return time in the body, escalating tags

Changes in v1.6.2:
- A re-sent expedition wave can no longer resurrect its own reminders

Changes in v1.6.1:
- Fixed duplicate reminder stacking when sending a wave fleet-by-fleet on mobile
- Fixed previous wave's reminders not being cancelled after sending a new wave

Changes in v1.6.0:
- Added: Cancel a queued reminder wave from the Dashboard. Each wave
card in the Reminders tab now has an × button that deletes its
pending ntfy messages and tombstones the wave in the per-universe
gist file. The reconciler carries the flag forward so no
auto-reschedule loop occurs while the wave's rows are still
visible in the event list.

Changes in v1.5.3:
Fixed:
- Malformed ntfy token in one universe's Settings no longer breaks
reminders on that universe. ntfy access tokens have a strict shape
(tk_ + at least 20 alphanumeric characters); anything else
produces a 401 that Firefox surfaces as a CORS preflight failure.
The producer now validates the local Settings value against this
pattern and falls back to the chrome.storage mirror (a valid token
from any other universe) when it doesn't match. A console warning
fires when a malformed local token is overridden by the mirrored
one. The mirror itself only accepts valid tokens, so corrupt input
in one universe cannot poison the global fallback that other
universes rely on.

Changes in v1.4.0:
Fixed:
- Expedition reminders no longer stack duplicate ntfy schedules after a
page reload mid-wave. The previous identity model (Wave.id =
'w_' + nextWaveAt with a 300s drift tolerance) flipped a partially-
returned wave to "brand-new" when a long gap between observations
let nextWaveAt drift past the tolerance — typically a page reload
while the wave was landing. The brand-new branch scheduled six fresh
reminders on top of the original schedule already queued on ntfy,
producing bursts of pushes seconds apart while the wave was
finishing.
- Re-sending while the previous wave is still landing now cancels the
rest of its reminder cycle (any matched wave whose first reminder
has already fired or fires within 60s is swept once a brand-new
wave is detected).
Changed:
- Wave identity switched to the SET of return-time epoch seconds.
Two scans share a wave iff their returnAts sets overlap by at least
one timestamp. Wave.id is stamped once at brand-new detection and
carried through the wave's whole life.
- Reminder schedule is locked at wave birth — matched waves are never
re-scheduled.
- Reminder gist file schema bumped to v2 (oge-reminders.json). Older
v1 state is treated as absent on read; the orphan sweep on the next
sync cancels any v1-era ntfy messages still queued.
- Event menu highlight no longer paints the loud central #middle
banner. The left-menu pulse on active events remains unchanged.
Added:
- Trader (Handlarz) menu highlight — new opt-out toggle in
Settings → Display. Time-of-day-aware pulse on the Trader menu
entry, with per-30-minute-slot suppression once the user clicks
Trader. Click state stored in localStorage under
oge-trader-last-click.
Removed:
- Wave.fleetIds intermediate field and the eventRow-<id> DOM
extraction step (return-time alone is now the identity carrier).
- Dead helpers from the v1.3.1 reconcile pipeline: computeWaveId,
applyResets, applyRenames, STALE_WAVE_AFTER_SEC, and the time-
tolerance match path.

Changes in v1.3.5:
- ntfy.sh authentication now uses the ?auth=base64(:token) query parameter
instead of the Authorization header. This is a documented ntfy.sh
alternative that bypasses the Firefox CORS preflight restriction
(Access-Control-Allow-Headers: * does not cover Authorization).
No background script is required. The background.js file and its
manifest/rollup entries have been removed.

Changes in v1.3.1:
- Expedition reminders pivoted from a separately-deployed Cloudflare
Worker to direct ntfy.sh scheduling via the X-Delay header. The
extension publishes up to 6 pre-scheduled push notifications per
expedition wave; ntfy.sh holds them in its queue and delivers each
at the right time, even when the browser is closed. Cancellation
on re-send is via DELETE /<topic>/<id>.
- The worker/ directory has been removed entirely; the Cloudflare
dependency is gone.
- New host permission: https://ntfy.sh/* — required for the schedule /
cancel / queue-poll calls described above. Used solely by the
reminders feature, gated behind a user-pasted ntfy.sh access token
in the OG-E settings panel.
- Wave identity simplified to time-only (no per-planet tracking in
identity, planets shown only for display).
- "OG-E Dashboard" rename of the histogram page (file paths unchanged
on disk — backward compatible).
- Push priority escalates 3→4→5 (default → high → max) across the
six reminders so an ignored first ping gets louder later.
- Push title format: "[<universeId>] Expeditions back"; body:
"Expeditions returned - Reminder #N."

Changes in v1.3.0:
- Added: Expedition return reminders. The extension passively reads
expedition return-flight rows from the in-game event list and writes
per-wave return times to the user's own private GitHub gist. A separate
Cloudflare Worker (not part of this extension) reads the gist and sends
push notifications via ntfy. New "Expedition Reminders" tab on the
histogram page with config + a live gist preview.
- Changed: reminder state is a separate plain-JSON file in the same gist;
the gist token is also mirrored into chrome.storage.local so the
extension page can fetch the gist for the preview.

What's new in v1.2.0
New: Free Positions tab — longest confirmed-empty runs per slot across all scanned galaxies
New: per-universe data isolation; each OGame server keeps its own separate scan and colony database
Fix: extension buttons no longer appear on forum or lobby pages
Fix: AGR menu no longer breaks after interacting with OG-E
Histogram chart now adapts to window width; no more horizontal scroll

Changes in v1.0.6:
• colonyRecorder: gate first tryCollect on whenHistoryHydrated() —
fixes colony record loss on Firefox/Android when
chrome.storage.local resolves after DOMContentLoaded
• draggableButton: measure element dimensions on drag-start instead
of a caller-supplied size param — fixes Y-axis clamp for
non-square elements (freshPlanet banner)
• readabilityBoost: add selector for fleet link on fleetdispatch
step 2 (#ago_summary_fleets) where AGR drops the ago_movement class