💾Settings Save Path
The asset uses several files to save settings for different sections of the asset. This dictates where these files are stored.
Whichever path you choose, remember that while switching them, it might be reset to the defaults.
This option is available in version 3.1.0 and later. As I am writing this, the update hasn't gone live.
User Settings
✅ Advantages:
Personalized settings per user Ideal for preferences like window layout, UI themes, or local workflow tweaks.
No Git pollution Since UserSettings are ignored by default in
.gitignore, changes don’t show up in version control.Avoids merge conflicts
Each user maintains their own independent version of the settings.
⚠️ Disadvantages:
Not shared with others Each team member must configure settings individually.
Requires reconfiguration on new machines If you move to another PC or clone the repo, you need to reapply settings manually.
Not suitable for team-wide configurations Inconsistent settings may cause confusion if the tool’s behavior differs between users.
Project Settings
✅ Advantages:
Shared with the whole team Settings are stored inside the project and committed to version control (Git, etc.), so all team members use the same configuration.
Ideal for project-wide behavior Useful when settings affect how the project behaves for everyone (e.g., serialization preferences, code generation rules, etc.).
Included in backups and exports The settings file travels with the project automatically.
⚠️ Disadvantages:
Generates Git changes frequently Any small tweak adds to the commit list, even if it’s just a local preference.
Cannot have personal overrides Every user shares the same settings, so it’s not good for purely local editor preferences.
Might create merge conflicts Especially if multiple users modify settings simultaneously.
Last updated