M1: keep settings next to the executable in portable mode (#1320) (#1558)

The settings folder comes from craft-settings' rules: FIGCRAFT_CONFIG_DIR,
a `portable` file next to the executable (config/ beside it), then the
platform folder every earlier version used. The Windows portable zip ships
the marker, and a portable folder without preferences starts with a copy
of the platform folder's.
This commit is contained in:
BFlat
2026-10-30 03:35:12 +07:00
committed by GitHub
parent 28a0fe6d18
commit aa727500a4
11 changed files with 214 additions and 6 deletions
+1 -1
View File
@@ -180,7 +180,7 @@ with the same limits and its manifest's permissions, as any other.
The desktop app keeps such plugins per user, beside its settings (`Plugins/` in FigCraft's settings
folder: `%APPDATA%\FigCraft` on Windows, `~/Library/Application Support/FigCraft` on macOS,
`~/.config/FigCraft` elsewhere), each in a folder of its own named by a hash of its id, with its
`~/.config/FigCraft` elsewhere; `config/` beside the executable in a portable copy), each in a folder of its own named by a hash of its id, with its
module and its assets. The CLI and the MCP server install for the session only.
**Updating.** When the directory has a newer version than the one installed, the plugin's row