Where Does Frosty Store Configs and Mods?
Frosty keeps manager and editor settings as JSON under %LOCALAPPDATA%\Frosty, with per-game caches beside them and mod files wherever you keep them.
Last updated
Frosty separates its own settings from your mod collection cleanly. The JSON configs and per-game caches live under %LOCALAPPDATA%\Frosty, shared across Frosty builds on the machine. Your .fbmod files live wherever you downloaded them; Frosty only references them.
That split guides every fix. Interface and profile trouble points at the AppData JSONs, which regenerate when deleted. Missing-texture or stale-data weirdness points at the per-game Cache folder, which the editor rebuilds. Mods themselves are safest in a folder you manage.
Where Frosty stores this, by platform
%LOCALAPPDATA%\Frosty
FrostyModManager.json and FrostyEditor.json for settings, Cache/<GameProfile>/ for generated type and asset caches. Corrupted configs can be deleted; both files regenerate with defaults.
[ModsFolder]\*.fbmod
Applied mods are injected at launch without touching game files, so removing a mod from the manager restores vanilla. Game profiles remember the target game between sessions.
Frequently asked questions
Frosty crashes on startup after a bad setting. How do I reset?
Close Frosty and delete (or rename) FrostyModManager.json and FrostyEditor.json in %LOCALAPPDATA%\Frosty. Both regenerate with defaults on next launch. Your .fbmod files elsewhere are untouched by the reset.
Where should I keep downloaded .fbmod files?
Anywhere you like; Frosty references them by path. Keep a dedicated mods folder outside the game install so reinstalls and updates never sweep your collection away.
Notice an outdated path? Let us know.