From c4cbde3a0ef12df9c666e7c31a3f68fae9cb752d Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 13 Apr 2026 06:07:35 +0000 Subject: [PATCH] =?UTF-8?q?Bridge:=20MSG=20=E2=80=94=20correction=20to=20v?= =?UTF-8?q?ersion=20display,=20cron=20stores=20versions=20backwards?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit current_version and latest_version swapped in DB. Server has 0.1.0 installed, 1.0.0 is latest. Need fix in CheckModpackUpdates.php assignment logic. --- .../MSG-2026-04-13-version-display-format.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/docs/code-bridge/responses/MSG-2026-04-13-version-display-format.md b/docs/code-bridge/responses/MSG-2026-04-13-version-display-format.md index 41ee7c9..2837148 100644 --- a/docs/code-bridge/responses/MSG-2026-04-13-version-display-format.md +++ b/docs/code-bridge/responses/MSG-2026-04-13-version-display-format.md @@ -47,3 +47,21 @@ Also applies to the "up to date" line 156 if it shows latest_version. ## After Code Pushes Chronicler will copy wrapper.tsx to Dev Panel, rebuild frontend, verify display. + +--- + +## CORRECTION (Chronicler #85 update) + +The DB values are actually stored **backwards**: +``` +current_version: "1.0.0" ← this is the LATEST from the API +latest_version: "All the Mods 9-0.1.0" ← this is what's INSTALLED +``` + +Test server has **0.1.0 installed**, and **1.0.0 is the latest available**. + +So there are TWO issues: +1. **Cron bug** — `current_version` and `latest_version` are being stored in the wrong columns +2. **Display** — once fixed, should read: `ATM9 0.1.0 → 1.0.0 ↑` + +Please check `CheckModpackUpdates.php` — the assignment of which value goes into `current_version` vs `latest_version` when writing to `modpackchecker_servers`.