Where Does Modo Store Configs and Kits?
Modo keeps its versioned .cfg, custom configs, kits and content under Luxology folders. Paths on Windows, macOS and Linux.
Last updated
Modo scatters user data across Luxology folders. The versioned MODO*.cfg holds recent files, layouts and keys, with a shutdown backup beside it for rescue. Custom Configs, Scripts and Kits live in their own trees, and installable content (the Content/Kits path) in another.
A corrupt config renames itself instead of deleting, so check for the renamed file before rebuilding everything. Safe mode (-safemode, plus -dbon:noconfig to protect the old file) boots vanilla for diagnosis. Reintroduce configs, kits and scripts one by one to find the culprit.
Where Modo stores this, by platform
C:\Users\[Username]\AppData\Roaming\Luxology
Versioned cfg plus Configs, Scripts and Kits trees. Shared content also appears under Documents\Luxology. Launch with -safemode -dbon:noconfig to diagnose without overwriting.
~/Library/Application Support/Luxology
Same role as Windows, with shared content in /Library/Application Support/Luxology. Stray com.luxology files in ~/Library/Preferences can be removed on full uninstall.
~/.luxology
Home-dotfolder equivalent, with shared bits in /usr/share/Luxology. NEXUS_USER, NEXUS_PREFS and NEXUS_TEMP variables can remap the whole tree for studio setups.
Frequently asked questions
Modo acts broken after a crash, what do I reset?
Close Modo, rename the MODO*.cfg in the Luxology folder above, and relaunch to regenerate it. The shutdown backup beside it restores the previous state if the fresh config doesn't help. Then re-add kits one at a time.
Where do I install a Modo kit?
Copy it into the Content/Kits directory (/Library/Application Support/Luxology/Content/Kits on Mac and equivalents elsewhere). Modo scans config paths at startup, so kits appear after a relaunch.
Notice an outdated path? Let us know.