System: Debian 13
I'm not sure if this is more a legendary issue, or a SMM issue, but metadata.go seems to be expecting a boolean value for installed.json -> game -> requires_ot however in some cases it gets saved as 0 instead of a boolean (I'm not sure if this is heroic causing this mismatch but it was across multiple games), this causes SMM to process the install, then discard it as invalid. Bringing you to a "there are x installs present" but with an invalid install tag, and also makes corresponding installs not appear on the debug info.
2026-07-28T14:02:30-04:00 INF SatisfactoryModManager/main.go:55 starting Satisfactory Mod Manager version=3.1.0 commit=935ec4ae90e4c46337122cdf568f78635d85087e date=2026-06-06T16:04:55Z type=appimage
2026-07-28T14:02:31-04:00 INF ficsitcli/metadata.go:27 failed to find installations error="Legendary not installed"
2026-07-28T14:02:31-04:00 INF ficsitcli/metadata.go:27 failed to find installations error="failed to parse legendary installed.json output: json: cannot unmarshal number into Go struct field Game.requires_ot of type bool"
2026-07-28T14:02:31-04:00 INF ficsitcli/metadata.go:27 failed to find installations error="steam-flatpak not installed"
2026-07-28T14:02:31-04:00 INF ficsitcli/metadata.go:27 failed to find installations error="steam-snap not installed"
2026-07-28T14:02:31-04:00 INF ficsitcli/metadata.go:27 failed to find installations error="Heroic not installed"
I resolved it by backing up installed.json and then replacing all "requires_ot": 0 with "requires_ot": false, which allowed the program to parse the installs again, but if possible it would be nice to have it realize that 0 = false for the metadata
System: Debian 13
I'm not sure if this is more a legendary issue, or a SMM issue, but metadata.go seems to be expecting a boolean value for installed.json -> game -> requires_ot however in some cases it gets saved as 0 instead of a boolean (I'm not sure if this is heroic causing this mismatch but it was across multiple games), this causes SMM to process the install, then discard it as invalid. Bringing you to a "there are x installs present" but with an invalid install tag, and also makes corresponding installs not appear on the debug info.
I resolved it by backing up installed.json and then replacing all "requires_ot": 0 with "requires_ot": false, which allowed the program to parse the installs again, but if possible it would be nice to have it realize that 0 = false for the metadata