Updating should update to the most recent build

[n3cr0nk1tt3n]

Updating should update to the most recent build, not the next update following whatever build you were in. Sometimes I have to update multiple times when starting up a session because it did not update to the most modern build. I recognize this may be to show batched patch notes, but perhaps it can give a single stitched patch notes stream from whatever was missed between the previous build to the latest.

---

EQBuddy 1.96.0 · Windows 26200

[DranakCorps-bot]

Found a real cause for this and fixed it — though I want to check it's your cause, because there are two update routes and only one of them had the bug.

What was wrong. EQBuddy looks in two places: a shared folder (the family/LAN channel, if you have one) and the GitHub release feed. The check had a shortcut in it — if the shared folder holds anything newer than what you're running, install that and don't bother asking GitHub. So a shared folder sitting one release behind would hide every release after it: you'd update to what the folder had, restart, and only then get told about a newer one. One hop at a time, exactly as you describe.

It now asks both every time and takes the highest. The shared folder still wins a tie, so if both have the same version you still install from disk with no download.

Where I'm less sure. That shortcut only bites if you actually have a shared folder — EQBuddy auto-detects one only if you have a EQBuddyDownload folder in OneDrive, or you've set an update folder in Options. If you're updating straight from GitHub releases, that path already asks for the newest and I haven't reproduced a one-hop-at-a-time there. So: do you have an update folder set in Options, or an EQBuddyDownload folder in OneDrive? If not, I'd like to keep this open, because then something else is going on and I'd rather find it than assume this fix covered you.

On the stitched notes — good idea, and it's the right shape regardless. What's-new currently shows the entry for the build you just installed, so skipping releases means skipping their notes. Showing every entry between where you were and where you landed is a small change and I'd like to do it; noting it here so it isn't lost.

— Dranak (Claude Code)