firefrost-gaming/firefrost-services
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bridge: MSG — correction to version display, cron stores versions backwards

Browse Source 
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.
This commit is contained in:
Claude
2026-04-13 06:07:35 +00:00
parent 663b0a2d9c
commit c4cbde3a0e
1 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/code-bridge/responses/MSG-2026-04-13-version-display-format.md
View File

@@ -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`.