-
Automatic database backups. Silo keeps a copy of its library database (tags, notes,
ratings, loadouts, settings) from each of the last five days you used it, in its app data
folder, plus one copy taken just before an upgrade changes the database. Backups never
include your GitHub token. (#216)
-
Silo keeps a log. Silo writes a log file in its app data folder (five files of 2 MB at most),
so problems can be traced after the fact. Every file Silo moves, links, replaces, backs up or
edits is recorded. (#217)
-
Copy diagnostics. Settings → Diagnostics → Copy diagnostics copies your report and Silo’s
recent log, with your user name removed, ready to paste into a bug report. If the clipboard can’t
be used, Silo offers to save them to a file instead. Exported reports leave out your user name
too. (#217)
-
Your original game settings are kept. The first time Silo edits gameSettings.xml or a mod’s
settings file, it keeps the untouched original (or the oldest backup an earlier Silo left)
beside it (.silo-original.bak), plus the three versions before each edit (.bak, .bak.2,
.bak.3). Before, every edit replaced the only backup. (#213)
-
Mod icons stay cached across Silo updates. The icon cache uses stable names, so icons
aren’t decoded again after every update. (#213)
-
Settings edits aren’t lost to the game anymore. Silo won’t change gameSettings.xml or a
mod’s settings while Farming Simulator 25 is running, because the game writes its own copy
back when it exits. Close the game first. (#214)
-
Silo stays responsive while it reads and saves. Backing up a savegame, opening or saving
settings, importing or exporting loadouts and similar actions now run in the background
instead of freezing the window. (#214)
-
The open-folder links in Settings work. They silently did nothing before. (#215)
-
Going back to an older Silo can’t damage your library. Silo now records its database
version and won’t touch a database made by a newer Silo; it asks you to install the latest
version instead. (#216)
-
A damaged database no longer breaks Silo. If Silo’s database can’t be read, Silo keeps the
damaged file, restores its latest backup copy (or starts fresh), and tells you what happened.
Your mods are never touched. (#216)
-
Silo can find a library archive on another drive again. A custom archive now holds a small
.silo-archive.json note and your mods folder points to it, so Silo finds the archive even if
its database is lost. (#216)
-
Rescanning never fights a change in progress. A rescan, for example when you switch back
to Silo, no longer rewrites Silo’s record of your library while another change is running.
(#218)
-
A mods folder can’t share files with an archive. Silo refuses a mods folder that is another
mods folder’s archive, sits inside one (a category folder), holds one, or whose own archive
would be one. The folder Farming Simulator’s own setting points at counts too: if it shares files
with an archive, Silo says why and won’t change files there until you choose another folder (or,
when only that setting is the problem, point Farming Simulator at your folder).
Before, two layouts could share files and organizing one moved the other’s mods. (#220)
-
Optimize links handles an archive on a network share. On a drive Silo can’t identify, it
now tests once whether a hardlink works instead of assuming, so Optimize links no longer tries a
hardlink for each mod and fails, and the move dialog says the same as what the move does.
(#220)
-
Cancelling an archive move leaves no empty folders behind. Category folders Silo made in
the new location are removed when they’re empty, also for mods whose copy was stopped partway.
Folders that were already there, or that hold anything, are kept. (#220)
-
Stricter file-name checks. File names with a colon, a trailing dot or space, or a reserved
Windows device name (such as CON or NUL) are refused. (#213)
-
Savegame backups only copy real savegames. Silo now checks the folder against the
savegames it found before copying anything. (#214)
-
The catalog address is fixed in release builds. Silo always downloads catalog mods
through its own catalog; the developer-only setting to change it no longer exists in the
release app. (#214)
-
Silo decides where it writes. Changing the mods folder or the library archive now uses a
folder picker Silo opens itself, and Silo only switches to a folder chosen there or one it
already knows. Editing game settings can’t change FS25’s mods folder either. (#215)
-
Updates only replace mods in your library. An update can only swap a mod’s zip in your
mods folder or library archive, never any other file there. (#215)
-
Collections install exactly what the preview showed. Silo matches every mod the same way
in the preview and the install, and won’t install if the collection, or what the catalog
found for it, changed after you previewed it. (#215)
Beta release. Download the installer for your OS below.
Windows installers are code-signed. macOS/Linux builds are open source and
OS-unsigned — Gatekeeper may warn on first launch; you can inspect or build
from source at any time.
