-
Notifications
You must be signed in to change notification settings - Fork 0
Data Locations and Logs
gtavmm-core keeps its own SQLite database — installed mods, history, profiles, settings, the
AI assistant's configuration, prompt templates. It lives at the OS-standard per-app data
directory (via the directories crate, org SpaceSquare, app GTAVModsManager):
-
Windows:
%APPDATA%\SpaceSquare\GTAVModsManager\...\gtavmm.sqlite3 -
Linux:
~/.local/share/SpaceSquare/GTAVModsManager/gtavmm.sqlite3(or$XDG_DATA_HOMEif set)
The exact subfolder depends on the directories crate's platform conventions — if you need the
precise path on your machine, the CLI and app both resolve it the same way at startup.
The database schema is versioned via SQLite's PRAGMA user_version and migrates forward
automatically when you run a newer build against an older database — no manual migration step,
and no data loss on upgrade.
Stored in the same database (user_settings table) — theme, language, AI provider/model
choice, default auto-backup behavior, the auto-approve whitelist, and any manual game-path
override. There's no separate plaintext config file to hunt for.
The AI assistant's cloud API key (if you use one) is stored in your OS's native credential store — Windows Credential Manager, or the Linux Secret Service (D-Bus) — never in the SQLite database or a plaintext file.
gtavmm report-crash "<description>" generates a GitHub Issue draft with your description and
relevant diagnostic info, after stripping your home-directory path from anything included. It
only prints a URL and the draft text — nothing is sent anywhere until you open that URL and
submit it yourself.